# Agent MCP Directory: every page > 1,336 companies checked for a public MCP server, a CLI and an OpenAPI file; tools were listed for 263 of them on 4 November 2026. Edition 2026-11-04. 1668 pages. Index: https://agentmcpdirectory.com/llms.txt --- title: "MCP servers and CLIs by company, checked | Agent MCP Directory" description: "1,336 companies checked for a public MCP server, a CLI and an OpenAPI file; tools were listed for 263 of them on 4 November 2026." canonical: https://agentmcpdirectory.com/ site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Home" --- # MCP servers and CLIs by company, checked | Agent MCP Directory > 1,336 companies checked for a public MCP server, a CLI and an OpenAPI file; tools were listed for 263 of them on 4 November 2026. Source: https://agentmcpdirectory.com/ Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP servers and CLIs by company, checked by connecting 1,336 companies checked on 4 November 2026. The connector tried 864 endpoints and 852 answered; it listed tools on 263 open servers, the only rows counted as having an MCP server. 533 answered with a sign-in challenge (tools not seen, not counted) and 472 had no endpoint to connect to. 36 have a CLI on record; 1,044 have neither. Each square is one of 1,336 companies, grouped by what the connector saw on 4 November 2026. Filled electric squares are open servers that listed tools; the key carries the same counts and links to each list. - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Category - [Developer Tools](https://agentmcpdirectory.com/directory/category/developer-tools/) 450 - [Infrastructure](https://agentmcpdirectory.com/directory/category/infrastructure/) 303 - [Uncategorised](https://agentmcpdirectory.com/directory/category/uncategorised/) 201 - [Agent Tools](https://agentmcpdirectory.com/directory/category/agent-tools/) 74 - [Productivity](https://agentmcpdirectory.com/directory/category/productivity/) 49 - [Data & Analytics](https://agentmcpdirectory.com/directory/category/data-and-analytics/) 39 - [AI & ML](https://agentmcpdirectory.com/directory/category/ai-and-ml/) 36 - [Communication & Support](https://agentmcpdirectory.com/directory/category/communication-and-support/) 35 - [Marketing](https://agentmcpdirectory.com/directory/category/marketing/) 31 - [Payments & Fintech](https://agentmcpdirectory.com/directory/category/payments-and-fintech/) 29 [All 27 categories](https://agentmcpdirectory.com/directory/), [by status](https://agentmcpdirectory.com/directory/status/verified/) and [A to Z](https://agentmcpdirectory.com/directory/letter/a/). ## First twenty rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Ora ora.ai | Verified no auth | – | 95 A+ | yes | yes | 2026-11-04 | | Google google.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | Cloudflare cloudflare.com | Verified no auth | wrangler | 82 B | yes | yes | 2026-11-04 | | Google Cloud googleapis.com | Verified no auth | – | | – | no | 2026-11-04 | | Microsoft microsoft.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Forter forter.com | Verified no auth | – | 92 A | yes | no | 2026-11-04 | | Autodesk autodesk.com | Verified no auth | – | 36 D | – | no | 2026-11-04 | | JustClaw-It justclaw.it.com | Verified no auth | – | | – | not read | 2026-11-04 | | Hugging Face huggingface.co | Verified no auth | huggingface_hub | 82 B | – | no | 2026-11-04 | | Usercentrics usercentrics.eu | Verified no auth | – | | – | yes | 2026-11-04 | | Twilio twilio.com | Verified no auth | twilio-cli | 85 B | – | no | 2026-11-04 | | Siemens siemens.com | Verified no auth | – | 56 C | – | no | 2026-11-04 | | AWS api.aws | Verified no auth | – | | – | not read | 2026-11-04 | | Kraken kraken.com | Verified no auth | – | 82 B | yes | no | 2026-11-04 | | Claude claude.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | GameAnalytics gameanalytics.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | Atom.com atom.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | DMCA.com dmca.com | Verified no auth | – | | – | no | 2026-11-04 | | Studocu studocu.com | Verified no auth | – | 40 D | – | no | 2026-11-04 | | Wolfram wolfram.com | Verified no auth | – | | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. The ruled row is Ora, the scanner this directory recommends for [testing an MCP server](https://agentmcpdirectory.com/test-your-mcp-server/); the other nineteen are verified open servers ordered by popularity rank. The CLI column shows a package only where a source names one; a dash is a gap in the record, not proof that none exists. All 1,336 rows are in [the directory](https://agentmcpdirectory.com/directory/). ## Ora's own MCP server Ora is the scanner this directory recommends, and its own row is verified like any other. The connector completed the handshake with `https://ora.ai/api/mcp` on 4 November 2026 with no credentials and listed 18 tools and 7 resources. The descriptions below are Ora's own, read from its public documentation on 5 November 2026. [The full row](https://agentmcpdirectory.com/directory/ora-ai/). | Tool | What Ora says it does | Parameters | | --- | --- | --- | | scan_domain | Run a full agent-readiness scan | url (required), mcpUrl (optional) | | get_score | Get the cached score for a domain | domain (required) | | get_leaderboard | Get ranked domains by score | category (optional), limit (optional) | | discover_products | Find products by intent | intent (required), limit (optional) | | search_capabilities | Find pay-per-call API endpoints (x402/MPP; no API key) | query (required), limit (optional) | | ask | Retrieve ora's published website passages, source URLs, and provenance using NLWeb v0.55; read-only | query.text (required, trimmed, 1-2000 characters); context, prefer | | get_verification_challenge | Get a challenge that proves agent identity | (none) | | submit_feedback | Submit agent feedback (MCP-only, verification required) | domain, agent_id, task_description, outcome, content | | send_feedback | Tell the ora team about a bug, a wrong result, a confusing tool, or a tool you needed in ora's MCP or scanner (MCP-only, verification required) | summary (required, one sentence, 5-300 characters), category | | submit_check_feedback | Report a problem with a specific check result (MCP-only, verification required) | domain, agent_id, check_id, content, is_bug_report (required) | | get_feedback | Read agent feedback for a product | domain (required), limit (optional) | | list_skills | List the skills ora publishes for coding agents | (none) | | get_skill | Fetch a skill by name and follow it step by step (e.g. "agent-ready-website") | name (required) | | list_checks | List the full check catalog behind the score (same document as GET /api/checks) | (none) | | run_checks | Run a selected subset of checks and get per-check results back - the re-verify step after a fix (same shape as POST /api/scan/checks) | url (required), checkIds (required, ids from list_checks), mcpUrl (optional) | | run_journey | Send a real AI agent at a site on a task and get ora's verdict, step count and insight | domain (required); intent | | get_journey_run | Keep following a run run_journey started until it finishes (waits up to 50s per call; starts no run) | run_id (required) | | generate_agent_files | Draft a site's agent discovery files from ora's last scan (same files as GET /api/agent-files/{domain}) | domain (required); include | ## The Act Layer Census Share of probed domains that publish each act-layer file, crawl of 4 November 2026. [Method and categories](https://agentmcpdirectory.com/census/). | File | Top 10,000 | Ora leaderboard | | --- | --- | --- | | /.well-known/oauth-authorization-server | 208 of 7,468 (2.79%) | 253 of 3,375 (7.5%) | | /.well-known/agent-skills/index.json | 53 of 7,435 (0.71%) | 144 of 3,364 (4.28%) | | /.well-known/ai-catalog.json | 38 of 7,438 (0.51%) | 85 of 3,365 (2.53%) | | /openapi.json | 21 of 7,472 (0.28%) | 78 of 3,369 (2.32%) | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | | /.well-known/agent-card.json | 10 of 7,470 (0.13%) | 48 of 3,368 (1.43%) | ## Hosts and registries at a glance | Product | Remote transport | OAuth with client registration | Hosting limits | | --- | --- | --- | --- | | Cloudflare | Streamable HTTP only | yes, DCR and CIMD | 80 servers per portal | | Vercel | Streamable HTTP only | bring your own AS; CIMD on Vercel MCP | Vercel Functions limits | | Composio | HTTP | Composio holds app OAuth | 2,000 to 10,000 requests a minute | | Zapier MCP | Streamable HTTP only | OAuth for clients | task quota | | Mintlify MCP | Streamable HTTP | client credentials at /authed/mcp/oauth/token | published rate limits | | Apify MCP | Streamable HTTP and stdio | OAuth | Actor run limits | | Browserbase MCP | Streamable HTTP | no, API key in URL | not stated | Registries and gateways, the rubric and the evidence are on [the hosts page](https://agentmcpdirectory.com/hosts/). The rubric has 9 lines and every cell carries a source. ## The directory as an API Agents can read the same rows through an MCP server, a REST API and an NLWeb ask endpoint, all read-only and open. [The API and MCP server page](https://agentmcpdirectory.com/developers/) lists the tools and the limits. The vendors around MCP servers, with their facts, are in [the vendor list](https://agentmcpdirectory.com/vendors/), which has its own CSV and JSON download. One call returns a company's row, with the status the connector recorded and the date it was observed: ```bash curl -s 'https://agentmcpdirectory.com/api/v1/get_company?domain=stripe.com' | jq '{mcp_status, has_mcp, url}' ``` ## How to get listed 1. Serve a remote MCP endpoint over Streamable HTTP and list it in the official registry ([how](https://agentmcpdirectory.com/guides/get-listed-in-registries/)). 2. Publish OAuth protected resource metadata so an agent can follow your sign-in ([how](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/)). 3. Give every tool a plain description; agents choose tools by it ([how](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/)). 4. Link the endpoint, your OpenAPI file and [llms.txt](https://agentmcpdirectory.com/llms.txt) from your docs; agents follow links, they do not guess paths. 5. Send the endpoint through [the submit page](https://agentmcpdirectory.com/directory/submit/); the connector verifies it before anything is published. 6. Check the row again after each release; the directory re-runs monthly and the whole site is also at [llms-full.txt](https://agentmcpdirectory.com/llms-full.txt). ## Latest news - 3 November 2026: [New Cloudflare AI Gateways require authentication](https://agentmcpdirectory.com/news/2026-11-03-new-cloudflare-ai-gateways-require-authentication/) - 2 November 2026: [Vercel MCP accepts Client ID Metadata Documents](https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-accepts-client-id-metadata-documents/) - 2 November 2026: [Vercel MCP renders deployments as an interactive card](https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-renders-deployments-as-an-interactive-card/) - 31 October 2026: [Smithery shuts down MCP Proxy and managed identity](https://agentmcpdirectory.com/news/2026-10-31-smithery-shuts-down-mcp-proxy-and-managed-identity/) - 30 October 2026: [Official Ruby SDK for MCP reaches Tier 1](https://agentmcpdirectory.com/news/2026-10-30-official-ruby-sdk-for-mcp-reaches-tier-1/) ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [GitHub MCP Registry API](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [awesome-remote-mcp-servers](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=home), read 4 November 2026 (vendor-published scores and categories) - [Tranco list](https://tranco-list.eu/), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=home), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=home), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "About the directory | Agent MCP Directory" description: "Agent MCP Directory is a reference publication on the act layer of agent readiness: which companies have an MCP server or a CLI, checked by connecting." canonical: https://agentmcpdirectory.com/about site: "Agent MCP Directory" last_updated: 2026-11-04 section: "About" --- # About the directory | Agent MCP Directory > Agent MCP Directory is a reference publication on the act layer of agent readiness: which companies have an MCP server or a CLI, checked by connecting. Source: https://agentmcpdirectory.com/about Site: Agent MCP Directory Last reviewed: 2026-11-04 # About Agent MCP Directory Agent MCP Directory is a reference publication on the act layer of agent readiness, the part where an agent finishes a task instead of reading a page. It keeps a directory of 1,336 companies checked by connecting where an endpoint is known, a census of discovery files, and comparisons of the hosts, registries and gateways behind them. ## What it covers - The directory: which companies expose a public MCP server, a CLI, an OpenAPI file, WebMCP, an A2A agent card or agents.json, and what a connector found when it tried. - The census: how many of the top 10,000 sites publish those discovery files. - The hosts: Cloudflare, Vercel, registries and AI gateways compared on a published rubric. - Guides, a glossary, a FAQ and dated news for the people who build and call these servers. ## Who it is for Product engineers deciding what to expose, developer-platform leads choosing a host, agent builders looking for servers to call, and technical marketers who need to say a company has an MCP server and mean it. ## How it is made Every page is generated from dated data files: the directory run of 4 November 2026, the shared crawl and the research notes. A page that has no data behind it is not published. The site has no accounts, and its read-only [API and MCP server](https://agentmcpdirectory.com/developers/) answer from the same data files as the pages. The [method](https://agentmcpdirectory.com/method/), the [editorial policy](https://agentmcpdirectory.com/editorial-policy/) and the [corrections page](https://agentmcpdirectory.com/corrections/) say how it works. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/about/index.md) ## Sources - [Model Context Protocol specification](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Act Layer Census: discovery files | Agent MCP Directory" description: "The Act Layer Census: how many of the top 10,000 sites publish MCP, A2A, OpenAPI and OAuth discovery files. Crawl of 4 November 2026." canonical: https://agentmcpdirectory.com/census site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Census" --- # Act Layer Census: discovery files | Agent MCP Directory > The Act Layer Census: how many of the top 10,000 sites publish MCP, A2A, OpenAPI and OAuth discovery files. Crawl of 4 November 2026. Source: https://agentmcpdirectory.com/census Site: Agent MCP Directory Last reviewed: 2026-11-04 # The Act Layer Census Of 7,548 top-10,000 domains probed on 4 November 2026, 208 publish OAuth server metadata, 21 an openapi.json and 19 an MCP discovery file. Valid files only: sites that answer every path with a web page are not counted. Ora's own leaderboard cohort publishes them more often. ## The headline chart Figure 1. Share of probed domains that publish each act-layer file, 4 November 2026. | File | Top 10,000 | Ora leaderboard | | --- | --- | --- | | /.well-known/oauth-authorization-server | 208 of 7,468 (2.79%) | 253 of 3,375 (7.5%) | | /.well-known/agent-skills/index.json | 53 of 7,435 (0.71%) | 144 of 3,364 (4.28%) | | /.well-known/ai-catalog.json | 38 of 7,438 (0.51%) | 85 of 3,365 (2.53%) | | /openapi.json | 21 of 7,472 (0.28%) | 78 of 3,369 (2.32%) | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | | /.well-known/agent-card.json | 10 of 7,470 (0.13%) | 48 of 3,368 (1.43%) | ## Next to Ora's lab finding In Ora's lab, agents reached openapi.json in 21 percent of traced runs on sites that ship one, and 97 percent of the openapi.json fetches arrived through a link, not a guessed path. That is a vendor-published finding from [Ora's AgentReady launch post](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset) of 19 October 2026, read 4 November 2026. It counts agent runs on sites that already ship an OpenAPI file; the census counts how many sites ship one at all, so the two numbers answer different questions and should not be set against each other as rates. Read together: a file is rare across the web (0.28% of probed top-10,000 domains publish a valid openapi.json), and where one exists agents reach it by following a link. Publishing the file is not enough; link it from the docs and from llms.txt. ## Files by cohort | File | Probed | Answered with JSON or YAML | Valid file | Share | | --- | --- | --- | --- | --- | | /.well-known/mcp.json | 7,470 | 27 | 19 | 0.25% | | /.well-known/agent.json | 7,461 | 12 | 6 | 0.08% | | /.well-known/agent-card.json | 7,470 | 17 | 10 | 0.13% | | /agents.json | 7,485 | 7 | 0 | 0% | | /openapi.json | 7,472 | 24 | 21 | 0.28% | | /openapi.yaml | 7,503 | 10 | 10 | 0.13% | | /.well-known/oauth-authorization-server | 7,468 | 214 | 208 | 2.79% | | /.well-known/ai-catalog.json | 7,438 | 39 | 38 | 0.51% | | /.well-known/agent-skills/index.json | 7,435 | 60 | 53 | 0.71% | | File | Probed | Answered with JSON or YAML | Valid file | Share | | --- | --- | --- | --- | --- | | /.well-known/mcp.json | 3,366 | 82 | 66 | 1.96% | | /.well-known/agent.json | 3,366 | 17 | 14 | 0.42% | | /.well-known/agent-card.json | 3,368 | 48 | 48 | 1.43% | | /agents.json | 3,366 | 7 | 0 | 0% | | /openapi.json | 3,369 | 79 | 78 | 2.32% | | /openapi.yaml | 3,378 | 22 | 22 | 0.65% | | /.well-known/oauth-authorization-server | 3,375 | 253 | 253 | 7.5% | | /.well-known/ai-catalog.json | 3,365 | 85 | 85 | 2.53% | | /.well-known/agent-skills/index.json | 3,364 | 144 | 144 | 4.28% | Edition page with the by-category chart, the directory split and the downloads: [4 November 2026 edition](https://agentmcpdirectory.com/census/2026-11-04/). ## Method - Source: the shared crawl of 4 November 2026, 13,071 domains, last request 2026-11-04 20:16 UTC. The crawl reads robots.txt first and skips what it disallows. - Two cohorts: the Tranco top 10,000 list (9,999 domains, 7,548 reachable and probed) and the domains on Ora's public leaderboard (3,456 domains, 3,388 probed). A domain can sit in both. - A domain is probed for a path when the crawl holds an HTTP status for it. Paths the crawl skipped for robots.txt or request budget are not probed and are not in the denominator. - A file counts as found only when the answer is JSON (YAML for openapi.yaml) whose top-level keys match the file type. A web page that answers 200 does not count: on /.well-known/mcp.json that was 11.53% of the probed top-10,000 domains. - The categories come from Ora's leaderboard, so only the leaderboard cohort has them. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/census/index.md) ## Sources - [Ora: Introducing AgentReady.org](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 4 November 2026 (vendor-published lab finding) - [Ora public leaderboard (category and score source)](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 4 November 2026 - [Tranco list](https://tranco-list.eu/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Act Layer Census, 4 November 2026 edition | Agent MCP Directory" description: "Act Layer Census, 4 November 2026 edition: three charts, the method, CSV and JSON downloads and a citation line. Valid files only, by cohort and category." canonical: https://agentmcpdirectory.com/census/2026-11-04 site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-11-04 section: "Census" --- # Act Layer Census, 4 November 2026 edition | Agent MCP Directory > Act Layer Census, 4 November 2026 edition: three charts, the method, CSV and JSON downloads and a citation line. Valid files only, by cohort and category. Source: https://agentmcpdirectory.com/census/2026-11-04 Site: Agent MCP Directory Last reviewed: 2026-11-04 # Act Layer Census: 4 November 2026 edition First edition, 4 November 2026. In the top 10,000, 274 of 7,548 probed domains publish at least one of nine act-layer files; among Ora-scored domains the figure is 430 of 3,388. The directory splits 1,336 companies by what a connector found. ## Chart 1: which files sites publish Share of probed domains with a valid file, two cohorts. | File | Top 10,000 | Ora leaderboard | | --- | --- | --- | | /.well-known/oauth-authorization-server | 208 of 7,468 (2.79%) | 253 of 3,375 (7.5%) | | /.well-known/agent-skills/index.json | 53 of 7,435 (0.71%) | 144 of 3,364 (4.28%) | | /.well-known/ai-catalog.json | 38 of 7,438 (0.51%) | 85 of 3,365 (2.53%) | | /openapi.json | 21 of 7,472 (0.28%) | 78 of 3,369 (2.32%) | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | | /.well-known/agent-card.json | 10 of 7,470 (0.13%) | 48 of 3,368 (1.43%) | ## Chart 2: by category Leaderboard cohort only; categories are Ora's. | Category | Domains probed | With at least one file | Share | | --- | --- | --- | --- | | Agent Tools | 130 | 32 | 24.62% | | CRM | 42 | 9 | 21.43% | | Productivity | 148 | 28 | 18.92% | | Consumer | 74 | 14 | 18.92% | | Developer Tools | 379 | 67 | 17.68% | | Data & Analytics | 148 | 26 | 17.57% | | E-commerce | 148 | 26 | 17.57% | | Infrastructure | 232 | 40 | 17.24% | | Communication & Support | 147 | 25 | 17.01% | | Education | 93 | 11 | 11.83% | | AI & ML | 205 | 24 | 11.71% | | Marketing | 219 | 24 | 10.96% | | Security | 94 | 10 | 10.64% | | Identity & Auth | 70 | 7 | 10% | | Healthcare | 246 | 22 | 8.94% | | Payments & Fintech | 398 | 30 | 7.54% | | Gaming & Media | 70 | 5 | 7.14% | | HR & Recruiting | 58 | 4 | 6.9% | | Logistics & Supply Chain | 85 | 5 | 5.88% | | Real Estate & Construction | 85 | 5 | 5.88% | | Legal & Compliance | 90 | 4 | 4.44% | | Hardware & Robotics | 103 | 4 | 3.88% | | Climate & Energy | 42 | 0 | 0% | ## Chart 3: what the connector found Verified means the endpoint listed tools with no credentials. | Status | Companies | Counted as an MCP server | | --- | --- | --- | | Verified | 263 | yes | | Sign-in required | 533 | no | | Credential wall | 19 | no | | No answer | 47 | no | | No tools listed | 2 | no | | None found | 472 | no | ## Auth types among reachable endpoints | Auth type | Endpoints | | --- | --- | | No authentication | 263 | | API key | 19 | | OAuth with client registration | 517 | | OAuth without client registration | 16 | | Auth not determined | 2 | ## Method - Source: the shared crawl of 4 November 2026, 13,071 domains, last request 2026-11-04 20:16 UTC. The crawl reads robots.txt first and skips what it disallows. - Two cohorts: the Tranco top 10,000 list (9,999 domains, 7,548 reachable and probed) and the domains on Ora's public leaderboard (3,456 domains, 3,388 probed). A domain can sit in both. - A domain is probed for a path when the crawl holds an HTTP status for it. Paths the crawl skipped for robots.txt or request budget are not probed and are not in the denominator. - A file counts as found only when the answer is JSON (YAML for openapi.yaml) whose top-level keys match the file type. A web page that answers 200 does not count: on /.well-known/mcp.json that was 11.53% of the probed top-10,000 domains. - The categories come from Ora's leaderboard, so only the leaderboard cohort has them. ## Downloads and citation - [act-layer-census-2026-11-04.csv](https://agentmcpdirectory.com/data/act-layer-census-2026-11-04.csv) one row per cohort and file - [act-layer-census-2026-11-04.json](https://agentmcpdirectory.com/data/act-layer-census-2026-11-04.json) cohorts, files and categories Agent MCP Directory, "Act Layer Census", 4 November 2026 edition, https://agentmcpdirectory.com/census/2026-11-04 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/census/2026-11-04/index.md) ## Sources - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 4 November 2026 - [Tranco list](https://tranco-list.eu/), read 4 November 2026 - [Official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "CLIs and MCP servers: who ships which | Agent MCP Directory" description: "36 companies with a CLI package on record and which of them also have an open MCP server, with versions and last publish dates." canonical: https://agentmcpdirectory.com/cli-and-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # CLIs and MCP servers: who ships which | Agent MCP Directory > 36 companies with a CLI package on record and which of them also have an open MCP server, with versions and last publish dates. Source: https://agentmcpdirectory.com/cli-and-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # CLIs and MCP servers: who ships which 36 of 1,336 companies in the directory have a CLI package on record, and 7 of them also have an open MCP server; 256 have a server only and 1,044 have neither. The CLI count is a floor: a package is shown only where a source names one. All 1,336 directory companies, by whether the connector listed tools on an open MCP server and whether a CLI package is on record. The table gives the same counts. | Group | Companies | Share | | --- | --- | --- | | Open MCP server and a CLI | 7 | 0.5% | | Open MCP server, no CLI on record | 256 | 19.2% | | A CLI on record, no open MCP server | 29 | 2.2% | | Neither | 1,044 | 78.1% | ## The 36 CLIs on record | Company | CLI package | Latest | Last publish | MCP server | Ora score | | --- | --- | --- | --- | --- | --- | | Cloudflare cloudflare.com | wrangler npm | 4.157.0 | 2026-11-03 | Verified | 82 B | | Sentry sentry.io | @sentry/cli npm | 3.8.2 | 2026-10-22 | Sign-in required | 79 B | | OpenAI openai.com | @openai/codex npm | 0.166.0 | 2026-10-29 | None found | 58 C | | Shopify shopify.com | @shopify/cli npm | 5.0.1 | 2026-11-04 | None found | 72 B | | HubSpot hubspot.com | @hubspot/cli npm | 8.18.0 | 2026-10-27 | Sign-in required | 72 B | | Datadog datadoghq.com | @datadog/datadog-ci npm | 5.27.0 | 2026-11-04 | Sign-in required | 69 C | | Canva canva.com | @canva/cli npm | 2.17.0 | 2026-11-02 | Sign-in required | 42 D | | Salesforce salesforce.com | @salesforce/cli npm | 2.157.8 | 2026-11-03 | None found | 51 C | | Anthropic anthropic.com | @anthropic-ai/claude-code npm | 2.1.318 | 2026-11-03 | None found | 71 B | | Wix wix.com | @wix/cli npm | 1.2.8 | 2026-11-01 | Sign-in required | 64 C | | Hugging Face huggingface.co | huggingface_hub pypi | 2.4.0 | 2026-10-29 | Verified | 82 B | | Twilio twilio.com | twilio-cli npm | 7.2.0 | 2026-10-13 | Verified | 85 B | | Snowflake snowflake.com | snowflake-cli pypi | 3.32.1 | 2026-11-02 | None found | 66 C | | Webflow webflow.com | @webflow/webflow-cli npm | 2.15.0 | 2026-10-27 | Sign-in required | 78 B | | Zapier zapier.com | zapier-platform-cli npm | 19.3.0 | 2026-10-30 | Sign-in required | 84 B | | Vercel vercel.com | vercel npm | 65.11.0 | 2026-11-03 | Sign-in required | 91 A | | Sanity sanity.io | @sanity/cli npm | 8.27.0 | 2026-10-30 | Sign-in required | 72 B | | Netlify netlify.com | netlify-cli npm | 27.16.2 | 2026-11-02 | Sign-in required | 92 A | | Supabase supabase.com | supabase npm | 3.0.0 | 2026-11-02 | Sign-in required | 93 A | | Heroku heroku.com | heroku npm | 11.12.1 | 2026-10-22 | Sign-in required | 73 B | | Expo expo.dev | eas-cli npm | 27.4.1 | 2026-11-04 | Sign-in required | 66 C | | Contentful contentful.com | contentful-cli npm | 4.0.14 | 2026-11-02 | Sign-in required | 74 B | | ngrok ngrok.com | ngrok npm; a third-party Node wrapper for ngrok, not ngrok's own CLI | 5.0.0-beta.2 | 2023-05-07 | Sign-in required | 90 A | | Amazon Web Services aws.amazon.com | awscli pypi | 1.46.2 | 2026-10-21 | Verified | 60 C | | Apify apify.com | apify-cli npm | 1.11.0 | 2026-10-29 | Sign-in required | 96 A+ | | Composio composio.dev | composio pypi | 0.31.0 | 2026-11-03 | None found | 83 B | | Convex convex.dev | convex npm | 1.49.0 | 2026-10-30 | Verified | 71 B | | Deno deno.com | deno npm | 2.9.6 | 2026-08-27 | None found | 65 C | | Firebase firebase.google.com | firebase-tools npm | 15.35.0 | 2026-11-04 | None found | 56 C | | Google Gemini gemini.google.com | @google/gemini-cli npm | 0.66.0 | 2026-10-27 | None found | 43 D | | Microsoft Learn learn.microsoft.com | azure-cli pypi | 2.92.0 | 2026-11-03 | Verified | 24 F | | Mintlify mintlify.com | mint npm | 4.2.1201 | 2026-11-04 | Verified | 74 B | | Modal modal.com | modal pypi | 1.6.3 | 2026-10-27 | None found | 63 C | | Neon neon.com | neonctl npm | 8.18.0 | 2026-11-03 | Sign-in required | 88 A | | Prisma prisma.io | prisma npm | 8.0.0-rc.30 | 2026-11-03 | Sign-in required | 82 B | | Railway railway.com | @railway/cli npm | 5.71.0 | 2026-10-19 | Sign-in required | 89 A | One row needs a caution. The CLI on record for ngrok.com is the npm package `ngrok`, which its registry record describes as "node wrapper for ngrok", published from https://github.com/bubenshchykov/ngrok#readme and last updated on 2023-05-07. It is a third-party Node wrapper for ngrok, not ngrok's own CLI, and it stays in the count because the directory counts a package found by name. ## Why the two are counted together AgentReady.org, launched by Ora on 19 Oct 2026, requires an MCP server or a CLI, at least one, for the act layer; a public API with OpenAPI and WebMCP are SHOULDs. Ora is the publisher of that standard. A company can meet that line with a CLI alone, which is why the directory records both. The CLI column shows a package only where a source names one, so the CLI-only group is a floor. How to publish a CLI is in [the CLI guide](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/); how agents see the MCP side is in [the pick page for testing a server](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/cli-and-mcp/index.md) ## Sources - [npm registry, read for CLI packages](https://registry.npmjs.org/), read 4 November 2026 - [PyPI, read for CLI packages](https://pypi.org/), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [AgentReady.org launch post](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP head-to-heads: hosts, registries, standards | Agent MCP Directory" description: "23 head-to-heads on the act layer: MCP hosts, registries, gateways and the standards agents use, each with a sourced difference." canonical: https://agentmcpdirectory.com/compare site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Head-to-heads" --- # MCP head-to-heads: hosts, registries, standards | Agent MCP Directory > 23 head-to-heads on the act layer: MCP hosts, registries, gateways and the standards agents use, each with a sourced difference. Source: https://agentmcpdirectory.com/compare Site: Agent MCP Directory Last reviewed: 2026-11-04 # Head-to-heads 23 pairings: 16 between hosts, registries and gateways and 7 between standards and agent surfaces. Each page states one sourced difference and gives a verdict for the product engineer, the platform lead and the agent builder. Read on 4 November 2026. ## Hosts, registries and gateways | Pair | The difference | | --- | --- | | Cloudflare vs Vercel | Cloudflare ships its own OAuth authorization server library (Workers OAuth Provider v1, DCR and CIMD) and a portal product that fronts up to 80 servers; Vercel's mcp-handler verifies tokens and serves resource metadata but does not issue tokens, so you bring the authorization server. | | Smithery vs Glama | Smithery shut down its MCP Proxy and managed identity on 31 Oct 2026 after joining Arcade, and its listing URLs return 404; Glama still lists 115,804 servers and 40,288 remote connectors with grades, but its API needs a key and attribution. | | Composio vs Zapier MCP | Composio generates per-user MCP URLs, restricts tools with allowed_tools and bills per call (0.0003 USD on Pro); Zapier MCP serves one endpoint at mcp.zapier.com over 9,000+ apps and bills two plan tasks per successful call. | | Official MCP Registry vs GitHub MCP Registry | The official registry holds 56,677 latest entries published by anyone who proves a namespace; GitHub's registry lists 773 servers, 587 with a remote, with GitHub metadata such as stars and licence. | | Official MCP Registry vs Claude Connectors Directory | The official registry accepts any verified namespace with no review; the Claude Connectors Directory requires remote HTTPS, OAuth 2.0 for user data and readOnlyHint or destructiveHint on every tool, then scans and may review. | | GitHub MCP Registry vs Claude Connectors Directory | GitHub lists 773 servers with install buttons for developer tools; Anthropic lists 1,064 connectors that run inside Claude, with a portal submission and automated scan. | | Cloudflare vs Composio | Cloudflare hosts code you write and lets you run your own OAuth server; Composio hosts the tools and holds the app OAuth for toolkits it supports, generating a Connect Link per user. | | Vercel vs Mintlify MCP | Vercel runs whatever MCP server you write; Mintlify generates a docs search server automatically at /mcp with fixed tools and published rate limits. | | Apify MCP vs Browserbase MCP | Apify exposes thousands of Store Actors as tools and supports OAuth; Browserbase exposes six browser tools (navigate, act, observe, extract, start, end) with the API key in the URL. | | Cloudflare AI Gateway vs Vercel AI Gateway | Cloudflare charges a 5 percent fee on Unified Billing credits and gives caching free; Vercel charges no token markup and bills add-ons such as team-wide ZDR at 0.10 USD per 1,000 requests. | | Portkey vs Kong AI Gateway | Portkey's MCP Gateway provisions tools per user and logs each call with parameters; Kong turns existing APIs into MCP tools and applies OAuth2 strategies, with OpenTelemetry across AI, MCP and A2A. | | Portkey vs Cloudflare AI Gateway | Portkey fronts MCP servers through its MCP Gateway with credential injection; Cloudflare AI Gateway fronts model APIs while MCP servers go through MCP server portals. | | Zapier MCP vs Apify MCP | Zapier covers SaaS actions across 9,000+ apps with Zapier holding credentials; Apify covers web data through Actors and can take per-request payments via Skyfire on pay-per-event Actors. | | Smithery vs Official MCP Registry | Smithery published 213 hosted servers into the official registry under ai.smithery, all pointing at server.smithery.ai; the registry itself does not host or proxy anything. | | Glama vs Official MCP Registry | Glama grades servers A to F for licence, quality and maintenance; the official registry records only active or deprecated status. | | Composio vs Portkey | Composio both hosts tools and holds app credentials; Portkey sits in front of servers you or others host and injects credentials per server. | ## Standards and surfaces | Pair | The difference | | --- | --- | | MCP vs A2A | MCP connects an agent to tools, resources and prompts on a server; A2A connects agents to other agents through an Agent Card at /.well-known/agent-card.json and task messages over JSON-RPC, gRPC or HTTP+JSON. | | MCP vs WebMCP | MCP runs over stdio or Streamable HTTP to a server; WebMCP registers tools inside a web page through document.modelContext, so only an agent running in the browser can call them. | | WebMCP vs agents.json | WebMCP exposes JavaScript tools in the page at run time; agents.json is a static OpenAPI-based file at /.well-known/agents.json describing API flows. | | NLWeb vs MCP | NLWeb gives a site a natural-language ask method returning Schema.org JSON, and every NLWeb instance is also an MCP server; MCP alone defines no ask method or content vocabulary. | | Agent Skills vs MCP | Agent Skills are SKILL.md instructions loaded by progressive disclosure; MCP servers expose callable tools. Vendors such as Stripe ship both and configure them together. | | CLIs vs MCP | A CLI runs in the agent's terminal; an MCP server runs remotely with OAuth. Stripe, Vercel and Neon now use their CLIs to configure their MCP servers. | | OpenAPI vs MCP | OpenAPI describes endpoints for code generation; MCP serves tool descriptions written for models and handles auth discovery through RFC 9728 metadata. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/index.md) ## Sources - [Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [smithery.ai home page](https://smithery.ai/), read 4 November 2026 - [Composio pricing](https://composio.dev/pricing), read 4 November 2026 - [Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 4 November 2026 - [Claude connectors directory](https://claude.com/connectors), read 4 November 2026 - [Composio MCP quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Mintlify: Model Context Protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Browserbase MCP setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 - [Vercel AI Gateway pricing](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026 - [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 - [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Apify MCP server docs](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=ai.smithery), read 4 November 2026 - [Glama MCP servers directory](https://glama.ai/mcp/servers), read 4 November 2026 - [A2A specification](https://a2a-protocol.org/latest/specification/), read 4 November 2026 - [webmachinelearning/webmcp](https://github.com/webmachinelearning/webmcp), read 4 November 2026 - [wild-card-ai/agents-json](https://github.com/wild-card-ai/agents-json), read 4 November 2026 - [nlweb-ai/NLWeb](https://github.com/nlweb-ai/NLWeb), read 4 November 2026 - [Stripe MCP docs](https://docs.stripe.com/mcp), read 4 November 2026 - [Neon MCP server docs](https://neon.com/docs/ai/neon-mcp-server), read 4 November 2026 - [MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Agent Skills vs MCP | Agent MCP Directory" description: "Agent Skills vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/agent-skills-vs-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Agent Skills vs MCP | Agent MCP Directory > Agent Skills vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/agent-skills-vs-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # Agent Skills vs MCP Product engineer: Ship a skill to teach agents your workflow and an MCP server to let them act. Developer-platform lead: Skills are files; MCP needs hosting and auth. Agent builder: Load the skill, then call the tools it names. Agent Skills are SKILL.md instructions loaded by progressive disclosure. ## The sourced difference Agent Skills are SKILL.md instructions loaded by progressive disclosure; MCP servers expose callable tools. Vendors such as Stripe ship both and configure them together. (Agent Skills: [agentskills.io](https://agentskills.io/), read 5 November 2026; MCP: [modelcontextprotocol.io/specification/2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28), read 5 November 2026; Stripe: [Stripe MCP docs](https://docs.stripe.com/mcp), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Ship a skill to teach agents your workflow and an MCP server to let them act. | | Developer-platform lead | Skills are files; MCP needs hosting and auth. | | Agent builder | Load the skill, then call the tools it names. | ## Side by side | Aspect | Agent Skills | MCP | | --- | --- | --- | | Maintainer | agentskills.io open standard (originated at Anthropic) | MCP maintainers under the Agentic AI Foundation | | What it is | A folder with a SKILL.md file (name, description, instructions) plus optional scripts, references and assets that agents load on demand. | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | | Status and version | Open format with a published specification at agentskills.io; adopted across many agent clients. | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | | What it does not do | Does not execute anything by itself or expose remote tools; skills are instructions and files, often paired with an MCP server or CLI. | Does not grade servers, verify registry entries, or prescribe a .well-known discovery file in the 2026-07-28 core spec; server cards are still Working Group work. | Read the full entries: [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) and [MCP](https://agentmcpdirectory.com/standards/mcp/). ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/agent-skills/index.json | 53 of 7,435 (0.71%) | 144 of 3,364 (4.28%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/agent-skills-vs-mcp/index.md) ## Sources - [agentskills.io](https://agentskills.io/), read 5 November 2026 - [modelcontextprotocol.io/specification/2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28), read 5 November 2026 - [Stripe MCP docs](https://docs.stripe.com/mcp), read 5 November 2026 - [MCP specification or home](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Apify MCP vs Browserbase MCP | Agent MCP Directory" description: "Apify MCP vs Browserbase MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Apify MCP vs Browserbase MCP | Agent MCP Directory > Apify MCP vs Browserbase MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apify MCP vs Browserbase MCP Product engineer: Use Browserbase for interactive browsing; use Apify for ready-made scrapers. Developer-platform lead: Browserbase's key-in-URL auth needs log hygiene; Apify's OAuth avoids it. Agent builder: Apify's call-actor returns IDs, so plan a second call for results. Apify exposes thousands of Store Actors as tools and supports OAuth. ## The sourced difference Apify exposes thousands of Store Actors as tools and supports OAuth; Browserbase exposes six browser tools (navigate, act, observe, extract, start, end) with the API key in the URL. (Apify MCP: [Apify MCP server docs](https://docs.apify.com/platform/integrations/mcp), read 5 November 2026; Browserbase MCP: [Browserbase MCP setup](https://docs.browserbase.com/integrations/mcp/setup), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Use Browserbase for interactive browsing; use Apify for ready-made scrapers. | | Developer-platform lead | Browserbase's key-in-URL auth needs log hygiene; Apify's OAuth avoids it. | | Agent builder | Apify's call-actor returns IDs, so plan a second call for results. | ## Side by side on the rubric | Dimension | Apify MCP | Browserbase MCP | | --- | --- | --- | | Remote transport | Streamable HTTP and stdio | Streamable HTTP | | OAuth with client registration | OAuth | no, API key in URL | | Per-tool auth scoping | tools parameter selects Actors | no | | Hosting and scale limits | Actor run limits | not stated | | Observability | run status and storage IDs | session lifecycle tools | | Pricing | per Actor run | not stated on MCP pages | | Registry submission | Apify Store for Actors | not a registry | | Discoverability by agents | search-actors tool | docs only | | Own server in the registries | yes | listed without remote | Evidence for every cell is on the profiles: [Apify MCP](https://agentmcpdirectory.com/hosts/apify-mcp/) and [Browserbase MCP](https://agentmcpdirectory.com/hosts/browserbase/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase/index.md) ## Sources - [Apify MCP server docs](https://docs.apify.com/platform/integrations/mcp), read 5 November 2026 - [Browserbase MCP setup](https://docs.browserbase.com/integrations/mcp/setup), read 5 November 2026 - [Apify MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.apify%2Fapify-mcp-server), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/introduction](https://docs.browserbase.com/integrations/mcp/introduction), read 4 November 2026 - [Browserbase MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=browserbase), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CLIs vs MCP | Agent MCP Directory" description: "CLIs vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/cli-as-agent-surface-vs-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # CLIs vs MCP | Agent MCP Directory > CLIs vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/cli-as-agent-surface-vs-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # CLIs vs MCP Product engineer: A CLI is the cheaper first act surface for developer products. Developer-platform lead: AgentReady.org accepts either for the act-layer MUST. Agent builder: Coding agents use both; chat agents need MCP. A CLI runs in the agent's terminal; an MCP server runs remotely with OAuth. Stripe, Vercel and Neon now use their CLIs to configure their MCP servers. ## The sourced difference A CLI runs in the agent's terminal; an MCP server runs remotely with OAuth. Stripe, Vercel and Neon now use their CLIs to configure their MCP servers. (CLIs: [vercel.com/docs/cli](https://vercel.com/docs/cli), read 5 November 2026; MCP: [MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 5 November 2026; Stripe: [Stripe MCP docs](https://docs.stripe.com/mcp), read 5 November 2026; Vercel: [Vercel MCP docs](https://vercel.com/docs/agent-resources/vercel-mcp), read 5 November 2026; Neon: [Neon MCP server docs](https://neon.com/docs/ai/neon-mcp-server), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | A CLI is the cheaper first act surface for developer products. | | Developer-platform lead | AgentReady.org accepts either for the act-layer MUST. | | Agent builder | Coding agents use both; chat agents need MCP. | ## Side by side | Aspect | CLIs | MCP | | --- | --- | --- | | Maintainer | Each vendor | MCP maintainers under the Agentic AI Foundation | | What it is | A command-line tool, usually on npm, that an agent runs in a shell; the same questions apply to each: install path, auth without a browser, machine-readable output, and whether it configures MCP. | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | | Status and version | Common practice; AgentReady.org (launched 19 Oct 2026) lists "an MCP server or a CLI, at least one" as a MUST for the act layer. | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | | What it does not do | Does not help agents that cannot run a shell, such as chat-only assistants; output formats differ by vendor. | Does not grade servers, verify registry entries, or prescribe a .well-known discovery file in the 2026-07-28 core spec; server cards are still Working Group work. | Read the full entries: [CLIs](https://agentmcpdirectory.com/standards/cli-as-agent-surface/) and [MCP](https://agentmcpdirectory.com/standards/mcp/). ## Seen in the directory 36 companies in the directory have a CLI package on record, out of 1,336. The figure is a floor: a package is checked only where a source names it. See [the CLI guide](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/cli-as-agent-surface-vs-mcp/index.md) ## Sources - [vercel.com/docs/cli](https://vercel.com/docs/cli), read 5 November 2026 - [MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 5 November 2026 - [Stripe MCP docs](https://docs.stripe.com/mcp), read 5 November 2026 - [Vercel MCP docs](https://vercel.com/docs/agent-resources/vercel-mcp), read 5 November 2026 - [Neon MCP server docs](https://neon.com/docs/ai/neon-mcp-server), read 5 November 2026 - [CLIs specification or home](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=compare), read 4 November 2026 - [MCP specification or home](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudflare AI Gateway vs Vercel AI Gateway | Agent MCP Directory" description: "Cloudflare AI Gateway vs Vercel AI Gateway: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Cloudflare AI Gateway vs Vercel AI Gateway | Agent MCP Directory > Cloudflare AI Gateway vs Vercel AI Gateway: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudflare AI Gateway vs Vercel AI Gateway Product engineer: Both pass provider list prices; compare the add-ons you need. Developer-platform lead: Cloudflare requires auth on new gateways from 3 Nov 2026. Agent builder: Neither fronts MCP tool calls; that is a separate product on both platforms. Cloudflare charges a 5 percent fee on Unified Billing credits and gives caching free. ## The sourced difference Cloudflare charges a 5 percent fee on Unified Billing credits and gives caching free; Vercel charges no token markup and bills add-ons such as team-wide ZDR at 0.10 USD per 1,000 requests. (Cloudflare AI Gateway: [Cloudflare AI Gateway pricing](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 5 November 2026; Vercel AI Gateway: [Vercel AI Gateway pricing](https://vercel.com/docs/ai-gateway/pricing), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Both pass provider list prices; compare the add-ons you need. | | Developer-platform lead | Cloudflare requires auth on new gateways from 3 Nov 2026. | | Agent builder | Neither fronts MCP tool calls; that is a separate product on both platforms. | ## Side by side on the rubric | Dimension | Cloudflare AI Gateway | Vercel AI Gateway | | --- | --- | --- | | Protocols fronted | model APIs; MCP goes through portals | model APIs | | Auth passthrough | BYOK or Unified Billing | BYOK with system fallback | | Caching | yes, free | not on the pricing page | | Pricing | free core, 5 percent on credits | no markup, paid add-ons | | Observability | analytics and logs | budgets, reporting, trace drains | Evidence for every cell is on the profiles: [Cloudflare AI Gateway](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/) and [Vercel AI Gateway](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway/index.md) ## Sources - [Cloudflare AI Gateway pricing](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 5 November 2026 - [Vercel AI Gateway pricing](https://vercel.com/docs/ai-gateway/pricing), read 5 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Vercel AI Gateway: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudflare vs Composio | Agent MCP Directory" description: "Cloudflare vs Composio: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/cloudflare-vs-composio site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Cloudflare vs Composio | Agent MCP Directory > Cloudflare vs Composio: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/cloudflare-vs-composio Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudflare vs Composio Product engineer: Write your own server on Cloudflare when the API is yours; use Composio when you call other companies' APIs. Developer-platform lead: Composio adds per-call cost; Cloudflare adds code you own. Agent builder: Composio is quicker for third-party SaaS tools. ## The sourced difference Cloudflare hosts code you write and lets you run your own OAuth server; Composio hosts the tools and holds the app OAuth for toolkits it supports, generating a Connect Link per user. (Cloudflare: [Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 5 November 2026; Composio: [docs.composio.dev/docs/authentication](https://docs.composio.dev/docs/authentication), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Write your own server on Cloudflare when the API is yours; use Composio when you call other companies' APIs. | | Developer-platform lead | Composio adds per-call cost; Cloudflare adds code you own. | | Agent builder | Composio is quicker for third-party SaaS tools. | ## Side by side on the rubric | Dimension | Cloudflare | Composio | | --- | --- | --- | | Remote transport | Streamable HTTP only | HTTP | | OAuth with client registration | yes, DCR and CIMD | Composio holds app OAuth | | Per-tool auth scoping | yes, at the portal | yes, allowed_tools | | Hosting and scale limits | 80 servers per portal | 2,000 to 10,000 requests a minute | | Observability | Access logs, API analytics, Logpush on Enterprise | not detailed on these pages | | Pricing | not published for MCP | 0 / 29 USD / custom | | Registry submission | not a registry | not a registry | | Discoverability by agents | portal endpoint, no public catalog | session-based tool discovery | | Own server in the registries | yes | yes | Evidence for every cell is on the profiles: [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/) and [Composio](https://agentmcpdirectory.com/hosts/composio/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/cloudflare-vs-composio/index.md) ## Sources - [Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 5 November 2026 - [docs.composio.dev/docs/authentication](https://docs.composio.dev/docs/authentication), read 5 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/agents/guides/remote-mcp-server](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026 - [Cloudflare: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.cloudflare.mcp%2Fmcp), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Composio: composio.dev/pricing](https://composio.dev/pricing), read 4 November 2026 - [Composio: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.ComposioHQ%2Fcomposio), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudflare vs Vercel | Agent MCP Directory" description: "Cloudflare vs Vercel: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/cloudflare-vs-vercel site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Cloudflare vs Vercel | Agent MCP Directory > Cloudflare vs Vercel: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/cloudflare-vs-vercel Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudflare vs Vercel Product engineer: Pick Cloudflare if you need to issue tokens yourself; pick Vercel if you already run Next.js and have an identity provider. Developer-platform lead: Cloudflare adds a central portal with per-tool controls; Vercel leaves central control to your code and firewall. ## The sourced difference Cloudflare ships its own OAuth authorization server library (Workers OAuth Provider v1, DCR and CIMD) and a portal product that fronts up to 80 servers; Vercel's mcp-handler verifies tokens and serves resource metadata but does not issue tokens, so you bring the authorization server. (Cloudflare: [Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 5 November 2026 and [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 5 November 2026; Vercel: [Vercel: deploy MCP servers to Vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Pick Cloudflare if you need to issue tokens yourself; pick Vercel if you already run Next.js and have an identity provider. | | Developer-platform lead | Cloudflare adds a central portal with per-tool controls; Vercel leaves central control to your code and firewall. | | Agent builder | Both serve Streamable HTTP only, so either works with current clients. | ## Side by side on the rubric | Dimension | Cloudflare | Vercel | | --- | --- | --- | | Remote transport | Streamable HTTP only | Streamable HTTP only | | OAuth with client registration | yes, DCR and CIMD | bring your own AS; CIMD on Vercel MCP | | Per-tool auth scoping | yes, at the portal | scopes per handler | | Hosting and scale limits | 80 servers per portal | Vercel Functions limits | | Observability | Access logs, API analytics, Logpush on Enterprise | platform logs, rollbacks, rolling releases | | Pricing | not published for MCP | Functions pricing | | Registry submission | not a registry | not a registry | | Discoverability by agents | portal endpoint, no public catalog | none built in | | Own server in the registries | yes | yes | Evidence for every cell is on the profiles: [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/) and [Vercel](https://agentmcpdirectory.com/hosts/vercel/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/cloudflare-vs-vercel/index.md) ## Sources - [Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 5 November 2026 - [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 5 November 2026 - [Vercel: deploy MCP servers to Vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 5 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/agents/guides/remote-mcp-server](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026 - [Cloudflare: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.cloudflare.mcp%2Fmcp), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Vercel: vercel.com/docs/agent-resources/vercel-mcp](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 - [Vercel: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.vercel%2Fvercel-mcp), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Composio vs Portkey | Agent MCP Directory" description: "Composio vs Portkey: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/composio-vs-portkey site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Composio vs Portkey | Agent MCP Directory > Composio vs Portkey: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/composio-vs-portkey Site: Agent MCP Directory Last reviewed: 2026-11-05 # Composio vs Portkey Product engineer: Composio when you lack the tools; Portkey when you have them and need control. Developer-platform lead: Portkey adds central logs; Composio adds managed auth. Agent builder: Both scope tools per user or per server. Composio both hosts tools and holds app credentials; Portkey sits in front of servers you or others host and injects credentials per server. ## The sourced difference Composio both hosts tools and holds app credentials; Portkey sits in front of servers you or others host and injects credentials per server. (Composio: [Composio MCP quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 5 November 2026; Portkey: [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Composio when you lack the tools; Portkey when you have them and need control. | | Developer-platform lead | Portkey adds central logs; Composio adds managed auth. | | Agent builder | Both scope tools per user or per server. | ## Side by side on the rubric | Dimension | Composio | Portkey | | --- | --- | --- | | Remote transport | HTTP | not read | | OAuth with client registration | Composio holds app OAuth | not read | | Per-tool auth scoping | yes, allowed_tools | not read | | Hosting and scale limits | 2,000 to 10,000 requests a minute | not read | | Observability | not detailed on these pages | per tool call logs | | Pricing | 0 / 29 USD / custom | free / 49 USD / custom | | Registry submission | not a registry | not read | | Discoverability by agents | session-based tool discovery | not read | | Own server in the registries | yes | not read | Evidence for every cell is on the profiles: [Composio](https://agentmcpdirectory.com/hosts/composio/) and [Portkey](https://agentmcpdirectory.com/hosts/portkey/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/composio-vs-portkey/index.md) ## Sources - [Composio MCP quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 5 November 2026 - [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026 - [Composio: composio.dev/pricing](https://composio.dev/pricing), read 4 November 2026 - [Composio: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.ComposioHQ%2Fcomposio), read 4 November 2026 - [Portkey: portkey.ai/pricing](https://portkey.ai/pricing), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Composio vs Zapier MCP | Agent MCP Directory" description: "Composio vs Zapier MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Composio vs Zapier MCP | Agent MCP Directory > Composio vs Zapier MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # Composio vs Zapier MCP Product engineer: Composio fits a product that embeds tools for its own users; Zapier fits internal automation on an existing Zapier plan. Developer-platform lead: Composio's per-call metering is easier to forecast at volume than task quotas. Agent builder: Zapier's agentic mode finds actions at run time; Composio recommends sessions for dynamic tools. ## The sourced difference Composio generates per-user MCP URLs, restricts tools with allowed\_tools and bills per call (0.0003 USD on Pro); Zapier MCP serves one endpoint at mcp.zapier.com over 9,000+ apps and bills two plan tasks per successful call. (Composio: [Composio MCP quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 5 November 2026 and [Composio pricing](https://composio.dev/pricing), read 5 November 2026; Zapier MCP: [Zapier MCP docs](https://docs.zapier.com/mcp/home), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Composio fits a product that embeds tools for its own users; Zapier fits internal automation on an existing Zapier plan. | | Developer-platform lead | Composio's per-call metering is easier to forecast at volume than task quotas. | | Agent builder | Zapier's agentic mode finds actions at run time; Composio recommends sessions for dynamic tools. | ## Side by side on the rubric | Dimension | Composio | Zapier MCP | | --- | --- | --- | | Remote transport | HTTP | Streamable HTTP only | | OAuth with client registration | Composio holds app OAuth | OAuth for clients | | Per-tool auth scoping | yes, allowed_tools | yes, app and action level | | Hosting and scale limits | 2,000 to 10,000 requests a minute | task quota | | Observability | not detailed on these pages | History log of every MCP action | | Pricing | 0 / 29 USD / custom | included, tasks per call | | Registry submission | not a registry | not a registry | | Discoverability by agents | session-based tool discovery | agentic mode | | Own server in the registries | yes | yes | Evidence for every cell is on the profiles: [Composio](https://agentmcpdirectory.com/hosts/composio/) and [Zapier MCP](https://agentmcpdirectory.com/hosts/zapier-mcp/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp/index.md) ## Sources - [Composio MCP quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 5 November 2026 - [Composio pricing](https://composio.dev/pricing), read 5 November 2026 - [Zapier MCP docs](https://docs.zapier.com/mcp/home), read 5 November 2026 - [Composio: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.ComposioHQ%2Fcomposio), read 4 November 2026 - [Zapier MCP: zapier.com/mcp](https://zapier.com/mcp), read 4 November 2026 - [Zapier MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.zapier%2Fmcp), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GitHub MCP Registry vs Claude Connectors | Agent MCP Directory" description: "GitHub MCP Registry vs Claude Connectors Directory: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # GitHub MCP Registry vs Claude Connectors | Agent MCP Directory > GitHub MCP Registry vs Claude Connectors Directory: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory Site: Agent MCP Directory Last reviewed: 2026-11-05 # GitHub MCP Registry vs Claude Connectors Directory Product engineer: Go where your users are: IDE users through GitHub, chat users through Claude. Developer-platform lead: Two separate submissions; neither feeds the other. Agent builder: Both expose remote endpoints you can call from any client. GitHub lists 773 servers with install buttons for developer tools; Anthropic lists 1,064 connectors that run inside Claude. ## The sourced difference GitHub lists 773 servers with install buttons for developer tools; Anthropic lists 1,064 connectors that run inside Claude, with a portal submission and automated scan. (GitHub MCP Registry: [GitHub MCP Registry](https://github.com/mcp), counted on 4 November 2026; Claude Connectors Directory: [Claude connectors directory](https://claude.com/connectors), counted on 4 November 2026 and [Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Go where your users are: IDE users through GitHub, chat users through Claude. | | Developer-platform lead | Two separate submissions; neither feeds the other. | | Agent builder | Both expose remote endpoints you can call from any client. | ## Side by side on the rubric | Dimension | GitHub MCP Registry | Claude Connectors Directory | | --- | --- | --- | | Remote transport | records remotes | remote HTTPS required | | OAuth with client registration | not applicable | OAuth 2.0 required for user data | | Per-tool auth scoping | not applicable | annotations required | | Hosting and scale limits | not a host | not a host | | Observability | Copilot usage metrics count MCP servers | health and usage metrics after publication | | Pricing | free | paid Claude plan to submit | | Registry submission | not documented on the page | portal, automated scan, optional human review | | Discoverability by agents | open API and install buttons | inside Claude | | Own server in the registries | yes | docs server listed | Evidence for every cell is on the profiles: [GitHub MCP Registry](https://agentmcpdirectory.com/hosts/github-mcp-registry/) and [Claude Connectors Directory](https://agentmcpdirectory.com/hosts/claude-connectors-directory/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory/index.md) ## Sources - [GitHub MCP Registry](https://github.com/mcp), read 4 November 2026 (Figure read on the github.com page on 4 November 2026.) - [Claude connectors directory](https://claude.com/connectors), read 4 November 2026 (Figure read on the claude.com page on 4 November 2026.) - [Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 5 November 2026 - [GitHub MCP Registry: api.mcp.github.com/v0/servers](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [GitHub MCP Registry: github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), read 4 November 2026 - [GitHub MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.github%2Fgithub-mcp-server), read 4 November 2026 - [Claude Connectors Directory: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.claude.platform%2Fdocs), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Glama vs Official MCP Registry | Agent MCP Directory" description: "Glama vs Official MCP Registry: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Head-to-heads" --- # Glama vs Official MCP Registry | Agent MCP Directory > Glama vs Official MCP Registry: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry Site: Agent MCP Directory Last reviewed: 2026-11-04 # Glama vs Official MCP Registry Product engineer: Use Glama grades as a hint, since the page does not explain the method. Developer-platform lead: The registry is the neutral source; Glama adds opinion. Agent builder: Neither confirms a server works today; connect and list tools. Glama grades servers A to F for licence, quality and maintenance; the official registry records only active or deprecated status. ## The sourced difference Glama grades servers A to F for licence, quality and maintenance; the official registry records only active or deprecated status. (Glama: [Glama MCP servers directory](https://glama.ai/mcp/servers), observed on 4 November 2026; Official MCP Registry: [Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), observed on 4 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Use Glama grades as a hint, since the page does not explain the method. | | Developer-platform lead | The registry is the neutral source; Glama adds opinion. | | Agent builder | Neither confirms a server works today; connect and list tools. | ## Side by side on the rubric | Dimension | Glama | Official MCP Registry | | --- | --- | --- | | Remote transport | lists both | records both | | OAuth with client registration | filter only | not applicable | | Per-tool auth scoping | not documented | not applicable | | Hosting and scale limits | not published | not a host | | Observability | health status on listings | not applicable | | Pricing | not detailed | free | | Registry submission | open, Add Server button | CLI with namespace verification | | Discoverability by agents | API with key and attribution | open paginated API | | Own server in the registries | not found | not applicable | Evidence for every cell is on the profiles: [Glama](https://agentmcpdirectory.com/hosts/glama/) and [Official MCP Registry](https://agentmcpdirectory.com/hosts/official-mcp-registry/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry/index.md) ## Sources - [Glama MCP servers directory](https://glama.ai/mcp/servers), read 4 November 2026 (Fact noted from the glama.ai page on 4 November 2026.) - [Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 (Fact noted from the registry API at registry.modelcontextprotocol.io on 4 November 2026.) - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [Glama: glama.ai/pricing](https://glama.ai/pricing), read 4 November 2026 - [Official MCP Registry: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP vs A2A | Agent MCP Directory" description: "MCP vs A2A: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/mcp-vs-a2a site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # MCP vs A2A | Agent MCP Directory > MCP vs A2A: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/mcp-vs-a2a Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP vs A2A Product engineer: Expose your product with MCP first; add A2A only if you ship an agent others delegate to. Developer-platform lead: Both now sit in the Agentic AI Foundation. Agent builder: Use MCP for tools and A2A for handing work to another agent. ## The sourced difference MCP connects an agent to tools, resources and prompts on a server; A2A connects agents to other agents through an Agent Card at /.well-known/agent-card.json and task messages over JSON-RPC, gRPC or HTTP+JSON. (MCP: [Model Context Protocol specification (latest, 2026-07-28)](https://modelcontextprotocol.io/specification/latest), read 5 November 2026; A2A: [A2A specification](https://a2a-protocol.org/latest/specification/), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Expose your product with MCP first; add A2A only if you ship an agent others delegate to. | | Developer-platform lead | Both now sit in the Agentic AI Foundation. | | Agent builder | Use MCP for tools and A2A for handing work to another agent. | ## Side by side | Aspect | MCP | A2A | | --- | --- | --- | | Maintainer | MCP maintainers under the Agentic AI Foundation | A2A project, Growth Stage project at the Agentic AI Foundation (Linux Foundation-directed) | | What it is | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | A protocol for agents to discover each other through an Agent Card and exchange tasks and messages. | | Status and version | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | Specification 1.0.0 is the latest release; joined the Agentic AI Foundation on 27 Aug 2026. | | What it does not do | Does not grade servers, verify registry entries, or prescribe a .well-known discovery file in the 2026-07-28 core spec; server cards are still Working Group work. | Does not define how an agent calls a plain API or a web page; it covers agent-to-agent tasks, not tool access. | Read the full entries: [MCP](https://agentmcpdirectory.com/standards/mcp/) and [A2A](https://agentmcpdirectory.com/standards/a2a/). ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/agent-card.json | 10 of 7,470 (0.13%) | 48 of 3,368 (1.43%) | | /.well-known/agent.json | 6 of 7,461 (0.08%) | 14 of 3,366 (0.42%) | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/mcp-vs-a2a/index.md) ## Sources - [Model Context Protocol specification (latest, 2026-07-28)](https://modelcontextprotocol.io/specification/latest), read 5 November 2026 - [A2A specification](https://a2a-protocol.org/latest/specification/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP vs WebMCP | Agent MCP Directory" description: "MCP vs WebMCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/mcp-vs-webmcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # MCP vs WebMCP | Agent MCP Directory > MCP vs WebMCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/mcp-vs-webmcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP vs WebMCP Product engineer: Ship an MCP server for API work; add WebMCP on pages where the user is present. Developer-platform lead: WebMCP is a draft in origin trial; MCP has dated spec revisions. Agent builder: WebMCP tools need a browser agent; most chat clients reach MCP servers instead. ## The sourced difference MCP runs over stdio or Streamable HTTP to a server; WebMCP registers tools inside a web page through document.modelContext, so only an agent running in the browser can call them. (MCP: [MCP transports overview, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 5 November 2026; WebMCP: [webmachinelearning/webmcp](https://github.com/webmachinelearning/webmcp), read 5 November 2026 and [Cloudflare changelog: Browser Run adds WebMCP to Kitesurf, moves to document.modelContext (28 Sep 2026)](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Ship an MCP server for API work; add WebMCP on pages where the user is present. | | Developer-platform lead | WebMCP is a draft in origin trial; MCP has dated spec revisions. | | Agent builder | WebMCP tools need a browser agent; most chat clients reach MCP servers instead. | ## Side by side | Aspect | MCP | WebMCP | | --- | --- | --- | | Maintainer | MCP maintainers under the Agentic AI Foundation | W3C Web Machine Learning Community Group (editors from Microsoft and Google) | | What it is | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | A browser API that lets a page register JavaScript functions as tools, with descriptions and schemas, that an in-browser agent can call. | | Status and version | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | Draft specification; Chrome and Edge test it in an origin trial, Brave behind a flag, no Firefox or Safari implementation (nekuda FAQ, October 2026). | | What it does not do | Does not grade servers, verify registry entries, or prescribe a .well-known discovery file in the 2026-07-28 core spec; server cards are still Working Group work. | Does not work without a browser agent that reads the page; does not replace a server-side MCP endpoint; the declarative form-based API is only being explored. | Read the full entries: [MCP](https://agentmcpdirectory.com/standards/mcp/) and [WebMCP](https://agentmcpdirectory.com/standards/webmcp/). ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). The shared crawl looks for WebMCP in the initial HTML of each home page. It found a WebMCP hint on 25 of 7,545 home pages in the Tranco top 10,000 and on 59 of 3,393 on Ora's leaderboard. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/mcp-vs-webmcp/index.md) ## Sources - [MCP transports overview, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 5 November 2026 - [webmachinelearning/webmcp](https://github.com/webmachinelearning/webmcp), read 5 November 2026 - [Cloudflare changelog: Browser Run adds WebMCP to Kitesurf, moves to document.modelContext (28 Sep 2026)](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 5 November 2026 - [MCP specification or home](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "NLWeb vs MCP | Agent MCP Directory" description: "NLWeb vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/nlweb-vs-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # NLWeb vs MCP | Agent MCP Directory > NLWeb vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/nlweb-vs-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # NLWeb vs MCP Product engineer: NLWeb fits content-heavy sites that want question answering over their catalog. Developer-platform lead: NLWeb is one implementation; MCP is the protocol under it. Agent builder: Call NLWeb sites through their MCP side. NLWeb gives a site a natural-language ask method returning Schema.org JSON, and every NLWeb instance is also an MCP server. ## The sourced difference NLWeb gives a site a natural-language ask method returning Schema.org JSON, and every NLWeb instance is also an MCP server; MCP alone defines no ask method or content vocabulary. (NLWeb: [nlweb-ai/NLWeb](https://github.com/nlweb-ai/NLWeb), read 5 November 2026; MCP: [modelcontextprotocol.io/specification/2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | NLWeb fits content-heavy sites that want question answering over their catalog. | | Developer-platform lead | NLWeb is one implementation; MCP is the protocol under it. | | Agent builder | Call NLWeb sites through their MCP side. | ## Side by side | Aspect | NLWeb | MCP | | --- | --- | --- | | Maintainer | Microsoft (repository nlweb-ai/NLWeb) | MCP maintainers under the Agentic AI Foundation | | What it is | Open protocols and a Python reference implementation for conversational interfaces on websites, returning Schema.org JSON; every instance is also an MCP server. | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | | Status and version | Active open-source project, MIT licence, about 6.3k stars; no tagged releases shown on 4 Nov 2026. | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | | What it does not do | Does not document fixed /ask or /mcp URL paths on the repository page; CI/CD pipelines are not included. | Does not grade servers, verify registry entries, or prescribe a .well-known discovery file in the 2026-07-28 core spec; server cards are still Working Group work. | Read the full entries: [NLWeb](https://agentmcpdirectory.com/standards/nlweb/) and [MCP](https://agentmcpdirectory.com/standards/mcp/). ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/nlweb-vs-mcp/index.md) ## Sources - [nlweb-ai/NLWeb](https://github.com/nlweb-ai/NLWeb), read 5 November 2026 - [modelcontextprotocol.io/specification/2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28), read 5 November 2026 - [MCP specification or home](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Official MCP Registry vs Claude Connectors | Agent MCP Directory" description: "Official MCP Registry vs Claude Connectors Directory: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Official MCP Registry vs Claude Connectors | Agent MCP Directory > Official MCP Registry vs Claude Connectors Directory: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory Site: Agent MCP Directory Last reviewed: 2026-11-05 # Official MCP Registry vs Claude Connectors Directory Product engineer: Annotate every tool before you submit to Claude. Developer-platform lead: The Claude directory is a distribution channel with review; the registry is metadata. Agent builder: Claude-listed connectors have annotated tools, which helps approval prompts. The official registry accepts any verified namespace with no review; the Claude Connectors Directory requires remote HTTPS. ## The sourced difference The official registry accepts any verified namespace with no review; the Claude Connectors Directory requires remote HTTPS, OAuth 2.0 for user data and readOnlyHint or destructiveHint on every tool, then scans and may review. (Official MCP Registry: [modelcontextprotocol/registry on GitHub](https://github.com/modelcontextprotocol/registry), read 5 November 2026; Claude Connectors Directory: [Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Annotate every tool before you submit to Claude. | | Developer-platform lead | The Claude directory is a distribution channel with review; the registry is metadata. | | Agent builder | Claude-listed connectors have annotated tools, which helps approval prompts. | ## Side by side on the rubric | Dimension | Official MCP Registry | Claude Connectors Directory | | --- | --- | --- | | Remote transport | records both | remote HTTPS required | | OAuth with client registration | not applicable | OAuth 2.0 required for user data | | Per-tool auth scoping | not applicable | annotations required | | Hosting and scale limits | not a host | not a host | | Observability | not applicable | health and usage metrics after publication | | Pricing | free | paid Claude plan to submit | | Registry submission | CLI with namespace verification | portal, automated scan, optional human review | | Discoverability by agents | open paginated API | inside Claude | | Own server in the registries | not applicable | docs server listed | Evidence for every cell is on the profiles: [Official MCP Registry](https://agentmcpdirectory.com/hosts/official-mcp-registry/) and [Claude Connectors Directory](https://agentmcpdirectory.com/hosts/claude-connectors-directory/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory/index.md) ## Sources - [modelcontextprotocol/registry on GitHub](https://github.com/modelcontextprotocol/registry), read 5 November 2026 - [Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 5 November 2026 - [Official MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Claude Connectors Directory: claude.com/connectors](https://claude.com/connectors), read 4 November 2026 - [Claude Connectors Directory: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.claude.platform%2Fdocs), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Official MCP Registry vs GitHub MCP Registry | Agent MCP Directory" description: "Official MCP Registry vs GitHub MCP Registry: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Official MCP Registry vs GitHub MCP Registry | Agent MCP Directory > Official MCP Registry vs GitHub MCP Registry: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry Site: Agent MCP Directory Last reviewed: 2026-11-05 # Official MCP Registry vs GitHub MCP Registry Product engineer: Publish to the official registry first; it is the source others read. Developer-platform lead: Treat GitHub's list as curated reach inside VS Code and Copilot, not as the registry of record. Agent builder: Query the official API for breadth and GitHub's for a short list with repo metadata. ## The sourced difference The official registry holds 56,677 latest entries published by anyone who proves a namespace; GitHub's registry lists 773 servers, 587 with a remote, with GitHub metadata such as stars and licence. (Official MCP Registry: [Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), counted on 4 November 2026 and [modelcontextprotocol/registry on GitHub](https://github.com/modelcontextprotocol/registry), read 5 November 2026; GitHub MCP Registry: [GitHub MCP Registry API, GET /v0/servers](https://api.mcp.github.com/v0/servers), counted on 4 November 2026 and [GitHub MCP Registry API, GET /v0/servers](https://api.mcp.github.com/v0/servers), observed on 4 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Publish to the official registry first; it is the source others read. | | Developer-platform lead | Treat GitHub's list as curated reach inside VS Code and Copilot, not as the registry of record. | | Agent builder | Query the official API for breadth and GitHub's for a short list with repo metadata. | ## Side by side on the rubric | Dimension | Official MCP Registry | GitHub MCP Registry | | --- | --- | --- | | Remote transport | records both | records remotes | | OAuth with client registration | not applicable | not applicable | | Per-tool auth scoping | not applicable | not applicable | | Hosting and scale limits | not a host | not a host | | Observability | not applicable | Copilot usage metrics count MCP servers | | Pricing | free | free | | Registry submission | CLI with namespace verification | not documented on the page | | Discoverability by agents | open paginated API | open API and install buttons | | Own server in the registries | not applicable | yes | Evidence for every cell is on the profiles: [Official MCP Registry](https://agentmcpdirectory.com/hosts/official-mcp-registry/) and [GitHub MCP Registry](https://agentmcpdirectory.com/hosts/github-mcp-registry/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry/index.md) ## Sources - [Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 (Count taken from the registry API at registry.modelcontextprotocol.io on 4 November 2026.) - [modelcontextprotocol/registry on GitHub](https://github.com/modelcontextprotocol/registry), read 5 November 2026 - [GitHub MCP Registry API, GET /v0/servers](https://api.mcp.github.com/v0/servers), read 4 November 2026 (Count taken from the registry API at api.mcp.github.com on 4 November 2026.) - [GitHub MCP Registry: github.com/mcp](https://github.com/mcp), read 4 November 2026 - [GitHub MCP Registry: github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), read 4 November 2026 - [GitHub MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.github%2Fgithub-mcp-server), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpenAPI vs MCP | Agent MCP Directory" description: "OpenAPI vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/openapi-as-agent-surface-vs-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # OpenAPI vs MCP | Agent MCP Directory > OpenAPI vs MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/openapi-as-agent-surface-vs-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenAPI vs MCP Product engineer: Keep the OpenAPI file and link it; agents reach it through links (Ora lab, 8 Oct 2026). Developer-platform lead: An OpenAPI file can seed MCP tools through gateways such as Kong. Agent builder: MCP gives you auth discovery; OpenAPI does not. ## The sourced difference OpenAPI describes endpoints for code generation; MCP serves tool descriptions written for models and handles auth discovery through RFC 9728 metadata. (OpenAPI: [OpenAPI Specification (latest)](https://spec.openapis.org/oas/latest.html), read 5 November 2026; MCP: [MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Keep the OpenAPI file and link it; agents reach it through links (Ora lab, 8 Oct 2026). | | Developer-platform lead | An OpenAPI file can seed MCP tools through gateways such as Kong. | | Agent builder | MCP gives you auth discovery; OpenAPI does not. | ## Side by side | Aspect | OpenAPI | MCP | | --- | --- | --- | | Maintainer | OpenAPI Initiative (spec); each vendor for its own file | MCP maintainers under the Agentic AI Foundation | | What it is | A machine-readable description of an HTTP API that agents and tool generators read to call endpoints without an MCP server. | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | | Status and version | OpenAPI 3.x in wide use; agents.json and Kong's AI MCP Server build on it. | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | | What it does not do | Does not carry agent auth flows or tool descriptions written for models; agents must find the file, usually through a link. | Does not grade servers, verify registry entries, or prescribe a .well-known discovery file in the 2026-07-28 core spec; server cards are still Working Group work. | Read the full entries: [OpenAPI](https://agentmcpdirectory.com/standards/openapi-as-agent-surface/) and [MCP](https://agentmcpdirectory.com/standards/mcp/). ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /openapi.json | 21 of 7,472 (0.28%) | 78 of 3,369 (2.32%) | | /openapi.yaml | 10 of 7,503 (0.13%) | 22 of 3,378 (0.65%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/openapi-as-agent-surface-vs-mcp/index.md) ## Sources - [OpenAPI Specification (latest)](https://spec.openapis.org/oas/latest.html), read 5 November 2026 - [MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 5 November 2026 - [OpenAPI specification or home](https://github.com/wild-card-ai/agents-json), read 4 November 2026 - [MCP specification or home](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Portkey vs Cloudflare AI Gateway | Agent MCP Directory" description: "Portkey vs Cloudflare AI Gateway: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Portkey vs Cloudflare AI Gateway | Agent MCP Directory > Portkey vs Cloudflare AI Gateway: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway Site: Agent MCP Directory Last reviewed: 2026-11-05 # Portkey vs Cloudflare AI Gateway Product engineer: One vendor for models and tools: Portkey; separate products: Cloudflare. Developer-platform lead: Cloudflare portals cap at 80 servers each. Agent builder: Both log tool calls; Cloudflare via Access, Portkey per user. Portkey fronts MCP servers through its MCP Gateway with credential injection; Cloudflare AI Gateway fronts model APIs while MCP servers go through MCP server portals. ## The sourced difference Portkey fronts MCP servers through its MCP Gateway with credential injection; Cloudflare AI Gateway fronts model APIs while MCP servers go through MCP server portals. (Portkey: [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026; Cloudflare AI Gateway: [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | One vendor for models and tools: Portkey; separate products: Cloudflare. | | Developer-platform lead | Cloudflare portals cap at 80 servers each. | | Agent builder | Both log tool calls; Cloudflare via Access, Portkey per user. | ## Side by side on the rubric | Dimension | Portkey | Cloudflare AI Gateway | | --- | --- | --- | | Protocols fronted | model APIs and MCP | model APIs; MCP goes through portals | | Auth passthrough | credential injection | BYOK or Unified Billing | | Caching | simple cache, 1-day TTL on Developer | yes, free | | Pricing | free / 49 USD / custom | free core, 5 percent on credits | | Observability | per tool call logs | analytics and logs | Evidence for every cell is on the profiles: [Portkey](https://agentmcpdirectory.com/hosts/portkey/) and [Cloudflare AI Gateway](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway/index.md) ## Sources - [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026 - [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 5 November 2026 - [Portkey: portkey.ai/pricing](https://portkey.ai/pricing), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/ai-gateway/reference/pricing](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Portkey vs Kong AI Gateway | Agent MCP Directory" description: "Portkey vs Kong AI Gateway: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Portkey vs Kong AI Gateway | Agent MCP Directory > Portkey vs Kong AI Gateway: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway Site: Agent MCP Directory Last reviewed: 2026-11-05 # Portkey vs Kong AI Gateway Product engineer: Kong suits teams that already run Kong for APIs. Developer-platform lead: Portkey publishes prices (49 USD a month Production); Kong's overview page does not. Agent builder: Portkey's per-user tool provisioning maps well to agents acting for many users. ## The sourced difference Portkey's MCP Gateway provisions tools per user and logs each call with parameters; Kong turns existing APIs into MCP tools and applies OAuth2 strategies, with OpenTelemetry across AI, MCP and A2A. (Portkey: [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026; Kong AI Gateway: [Kong AI Gateway docs](https://developer.konghq.com/ai-gateway/), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Kong suits teams that already run Kong for APIs. | | Developer-platform lead | Portkey publishes prices (49 USD a month Production); Kong's overview page does not. | | Agent builder | Portkey's per-user tool provisioning maps well to agents acting for many users. | ## Side by side on the rubric | Dimension | Portkey | Kong AI Gateway | | --- | --- | --- | | Protocols fronted | model APIs and MCP | model APIs, MCP, A2A | | Auth passthrough | credential injection | OAuth2 auth strategies | | Caching | simple cache, 1-day TTL on Developer | semantic cache | | Pricing | free / 49 USD / custom | not published on the docs page | | Observability | per tool call logs | OpenTelemetry, Konnect dashboards, audit logs | Evidence for every cell is on the profiles: [Portkey](https://agentmcpdirectory.com/hosts/portkey/) and [Kong AI Gateway](https://agentmcpdirectory.com/hosts/kong-ai-gateway/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway/index.md) ## Sources - [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026 - [Kong AI Gateway docs](https://developer.konghq.com/ai-gateway/), read 5 November 2026 - [Portkey: portkey.ai/pricing](https://portkey.ai/pricing), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Smithery vs Glama | Agent MCP Directory" description: "Smithery vs Glama: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/smithery-vs-glama site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Smithery vs Glama | Agent MCP Directory > Smithery vs Glama: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/smithery-vs-glama Site: Agent MCP Directory Last reviewed: 2026-11-05 # Smithery vs Glama Product engineer: Use Glama to check whether your server is listed and graded. Developer-platform lead: Do not plan new hosting on Smithery; Glama's data license affects reuse. Agent builder: Glama's connector filters (No Auth, OAuth 2.0, health) are the faster way to find a working remote. ## The sourced difference Smithery shut down its MCP Proxy and managed identity on 31 Oct 2026 after joining Arcade, and its listing URLs return 404; Glama still lists 115,804 servers and 40,288 remote connectors with grades, but its API needs a key and attribution. (Smithery: [smithery.ai home page](https://smithery.ai/), read 5 November 2026 and [Arcade: Smithery is now part of Arcade.dev (5 Aug 2026)](https://www.arcade.dev/blog/smithery-joins-arcade), read 5 November 2026; Glama: [Glama MCP servers directory](https://glama.ai/mcp/servers), counted on 4 November 2026 and [Glama MCP connectors (remote servers)](https://glama.ai/mcp/connectors), counted on 4 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Use Glama to check whether your server is listed and graded. | | Developer-platform lead | Do not plan new hosting on Smithery; Glama's data license affects reuse. | | Agent builder | Glama's connector filters (No Auth, OAuth 2.0, health) are the faster way to find a working remote. | ## Side by side on the rubric | Dimension | Smithery | Glama | | --- | --- | --- | | Remote transport | Streamable HTTP (registry entries) | lists both | | OAuth with client registration | managed identity retired | filter only | | Per-tool auth scoping | not documented | not documented | | Hosting and scale limits | proxy retired | not published | | Observability | not documented | health status on listings | | Pricing | not published | not detailed | | Registry submission | unclear after acquisition | open, Add Server button | | Discoverability by agents | catalog browse only | API with key and attribution | | Own server in the registries | no own server found | not found | Evidence for every cell is on the profiles: [Smithery](https://agentmcpdirectory.com/hosts/smithery/) and [Glama](https://agentmcpdirectory.com/hosts/glama/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/smithery-vs-glama/index.md) ## Sources - [smithery.ai home page](https://smithery.ai/), read 5 November 2026 - [Arcade: Smithery is now part of Arcade.dev (5 Aug 2026)](https://www.arcade.dev/blog/smithery-joins-arcade), read 5 November 2026 - [Glama MCP servers directory](https://glama.ai/mcp/servers), read 4 November 2026 (Figure read on the glama.ai page on 4 November 2026.) - [Glama MCP connectors (remote servers)](https://glama.ai/mcp/connectors), read 4 November 2026 (Figure read on the glama.ai page on 4 November 2026.) - [Smithery: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=ai.smithery), read 4 November 2026 - [Smithery: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Glama: glama.ai/pricing](https://glama.ai/pricing), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Smithery vs Official MCP Registry | Agent MCP Directory" description: "Smithery vs Official MCP Registry: one sourced difference and a verdict for product engineers, platform leads and agent builders." canonical: https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Smithery vs Official MCP Registry | Agent MCP Directory > Smithery vs Official MCP Registry: one sourced difference and a verdict for product engineers, platform leads and agent builders. Source: https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry Site: Agent MCP Directory Last reviewed: 2026-11-05 # Smithery vs Official MCP Registry Product engineer: Check whether a registry entry points at a host that still serves it. Developer-platform lead: Hosted-by-third-party entries can break when the host changes, as the 31 Oct 2026 proxy shutdown shows. Agent builder: Prefer entries whose remote is on the vendor's own domain. ## The sourced difference Smithery published 213 hosted servers into the official registry under ai.smithery, all pointing at server.smithery.ai; the registry itself does not host or proxy anything. (Smithery: [registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=ai.smithery), observed on 4 November 2026 and [Arcade: Smithery is now part of Arcade.dev (5 Aug 2026)](https://www.arcade.dev/blog/smithery-joins-arcade), read 5 November 2026; Official MCP Registry: [MCP Registry: about](https://modelcontextprotocol.io/registry/about), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Check whether a registry entry points at a host that still serves it. | | Developer-platform lead | Hosted-by-third-party entries can break when the host changes, as the 31 Oct 2026 proxy shutdown shows. | | Agent builder | Prefer entries whose remote is on the vendor's own domain. | ## Side by side on the rubric | Dimension | Smithery | Official MCP Registry | | --- | --- | --- | | Remote transport | Streamable HTTP (registry entries) | records both | | OAuth with client registration | managed identity retired | not applicable | | Per-tool auth scoping | not documented | not applicable | | Hosting and scale limits | proxy retired | not a host | | Observability | not documented | not applicable | | Pricing | not published | free | | Registry submission | unclear after acquisition | CLI with namespace verification | | Discoverability by agents | catalog browse only | open paginated API | | Own server in the registries | no own server found | not applicable | Evidence for every cell is on the profiles: [Smithery](https://agentmcpdirectory.com/hosts/smithery/) and [Official MCP Registry](https://agentmcpdirectory.com/hosts/official-mcp-registry/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry/index.md) ## Sources - [registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=ai.smithery), read 4 November 2026 (Fact noted from the registry API at registry.modelcontextprotocol.io on 4 November 2026.) - [Arcade: Smithery is now part of Arcade.dev (5 Aug 2026)](https://www.arcade.dev/blog/smithery-joins-arcade), read 5 November 2026 - [MCP Registry: about](https://modelcontextprotocol.io/registry/about), read 5 November 2026 - [Smithery: smithery.ai](https://smithery.ai/), read 4 November 2026 - [Smithery: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Official MCP Registry: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vercel vs Mintlify MCP | Agent MCP Directory" description: "Vercel vs Mintlify MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Vercel vs Mintlify MCP | Agent MCP Directory > Vercel vs Mintlify MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vercel vs Mintlify MCP Product engineer: If the job is answering questions about your docs, Mintlify gives it to you without code. Developer-platform lead: Mintlify publishes .well-known discovery files; Vercel leaves discovery to you. Agent builder: Mintlify's rate limits (5,000 per hour per IP) bound heavy agent use. ## The sourced difference Vercel runs whatever MCP server you write; Mintlify generates a docs search server automatically at /mcp with fixed tools and published rate limits. (Vercel: [Vercel: deploy MCP servers to Vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 5 November 2026; Mintlify MCP: [Mintlify: Model Context Protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | If the job is answering questions about your docs, Mintlify gives it to you without code. | | Developer-platform lead | Mintlify publishes .well-known discovery files; Vercel leaves discovery to you. | | Agent builder | Mintlify's rate limits (5,000 per hour per IP) bound heavy agent use. | ## Side by side on the rubric | Dimension | Vercel | Mintlify MCP | | --- | --- | --- | | Remote transport | Streamable HTTP only | Streamable HTTP | | OAuth with client registration | bring your own AS; CIMD on Vercel MCP | client credentials at /authed/mcp/oauth/token | | Per-tool auth scoping | scopes per handler | public versus authed endpoints | | Hosting and scale limits | Vercel Functions limits | published rate limits | | Observability | platform logs, rollbacks, rolling releases | not detailed | | Pricing | Functions pricing | MCP included; WebMCP Pro or Enterprise | | Registry submission | not a registry | not a registry | | Discoverability by agents | none built in | four .well-known discovery files | | Own server in the registries | yes | yes | Evidence for every cell is on the profiles: [Vercel](https://agentmcpdirectory.com/hosts/vercel/) and [Mintlify MCP](https://agentmcpdirectory.com/hosts/mintlify-mcp/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp/index.md) ## Sources - [Vercel: deploy MCP servers to Vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 5 November 2026 - [Mintlify: Model Context Protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 5 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Vercel: vercel.com/docs/agent-resources/vercel-mcp](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 - [Vercel: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.vercel%2Fvercel-mcp), read 4 November 2026 - [Mintlify MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.mintlify), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WebMCP vs agents.json | Agent MCP Directory" description: "WebMCP vs agents.json: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/webmcp-vs-agents-json site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # WebMCP vs agents.json | Agent MCP Directory > WebMCP vs agents.json: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/webmcp-vs-agents-json Site: Agent MCP Directory Last reviewed: 2026-11-05 # WebMCP vs agents.json Product engineer: agents.json documents an API; WebMCP wraps page actions. Developer-platform lead: agents.json is at 0.1.0; WebMCP has browser vendors behind it. Agent builder: Neither is required by MCP clients today. WebMCP exposes JavaScript tools in the page at run time; agents.json is a static OpenAPI-based file at /.well-known/agents.json describing API flows. ## The sourced difference WebMCP exposes JavaScript tools in the page at run time; agents.json is a static OpenAPI-based file at /.well-known/agents.json describing API flows. (WebMCP: [webmachinelearning/webmcp](https://github.com/webmachinelearning/webmcp), read 5 November 2026; agents.json: [wild-card-ai/agents-json](https://github.com/wild-card-ai/agents-json), observed on 4 November 2026 and [wild-card-ai/agents-json](https://github.com/wild-card-ai/agents-json), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | agents.json documents an API; WebMCP wraps page actions. | | Developer-platform lead | agents.json is at 0.1.0; WebMCP has browser vendors behind it. | | Agent builder | Neither is required by MCP clients today. | ## Side by side | Aspect | WebMCP | agents.json | | --- | --- | --- | | Maintainer | W3C Web Machine Learning Community Group (editors from Microsoft and Google) | Wildcard AI (started the project); maintainers listed in MAINTAINERS.md | | What it is | A browser API that lets a page register JavaScript functions as tools, with descriptions and schemas, that an in-browser agent can call. | An OpenAPI-based contract that describes flows (sequences of API calls) and links between actions so agents can call an API correctly. | | Status and version | Draft specification; Chrome and Edge test it in an origin trial, Brave behind a flag, no Firefox or Safari implementation (nekuda FAQ, October 2026). | Version 0.1.0, MIT licence; proposed location /.well-known/agents.json. | | What it does not do | Does not work without a browser agent that reads the page; does not replace a server-side MCP endpoint; the declarative form-based API is only being explored. | Does not define transport or auth beyond OpenAPI; not referenced by the MCP spec. | Read the full entries: [WebMCP](https://agentmcpdirectory.com/standards/webmcp/) and [agents.json](https://agentmcpdirectory.com/standards/agents-json/). ## Seen in the shared crawl The shared crawl looks for WebMCP in the initial HTML of each home page. It found a WebMCP hint on 25 of 7,545 home pages in the Tranco top 10,000 and on 59 of 3,393 on Ora's leaderboard. | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /agents.json | 0 of 7,485 (0%) | 0 of 3,366 (0%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/webmcp-vs-agents-json/index.md) ## Sources - [webmachinelearning/webmcp](https://github.com/webmachinelearning/webmcp), read 5 November 2026 - [wild-card-ai/agents-json](https://github.com/wild-card-ai/agents-json), read 4 November 2026 (Fact noted from the github.com page on 4 November 2026.) Last reviewed 5 November 2026 --- --- title: "Zapier MCP vs Apify MCP | Agent MCP Directory" description: "Zapier MCP vs Apify MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026." canonical: https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Head-to-heads" --- # Zapier MCP vs Apify MCP | Agent MCP Directory > Zapier MCP vs Apify MCP: one sourced difference and a verdict for product engineers, platform leads and agent builders. Read 4 November 2026. Source: https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zapier MCP vs Apify MCP Product engineer: Use Zapier for writing into business apps; Apify for reading the web. Developer-platform lead: Zapier bills tasks; Apify bills Actor runs. Agent builder: Apify allows a keyless mode for search and docs tools. Zapier covers SaaS actions across 9,000+ apps with Zapier holding credentials. ## The sourced difference Zapier covers SaaS actions across 9,000+ apps with Zapier holding credentials; Apify covers web data through Actors and can take per-request payments via Skyfire on pay-per-event Actors. (Zapier MCP: [Zapier MCP docs](https://docs.zapier.com/mcp/home), read 5 November 2026; Apify MCP: [Apify MCP server docs](https://docs.apify.com/platform/integrations/mcp), read 5 November 2026) ## Verdicts by reader | Reader | Verdict | | --- | --- | | Product engineer | Use Zapier for writing into business apps; Apify for reading the web. | | Developer-platform lead | Zapier bills tasks; Apify bills Actor runs. | | Agent builder | Apify allows a keyless mode for search and docs tools. | ## Side by side on the rubric | Dimension | Zapier MCP | Apify MCP | | --- | --- | --- | | Remote transport | Streamable HTTP only | Streamable HTTP and stdio | | OAuth with client registration | OAuth for clients | OAuth | | Per-tool auth scoping | yes, app and action level | tools parameter selects Actors | | Hosting and scale limits | task quota | Actor run limits | | Observability | History log of every MCP action | run status and storage IDs | | Pricing | included, tasks per call | per Actor run | | Registry submission | not a registry | Apify Store for Actors | | Discoverability by agents | agentic mode | search-actors tool | | Own server in the registries | yes | yes | Evidence for every cell is on the profiles: [Zapier MCP](https://agentmcpdirectory.com/hosts/zapier-mcp/) and [Apify MCP](https://agentmcpdirectory.com/hosts/apify-mcp/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp/index.md) ## Sources - [Zapier MCP docs](https://docs.zapier.com/mcp/home), read 5 November 2026 - [Apify MCP server docs](https://docs.apify.com/platform/integrations/mcp), read 5 November 2026 - [Zapier MCP: zapier.com/mcp](https://zapier.com/mcp), read 4 November 2026 - [Zapier MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.zapier%2Fmcp), read 4 November 2026 - [Apify MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.apify%2Fapify-mcp-server), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Contact | Agent MCP Directory" description: "Contact Agent MCP Directory about a row, an endpoint, a correction or the data. The form is not connected to a backend yet." canonical: https://agentmcpdirectory.com/contact site: "Agent MCP Directory" last_updated: 2026-11-04 section: "About" --- # Contact | Agent MCP Directory > Contact Agent MCP Directory about a row, an endpoint, a correction or the data. The form is not connected to a backend yet. Source: https://agentmcpdirectory.com/contact Site: Agent MCP Directory Last reviewed: 2026-11-04 # Contact ## Write to the editor Use this for a row, an endpoint to add, a correction or a question about the data. ## What to include - The page address, so the row or figure can be found. - What is wrong or missing, and a public source that shows it: a registry entry, a changelog or a documentation page. - For a missing company, the domain and the public MCP endpoint, if there is one. - A reply address, if you want an answer. ## What happens next Reports about a fact are checked against the source you give and against a fresh connector run where the row concerns an endpoint. A confirmed error is fixed in place and written to the corrections log with its date. Reports with no source are read but cannot change a row. To add an endpoint, use [the submit page](https://agentmcpdirectory.com/directory/submit/). To report an error, use [corrections](https://agentmcpdirectory.com/corrections/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/contact/index.md) Last reviewed 4 November 2026 --- --- title: "Corrections | Agent MCP Directory" description: "How to report an error in the directory, what happens next, and the log of corrections published since the first edition on 4 November 2026." canonical: https://agentmcpdirectory.com/corrections site: "Agent MCP Directory" last_updated: 2026-11-04 section: "About" --- # Corrections | Agent MCP Directory > How to report an error in the directory, what happens next, and the log of corrections published since the first edition on 4 November 2026. Source: https://agentmcpdirectory.com/corrections Site: Agent MCP Directory Last reviewed: 2026-11-04 # Corrections ## Report an error Send the page, what is wrong and a source that shows it. A company can ask for a row to be re-checked after it fixes an endpoint; the connector runs again in the next edition and sooner on request. ## What is corrected - A status, auth type, tool count or endpoint that no longer matches what the endpoint answers: the row is re-checked and the new result replaces the old one with its date. - A fact on a host, standard or guide that disagrees with its cited source: the text is fixed in place and the source stays linked. - A company name, category or domain that is wrong: fixed from the company's own site or registry entry. - A claim that a company has no MCP server when it has one: send the public endpoint and the next connector run will try it. ## Corrections log No corrections have been published since the first edition on 4 November 2026. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/corrections/index.md) Last reviewed 4 November 2026 --- --- title: "Download the MCP and CLI Directory (CSV, JSON) | Agent MCP Directory" description: "Download the MCP and CLI Directory as CSV or JSON: 1,336 companies with endpoint, auth type, tools and CLI, checked 4 November 2026." canonical: https://agentmcpdirectory.com/data site: "Agent MCP Directory" last_updated: 2026-11-05 date: 2026-11-04 section: "Data" --- # Download the MCP and CLI Directory (CSV, JSON) | Agent MCP Directory > Download the MCP and CLI Directory as CSV or JSON: 1,336 companies with endpoint, auth type, tools and CLI, checked 4 November 2026. Source: https://agentmcpdirectory.com/data Site: Agent MCP Directory Last reviewed: 2026-11-05 # The directory as data The whole directory as CSV and JSON: 1,336 companies, each with its MCP endpoint, auth type, tool names, CLI package and the date a connector last reached it. The first edition is dated 4 November 2026. A citation line and the column list follow. ## Downloads - [mcp-directory-2026-11-04.csv](https://agentmcpdirectory.com/data/mcp-directory-2026-11-04.csv) 1,336 rows, one per company - [mcp-directory-2026-11-04.json](https://agentmcpdirectory.com/data/mcp-directory-2026-11-04.json) the same rows with tool names as arrays - [act-layer-census-2026-11-04.csv](https://agentmcpdirectory.com/data/act-layer-census-2026-11-04.csv) the census, one row per cohort and file - [act-layer-census-2026-11-04.json](https://agentmcpdirectory.com/data/act-layer-census-2026-11-04.json) the census with categories ## Cite this Agent MCP Directory, "MCP and CLI Directory", 4 November 2026 edition, https://agentmcpdirectory.com/data ## Columns | company, descriptor, domain, category | Display name, any registry description, the domain and the category. | | --- | --- | | mcp_status, has_mcp | verified, sign-in, credential-wall, no-answer, no-tools or none-found; true only when the connector listed tools; sign-in challenges are not counted. | | endpoint, endpoint_source | The endpoint tried, and whether it was listed or found by a subdomain guess. | | transport, protocol_version, auth_type | Observed by connecting: transport, protocol revision and auth type. | | tool_count, tool_names, resources_count, prompts_count | From tools/list, resources/list and prompts/list; names are capped at 40. | | connected_at | UTC time of the handshake. | | cli_package, cli_registry, cli_latest_version, cli_last_publish | Where a CLI package is on record. | | openapi_url, webmcp, a2a_agent_card, agents_json, mcp_json | From the shared crawl: yes, no or not checked. | | official_registry, github_registry | Whether the company is listed in each registry. | | ora_score, ora_grade, ora_scanned, ora_read, ora_via, ora_source, tranco_rank | Ora's cached score and grade for the domain (a vendor-published figure), the day Ora scanned it, the day it was read on 5 November 2026, which read it came from in ora_via (score-api for GET /api/score/{domain}, leaderboard for the same day's GET /api/leaderboard) and Ora's score page for the domain in ora_source; empty where Ora has no cached score. The Tranco rank. | | verified_at, entry_url | Verification date and the page for the row. | ## Edition log | Edition | Rows | Tools listed | Sign-in required | Note | | --- | --- | --- | --- | --- | | 2026-11-04 | 1,336 | 263 | 533 | First edition. The next re-run is due in December 2026. | Rows for platform domains and one registry entry without a valid hostname were left out of this edition. See [the method](https://agentmcpdirectory.com/method/) for what the status words mean. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/data/index.md) ## Sources - [Official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [GitHub MCP Registry](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "API and MCP server | Agent MCP Directory" description: "How to query the directory as data: the MCP server at /mcp, the REST API described by openapi.json and the NLWeb ask endpoint, all read-only and open." canonical: https://agentmcpdirectory.com/developers site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Developers" --- # API and MCP server | Agent MCP Directory > How to query the directory as data: the MCP server at /mcp, the REST API described by openapi.json and the NLWeb ask endpoint, all read-only and open. Source: https://agentmcpdirectory.com/developers Site: Agent MCP Directory Last reviewed: 2026-11-05 # API and MCP server Agents can query every directory row through an MCP server at /mcp with five read-only tools, a REST API under /api/v1 described by openapi.json, and an NLWeb /ask endpoint over the rows and pages. No credential is needed, the limit is 120 requests a minute, and each answer names the page to cite. ## Connect the MCP server The server speaks the Streamable HTTP transport at `https://agentmcpdirectory.com/mcp`: send JSON-RPC 2.0 messages with POST and read the JSON answer. There is no session, no credential and no server-initiated stream, so one request is one answer. Any MCP client that takes a URL connects with the address alone. The card at [/mcp/server-card](https://agentmcpdirectory.com/mcp/server-card) and the manifest at [/.well-known/mcp.json](https://agentmcpdirectory.com/.well-known/mcp.json) say the same thing in the forms clients read. ```bash curl -s https://agentmcpdirectory.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}' ``` ```bash curl -s https://agentmcpdirectory.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_company","arguments":{"domain":"stripe.com"}}}' ``` A tool answers with the result as `structuredContent` and the same JSON as text. A wrong argument answers `isError: true` with the parameter list; an unknown tool answers JSON-RPC error -32602. The server also lists resources with `resources/list`: the page index, the method page, this page and the two dataset files, readable with `resources/read`. ## The five tools | Tool | What it returns | Parameters | | --- | --- | --- | | search_directory | Lists directory companies (name, domain, category, MCP status, auth type, transport, tool count, whether a CLI is on record, entry page URL). Filter by words in the company name, registry title or domain, by category, status, auth type, transport or CLI. Call it to find a domain before get_company. | q?: Words to look for in the company name, registry title or domain, for example "stripe" or "pay"; category?: A category name or its slug, for example "Payments & Fintech" or "developer-tools". list_categories gives them all; mcp_status?: verified is the only counted state (tools listed); sign-in is a sign-in challenge, tools not seen, not counted; none-found means no endpoint is on record; auth_type?: none, api-key, oauth-dcr (OAuth with client registration), oauth (OAuth without) or unknown. Rows with no endpoint, and rows whose endpoint did not answer, have no auth type, as on the directory page; transport?: The transport the connector observed; has_cli?: true for companies with a CLI package on record, false for those without. The CLI column is a floor: a package is checked only where a source names one | | get_company | Returns the full directory row for one domain (for example stripe.com): status, endpoint and where it was found, transport, protocol revision, auth type, tool count and the recorded tool names, CLI package, OpenAPI, registries, plus how and when the row was observed and the entry page URL to cite. | domain: The company domain as listed in the directory, for example stripe.com. A leading https:// or www. is ignored | | list_categories | Lists the directory categories with how many companies each holds and how many fall in each status: verified (open, tools listed), sign_in (challenge, tools not seen, not counted), credential_wall, no_answer, no_tools and none_found (no endpoint on record). Call it to see where open servers sit before search_directory. | none | | get_directory_stats | Returns the directory totals: companies, how many count as having an MCP server (tools listed), the split by status, auth type (endpoints that answered, as on the directory page) and transport, the distribution of tool counts across the open servers, and how many have a CLI or an OpenAPI file. No parameters. | none | | get_census | Returns the Act Layer Census: for the Tranco top 10,000 and for the domains on the Ora leaderboard, how many probed domains publish each discovery file (MCP, A2A agent card, agents.json, OpenAPI, OAuth metadata, AI catalog, agent skills), and the same counts per leaderboard category. Filter by cohort, category or file path. | cohort?: top10k is the Tranco top 10,000; ora-leaderboard is the domains scored on Ora's public leaderboard. Omit for both; category?: An Ora leaderboard category, for example "Developer Tools". Only the leaderboard cohort has categories; file?: Words from a file path or label to keep one file, for example "openapi" or ".well-known/mcp.json" | ## The REST API Each tool is also one GET endpoint under `/api/v1/`, with the parameters in the query string and the same JSON in the answer. [/api](https://agentmcpdirectory.com/api) is the index; [/openapi.json](https://agentmcpdirectory.com/openapi.json) describes every operation with its parameters, its response schema and the Error schema; [/.well-known/api-catalog](https://agentmcpdirectory.com/.well-known/api-catalog) links that description the way RFC 9727 says. Paginated endpoints take `limit` and the `next_cursor` of the previous page as `cursor`. - [/api/v1/search\_directory?category=Payments+%26+Fintech&mcp\_status=verified](https://agentmcpdirectory.com/api/v1/search_directory?category=Payments+%26+Fintech&mcp_status=verified): Search the directory. Paginated. - [/api/v1/get\_company?domain=stripe.com](https://agentmcpdirectory.com/api/v1/get_company?domain=stripe.com): One company in full. - [/api/v1/list\_categories](https://agentmcpdirectory.com/api/v1/list_categories): List categories with counts. - [/api/v1/get\_directory\_stats](https://agentmcpdirectory.com/api/v1/get_directory_stats): Directory totals. - [/api/v1/get\_census?cohort=top10k](https://agentmcpdirectory.com/api/v1/get_census?cohort=top10k): Act Layer Census. - [/api](https://agentmcpdirectory.com/api): the index with the endpoints, the dataset downloads, the limits and the versioning policy. ```bash curl -s 'https://agentmcpdirectory.com/api/v1/get_company?domain=stripe.com' | jq .observation ``` ## Ask in plain words The `/ask` endpoint follows NLWeb 0.55. It searches the directory rows, the census files and every page, and returns schema.org objects, each with a `grounding.source` URL to cite. GET takes `query`; POST takes the NLWeb request object. Add `streaming=true`, or `prefer.streaming`, for server-sent events named start, result and complete. With `mode=summarize` the answer gains a one-sentence summary assembled from the results, never from a model. ```bash curl -s 'https://agentmcpdirectory.com/ask?query=stripe' ``` ```bash curl -s https://agentmcpdirectory.com/ask -H 'Content-Type: application/json' -d '{"query":{"text":"payments companies with an open MCP server"},"prefer":{"mode":"list"},"meta":{"version":"0.55"}}' ``` No match answers `_meta.response_type: failure` with code NO\_RESULTS; a missing query answers 400 with INVALID\_QUERY. Context objects are accepted and ignored, because the answers come from the data and not from a conversation. ## Discovery files | File | What it holds | | --- | --- | | /openapi.json | OpenAPI 3.1 for the REST API and /ask; linked from every page as rel=service-desc and from the Link header of the home page. | | /.well-known/api-catalog | The RFC 9727 linkset: the API, the MCP server and the ask endpoint with their descriptions. | | /.well-known/mcp/server-card.json | The MCP server card: name, version, remote URL and protocol versions. The same card is served at /mcp/server-card. | | /.well-known/mcp.json | The manifest: endpoint, transport and the tools with their input schemas. | | /.well-known/ai-catalog.json | AI Catalog 1.0 with entries for the MCP card, the OpenAPI document, the ask endpoint and every document; the same file is at /.well-known/ard.json. | | /schemamap.xml | Schema feeds: the directory rows and the census files as JSON-LD lines under /feeds/, named in robots.txt. | | /.well-known/agent-skills/index.json | One agent skill that says how to answer a question about a company's MCP server with these tools. | ## What a count means A company has an MCP server in these answers only when the connector listed its tools: `has_mcp` is true for `mcp_status` verified and for no other status. A sign-in challenge is its own status, listed apart and never counted. A none-found row says that no source read for this edition names an endpoint, which is not proof that no server exists. Auth types are counted for endpoints that answered, as on the directory page, so a row whose endpoint did not answer has none. Every company answer carries `observed_at` and the method, so a reader can see when and how the row was observed. [The method page](https://agentmcpdirectory.com/method/) holds the full rules. ## Access, limits and errors | Credential | None. The OpenAPI document declares security: [] with no security schemes, and auth.md says the same. The site publishes no OAuth metadata because no endpoint takes a token; metadata for an authorization server that does not exist would send agents to a door that is not there. | | --- | --- | | Rate limit | 120 requests a minute per client address, counted per running instance and announced in RateLimit and RateLimit-Policy headers; a 429 carries Retry-After. The host adds its own limits above that. The whole directory is one download from the data page, so bulk readers never need the API. | | Errors | JSON, never HTML: {"error":{"code","message","hint","status","docs"}} with the codes invalid_params, not_found, method_not_allowed, rate_limited and internal. A missing endpoint under /api answers 404 with the list of endpoints in the hint. | | Writes | There are none, so every call is safe to retry and no idempotency key exists. Every call answers in one response; nothing runs long enough to need a job pattern. | | CORS | Every answer carries Access-Control-Allow-Origin: *, so a browser-resident agent can call the API and the MCP server. The home page also registers two of the tools through WebMCP in browsers that offer it. | ## Versioning The path prefix `/api/v1` is the contract. A breaking change, such as a field removed or renamed or a tool removed, ships under `/api/v2` while `/api/v1` keeps answering for at least 180 days, announced on this page and in the `info.version` of openapi.json. Additive changes, such as a new field or a new tool, do not change the prefix. The MCP server follows the same rule: its card and its `serverInfo.version` carry the same version number as the OpenAPI document. The data behind every answer is edition 2026-11-04; the edition is in the `X-Dataset-Edition` header and in every tool result. Each running instance keeps a data file for ten minutes after it reads it. ## Cite the data Every result names the page it comes from; cite that URL. The data files are published under CC BY 4.0 (see [pricing.md](https://agentmcpdirectory.com/pricing.md)). The citation line for the directory is on [the data page](https://agentmcpdirectory.com/data/), where the rows are also published as CSV and JSON. Agent MCP Directory, "MCP and CLI Directory", 4 November 2026 edition, https://agentmcpdirectory.com/data ## What the surface does not do It does not write, hold accounts, generate text with a model or call any company's MCP server. It does not search beyond this site's own rows and pages, and it does not refresh the data: the connector run behind the rows is the one of 4 November 2026. The directory pages remain the record, and [the method](https://agentmcpdirectory.com/method/) explains how each row is made. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/developers/index.md) ## Sources - [MCP transports, Streamable HTTP](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026 - [NLWeb repository and specification](https://github.com/nlweb-ai/NLWeb), read 4 November 2026 - [OpenAPI Specification](https://spec.openapis.org/oas/latest.html), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Directory by status, auth and category | Agent MCP Directory" description: "The directory by status, auth type, category and letter: 1,336 companies, 263 with tools listed, 36 with a CLI on record." canonical: https://agentmcpdirectory.com/directory site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Directory" --- # Directory by status, auth and category | Agent MCP Directory > The directory by status, auth type, category and letter: 1,336 companies, 263 with tools listed, 36 with a CLI on record. Source: https://agentmcpdirectory.com/directory Site: Agent MCP Directory Last reviewed: 2026-11-04 # The directory 1,336 companies, each checked for an MCP server, a CLI and an OpenAPI file. Browse by MCP status, by auth type, by category or by letter. 263 listed tools to a client with no credentials; 533 more answered with a sign-in challenge and are not counted. ## By MCP status | Status | Companies | What it means | | --- | --- | --- | | Verified | 263 | The endpoint answered a handshake with no credentials and listed its tools. | | Sign-in required | 533 | Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. | | Credential wall | 19 | The endpoint asked for credentials and published no OAuth metadata, so it cannot be told apart from any other protected API. Not counted as an MCP server. | | No answer | 47 | A source lists an endpoint, but it did not answer an MCP handshake on the day. Not counted. | | No tools listed | 2 | The endpoint completed the handshake and listed no tools. Not counted. | | None found | 472 | No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to. | ## By auth type | Auth type | Endpoints | What it means | | --- | --- | --- | | No authentication | 263 | The server listed its tools to a client that sent no credentials. | | API key | 19 | The server answered 401 or 403 and asks for a key or bearer token with no OAuth metadata for an agent to follow. | | OAuth with client registration | 517 | The server publishes OAuth metadata and a registration endpoint, so a client can register itself without a human filling in a form first. | | OAuth without client registration | 16 | The server publishes OAuth metadata but no registration endpoint, so a client must be registered by hand or identified by a client ID metadata document. | | Auth not determined | 2 | The connector could not tell what the endpoint wants, usually because it did not answer. | ## By category | Category | Companies | Tools listed | Sign-in required | CLI on record | | --- | --- | --- | --- | --- | | Developer Tools | 450 | 41 | 96 | 8 | | Infrastructure | 303 | 26 | 92 | 12 | | Uncategorised | 201 | 91 | 97 | 0 | | Agent Tools | 74 | 27 | 38 | 2 | | Productivity | 49 | 3 | 45 | 2 | | Data & Analytics | 39 | 8 | 28 | 1 | | AI & ML | 36 | 9 | 22 | 5 | | Communication & Support | 35 | 14 | 19 | 1 | | Marketing | 31 | 7 | 24 | 0 | | Payments & Fintech | 29 | 5 | 23 | 0 | | CRM | 19 | 5 | 12 | 2 | | E-commerce | 14 | 7 | 7 | 0 | | Gaming & Media | 12 | 4 | 6 | 0 | | Security | 10 | 4 | 5 | 0 | | Commerce Tools | 6 | 0 | 4 | 3 | | Identity & Auth | 6 | 3 | 2 | 0 | | Travel & Hospitality | 5 | 2 | 3 | 0 | | Legal & Compliance | 4 | 1 | 3 | 0 | | Education | 2 | 1 | 1 | 0 | | Hardware & Robotics | 2 | 1 | 1 | 0 | | Healthcare | 2 | 1 | 1 | 0 | | Logistics & Supply Chain | 2 | 0 | 2 | 0 | | Climate & Energy | 1 | 0 | 1 | 0 | | Consumer | 1 | 1 | 0 | 0 | | HR & Recruiting | 1 | 1 | 0 | 0 | | News & Intelligence | 1 | 0 | 1 | 0 | | Real Estate & Construction | 1 | 1 | 0 | 0 | ## A to Z Starts with - [A](https://agentmcpdirectory.com/directory/letter/a/) 109 - [B](https://agentmcpdirectory.com/directory/letter/b/) 62 - [C](https://agentmcpdirectory.com/directory/letter/c/) 119 - [D](https://agentmcpdirectory.com/directory/letter/d/) 55 - [E](https://agentmcpdirectory.com/directory/letter/e/) 35 - [F](https://agentmcpdirectory.com/directory/letter/f/) 48 - [G](https://agentmcpdirectory.com/directory/letter/g/) 48 - [H](https://agentmcpdirectory.com/directory/letter/h/) 46 - [I](https://agentmcpdirectory.com/directory/letter/i/) 34 - [J](https://agentmcpdirectory.com/directory/letter/j/) 12 - [K](https://agentmcpdirectory.com/directory/letter/k/) 30 - [L](https://agentmcpdirectory.com/directory/letter/l/) 52 - [M](https://agentmcpdirectory.com/directory/letter/m/) 78 - [N](https://agentmcpdirectory.com/directory/letter/n/) 36 - [O](https://agentmcpdirectory.com/directory/letter/o/) 48 - [P](https://agentmcpdirectory.com/directory/letter/p/) 87 - [Q](https://agentmcpdirectory.com/directory/letter/q/) 8 - [R](https://agentmcpdirectory.com/directory/letter/r/) 67 - [S](https://agentmcpdirectory.com/directory/letter/s/) 170 - [T](https://agentmcpdirectory.com/directory/letter/t/) 79 - [U](https://agentmcpdirectory.com/directory/letter/u/) 23 - [V](https://agentmcpdirectory.com/directory/letter/v/) 28 - [W](https://agentmcpdirectory.com/directory/letter/w/) 39 - [X](https://agentmcpdirectory.com/directory/letter/x/) 3 - [Y](https://agentmcpdirectory.com/directory/letter/y/) 1 - [Z](https://agentmcpdirectory.com/directory/letter/z/) 15 - [0-9](https://agentmcpdirectory.com/directory/letter/0/) 4 [106 endpoints found by subdomain guess](https://agentmcpdirectory.com/directory/guessed/), [search](https://agentmcpdirectory.com/directory/search/) and [submit a company](https://agentmcpdirectory.com/directory/submit/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "0xArchive MCP server | Agent MCP Directory" description: "0xArchive: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/0xarchive-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # 0xArchive MCP server | Agent MCP Directory > 0xArchive: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/0xarchive-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # 0xArchive: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for 0xArchive at mcp.0xarchive.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | 0xArchive (registry title: 0xArchive Market Data) | | --- | --- | | Domain | 0xarchive.io | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 94, grade A; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for 0xarchive.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.0xarchive.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,482 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:16Z https://mcp.0xarchive.io/mcp sent initialize result auth-required (HTTP 401) 1500 ms - 20:01:55Z https://mcp.0xarchive.io/mcp sent initialize result auth-required (HTTP 401) 1482 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="0xArchive", resource_metadata="https://mcp.0xarchive.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.0xarchive.io | | Authorization server metadata | auth.0xarchive.io | | Registration endpoint | https://auth.0xarchive.io/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.0xarchive.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.0xarchive.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.0xarchive.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for 0xArchive. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: 0xarchive.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.0xarchive/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/0xarchive-io/index.md) ## Sources - [Ora score page for 0xarchive.io](https://ora.ai/score/0xarchive.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=0xarchive), read 4 November 2026 - [0xArchive website](https://0xarchive.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "1102tools MCP server | Agent MCP Directory" description: "1102tools has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/1102tools-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # 1102tools MCP server | Agent MCP Directory > 1102tools has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/1102tools-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # 1102tools: MCP server, CLI and agent surfaces Yes: 1102tools runs a public MCP server at sam.1102tools.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: search\_opportunities, get\_opportunity, summarize\_opportunities. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | 1102tools (registry title: Acquisition.gov) | | --- | --- | | Domain | 1102tools.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for 1102tools.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://sam.1102tools.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | sam-gov 1.1.19 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 149 ms over 1 attempt | ### Tools listed 6 tools - search\_opportunities - get\_opportunity - summarize\_opportunities - get\_data\_status - search\_entities - search\_exclusions ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:16Z https://sam.1102tools.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1202 ms - 20:01:53Z https://sam.1102tools.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 149 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://sam.1102tools.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for 1102tools. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.1102tools/acquisition-gov-mcp, com.1102tools/bls-oews-mcp, com.1102tools/ecfr-mcp and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/1102tools-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=1102tools), read 4 November 2026 - [1102tools website](https://1102tools.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "2extract MCP server | Agent MCP Directory" description: "2extract has an open MCP server with 20 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/2extract-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # 2extract MCP server | Agent MCP Directory > 2extract has an open MCP server with 20 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/2extract-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # 2extract: MCP server, CLI and agent surfaces Yes: 2extract runs a public MCP server at mcp.2extract.com that listed 20 tools to a client with no credentials on 4 November 2026. Examples: buildConnectionString, createProxyResource, deactivateProxyResource. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | 2extract | | --- | --- | | Domain | 2extract.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for 2extract.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.2extract.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | 2extract-mcp-public | | Capabilities | logging, prompts, resources, tools | | Tools | 20 | | Resources | 20 | | Prompts | 4 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 961 ms over 1 attempt | ### Tools listed 20 tools - buildConnectionString - createProxyResource - deactivateProxyResource - deleteProxyResource - getAccountBalance - getAccountTrafficUsage - getProxyResource - listAccountBalanceHistory - listGeoCountries - listProxyPlans - listProxyResources - regenerateProxyPassword - searchGeoCities - searchGeoISP - searchGeoRegions - searchGeoZips - setProxyIpWhitelist - setProxyLimits - setProxyTargetHosts - updateProxyResource ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:17Z https://mcp.2extract.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1378 ms - 20:01:55Z https://mcp.2extract.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 961 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.2extract.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for 2extract. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.2extract/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/2extract-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=2extract), read 4 November 2026 - [2extract website](https://2extract.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "3Dsellers MCP server | Agent MCP Directory" description: "3Dsellers: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/3dsellers-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # 3Dsellers MCP server | Agent MCP Directory > 3Dsellers: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/3dsellers-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # 3Dsellers: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for 3Dsellers at api.3dsellers.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | 3Dsellers | | --- | --- | | Domain | 3dsellers.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for 3dsellers.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.3dsellers.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 921 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:16Z https://api.3dsellers.com/mcp sent initialize result auth-required (HTTP 401) 957 ms - 20:01:55Z https://api.3dsellers.com/mcp sent initialize result auth-required (HTTP 401) 921 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://api.3dsellers.com", resource_metadata="https://api.3dsellers.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.3dsellers.com | | Authorization server metadata | api.3dsellers.com | | Registration endpoint | https://api.3dsellers.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.3dsellers.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.3dsellers.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.3dsellers.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for 3Dsellers. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.3dsellers/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/3dsellers-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=3dsellers), read 4 November 2026 - [3Dsellers website](https://3dsellers.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "a0.dev MCP server | Agent MCP Directory" description: "Does a0.dev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/a0-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # a0.dev MCP server | Agent MCP Directory > Does a0.dev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/a0-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # a0.dev: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for a0.dev, so the connector had nothing to connect to. Ora's cached score for a0.dev is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | a0.dev | | --- | --- | | Domain | a0.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for a0.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for a0.dev. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for a0.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for a0.dev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/a0-dev/index.md) ## Sources - [Ora score page for a0.dev](https://ora.ai/score/a0.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where a0.dev was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [a0.dev website](https://a0.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Aaly MCP server | Agent MCP Directory" description: "Aaly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aaly-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Aaly MCP server | Agent MCP Directory > Aaly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/aaly-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Aaly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Aaly at mcp.aaly.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Aaly | | --- | --- | | Domain | aaly.io | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for aaly.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.aaly.io | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,660 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:18Z https://mcp.aaly.io sent initialize result auth-required (HTTP 401) 1793 ms - 20:01:56Z https://mcp.aaly.io sent initialize result auth-required (HTTP 401) 1660 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.aaly.io | | Authorization server metadata | mcp.aaly.io | | Registration endpoint | https://mcp.aaly.io/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.aaly.io` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.aaly.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.aaly.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Aaly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.aaly/aaly | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aaly-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=aaly), read 4 November 2026 - [Aaly website](https://aaly.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Abstra MCP server | Agent MCP Directory" description: "Abstra has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/abstra-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Abstra MCP server | Agent MCP Directory > Abstra has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/abstra-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Abstra: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Abstra; the connector tried mcp.abstra.io as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/html). ## Fact sheet | Company | Abstra (registry title: abstra.io) | | --- | --- | | Domain | abstra.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 55, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for abstra.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.abstra.io/mcp | | --- | --- | | How it was found | mcp.abstra.io was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,190 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/html) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:17Z https://mcp.abstra.io/mcp sent initialize result no-answer (HTTP 404) 1052 ms - 20:01:56Z https://mcp.abstra.io/mcp sent initialize result no-answer (HTTP 404) 1190 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.abstra.io/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/html). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Abstra. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/abstra-io/index.md) ## Sources - [Ora score page for abstra.io](https://ora.ai/score/abstra.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Abstra was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Abstra website](https://abstra.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Account Executive Jobs MCP server | Agent MCP Directory" description: "Account Executive Jobs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/accountexecutivejobs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Account Executive Jobs MCP server | Agent MCP Directory > Account Executive Jobs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/accountexecutivejobs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Account Executive Jobs: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Account Executive Jobs at mcp.accountexecutivejobs.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Account Executive Jobs | | --- | --- | | Domain | accountexecutivejobs.com | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for accountexecutivejobs.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.accountexecutivejobs.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 235 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:18Z https://mcp.accountexecutivejobs.com/mcp sent initialize result auth-required (HTTP 401) 1822 ms - 20:01:56Z https://mcp.accountexecutivejobs.com/mcp sent initialize result auth-required (HTTP 401) 235 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.accountexecutivejobs.com/.well-known/oauth-protected-resource/mcp", scope="openid" | | Protected resource metadata | mcp.accountexecutivejobs.com | | Authorization server metadata | clerk.accountexecutivejobs.com | | Registration endpoint | https://clerk.accountexecutivejobs.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.accountexecutivejobs.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.accountexecutivejobs.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.accountexecutivejobs.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Account Executive Jobs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: accountexecutivejobs.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.accountexecutivejobs/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/accountexecutivejobs-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=accountexecutivejobs), read 4 November 2026 - [Account Executive Jobs website](https://accountexecutivejobs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Acquia MCP server | Agent MCP Directory" description: "Does Acquia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/acquia-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Acquia MCP server | Agent MCP Directory > Does Acquia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/acquia-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Acquia: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Acquia (acquia.com), so the connector had nothing to connect to. Ora's cached score for acquia.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Acquia (registry title: acquia.com) | | --- | --- | | Domain | acquia.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for acquia.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Acquia. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for acquia.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Acquia. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/acquia-com/index.md) ## Sources - [Ora score page for acquia.com](https://ora.ai/score/acquia.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Acquia was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Acquia website](https://acquia.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Activeloop MCP server | Agent MCP Directory" description: "Does Activeloop have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/activeloop-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Activeloop MCP server | Agent MCP Directory > Does Activeloop have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/activeloop-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Activeloop: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Activeloop (activeloop.ai), so the connector had nothing to connect to. Ora's cached score for activeloop.ai is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Activeloop (registry title: activeloop.ai) | | --- | --- | | Domain | activeloop.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for activeloop.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Activeloop. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for activeloop.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Activeloop. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/activeloop-ai/index.md) ## Sources - [Ora score page for activeloop.ai](https://ora.ai/score/activeloop.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/leaderboard) - [Where Activeloop was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Activeloop website](https://activeloop.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Actual AI MCP server | Agent MCP Directory" description: "Does Actual AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/actual-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Actual AI MCP server | Agent MCP Directory > Does Actual AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/actual-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Actual AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Actual AI (actual.ai), so the connector had nothing to connect to. Ora's cached score for actual.ai is 81, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Actual AI | | --- | --- | | Domain | actual.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 81, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for actual.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Actual AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for actual.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Actual AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: actual.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: actual.ai/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Found: actual.ai/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: actual.ai/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/actual-ai/index.md) ## Sources - [Ora score page for actual.ai](https://ora.ai/score/actual.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Actual AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Actual AI website](https://actual.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Adalo MCP server | Agent MCP Directory" description: "Does Adalo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/adalo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Adalo MCP server | Agent MCP Directory > Does Adalo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/adalo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Adalo: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Adalo (adalo.com), so the connector had nothing to connect to. Ora's cached score for adalo.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Adalo (registry title: adalo.com) | | --- | --- | | Domain | adalo.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for adalo.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Adalo. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for adalo.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Adalo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/adalo-com/index.md) ## Sources - [Ora score page for adalo.com](https://ora.ai/score/adalo.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Adalo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Adalo website](https://adalo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Aden MCP server | Agent MCP Directory" description: "Does Aden have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/adenhq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Aden MCP server | Agent MCP Directory > Does Aden have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/adenhq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Aden: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Aden (adenhq.com), so the connector had nothing to connect to. Ora's cached score for adenhq.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Aden (registry title: adenhq.com) | | --- | --- | | Domain | adenhq.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for adenhq.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Aden. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for adenhq.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Aden. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/adenhq-com/index.md) ## Sources - [Ora score page for adenhq.com](https://ora.ai/score/adenhq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Aden was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Aden website](https://adenhq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Adkit MCP server | Agent MCP Directory" description: "Adkit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/adkit-so site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Adkit MCP server | Agent MCP Directory > Adkit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/adkit-so Site: Agent MCP Directory Last reviewed: 2026-11-05 # Adkit: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Adkit at mcp.adkit.so answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Adkit (registry title: Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads) | | --- | --- | | Domain | adkit.so | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 59, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for adkit.so, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.adkit.so | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 453 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:19Z https://mcp.adkit.so sent initialize result auth-required (HTTP 401) 677 ms - 20:01:56Z https://mcp.adkit.so sent initialize result auth-required (HTTP 401) 453 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.adkit.so/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.adkit.so | | Authorization server metadata | mcp.adkit.so | | Registration endpoint | https://mcp.adkit.so/api/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.adkit.so` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.adkit.so/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.adkit.so/api/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Adkit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/adkit-so/index.md) ## Sources - [Ora score page for adkit.so](https://ora.ai/score/adkit.so?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/score) - [Adkit website](https://adkit.so), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ads Uploader MCP server | Agent MCP Directory" description: "Ads Uploader: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/adsuploader-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ads Uploader MCP server | Agent MCP Directory > Ads Uploader: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/adsuploader-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ads Uploader: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Ads Uploader at adsuploader.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Ads Uploader | | --- | --- | | Domain | adsuploader.com | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for adsuploader.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://adsuploader.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 851 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:19Z https://adsuploader.com/api/mcp sent initialize result auth-required (HTTP 401) 934 ms - 20:01:57Z https://adsuploader.com/api/mcp sent initialize result auth-required (HTTP 401) 851 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://adsuploader.com/.well-known/oauth-protected-resource" | | Protected resource metadata | adsuploader.com | | Authorization server metadata | adsuploader.com | | Registration endpoint | https://adsuploader.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://adsuploader.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://adsuploader.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://adsuploader.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ads Uploader. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.adsuploader/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/adsuploader-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=adsuploader), read 4 November 2026 - [Ads Uploader website](https://adsuploader.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AfterQuery MCP server | Agent MCP Directory" description: "Does AfterQuery have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/afterquery-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AfterQuery MCP server | Agent MCP Directory > Does AfterQuery have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/afterquery-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AfterQuery: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for AfterQuery (afterquery.com), so the connector had nothing to connect to. Ora's cached score for afterquery.com is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | AfterQuery (registry title: afterquery.com) | | --- | --- | | Domain | afterquery.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for afterquery.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for AfterQuery. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for afterquery.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for AfterQuery. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/afterquery-com/index.md) ## Sources - [Ora score page for afterquery.com](https://ora.ai/score/afterquery.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where AfterQuery was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [AfterQuery website](https://afterquery.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Agent Ready MCP server | Agent MCP Directory" description: "Agent Ready has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/agent-ready-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Agent Ready MCP server | Agent MCP Directory > Agent Ready has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/agent-ready-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Agent Ready: MCP server, CLI and agent surfaces Yes: Agent Ready runs a public MCP server at agent-ready.dev that listed 3 tools to a client with no credentials on 4 November 2026. Examples: scan\_site, get\_scan, ask. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for agent-ready.dev is 94, grade A, read on 5 November 2026. ## Fact sheet | Company | Agent Ready | | --- | --- | | Domain | agent-ready.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 94, grade A; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for agent-ready.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agent-ready.dev/api/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | agent-ready 1.0.0 | | Capabilities | resources, tools, prompts | | Tools | 3 | | Resources | 5 | | Prompts | 3 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,437 ms over 1 attempt | ### Tools listed 3 tools - scan\_site - get\_scan - ask ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:20Z https://agent-ready.dev/api/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1395 ms - 20:01:57Z https://agent-ready.dev/api/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1437 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://agent-ready.dev/api/v1/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Agent Ready. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: agent-ready.dev (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: agent-ready.dev/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: agent-ready.dev/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: agent-ready.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agent-ready-dev/index.md) ## Sources - [Ora score page for agent-ready.dev](https://ora.ai/score/agent-ready.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Where Agent Ready was found](https://github.com/mcp/mlava/agent-ready-mcp), read 4 November 2026 - [Agent Ready website](https://agent-ready.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Agentalog MCP server | Agent MCP Directory" description: "Agentalog has an open MCP server with 46 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/agentalog-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Agentalog MCP server | Agent MCP Directory > Agentalog has an open MCP server with 46 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/agentalog-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Agentalog: MCP server, CLI and agent surfaces Yes: Agentalog runs a public MCP server at agentalog.com that listed 46 tools to a client with no credentials on 4 November 2026. Examples: search\_bundles, get\_bundle, index\_stats. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Agentalog (registry title: Agentalog: Agent Auto Log) | | --- | --- | | Domain | agentalog.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for agentalog.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agentalog.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Agentalog fb0c5518 | | Capabilities | tools, prompts | | Tools | 46 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,316 ms over 1 attempt | ### Tools listed 46 tools; the first 40 names are recorded - search\_bundles - get\_bundle - index\_stats - feed\_find - feed\_posts - feed\_post - feed\_search - mcp\_index\_signals - mcp\_index\_search - check\_tool - listing\_security - listing\_tools - list\_watched\_tools - watch\_tool - unwatch\_tool - list\_plans - buy\_plan - cancel\_plan - claude\_code\_allowlist - watch\_alerts - a2a\_agent\_search - a2a\_agent - briefings\_topics - briefings\_links - api\_index - health - create\_guest - list\_listings - list\_mcp\_servers - get\_listing - get\_listing\_readme - listing\_updates - listing\_history - go\_listing - like\_listing - list\_comments - create\_listing - listing\_status - submit\_okf - billing ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:21Z https://agentalog.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2689 ms - 20:01:59Z https://agentalog.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2316 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://agentalog.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Agentalog. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: agentalog.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.agentalog/meta-agent-tools | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agentalog-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=agentalog), read 4 November 2026 - [Agentalog website](https://agentalog.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AgentBIT MCP server | Agent MCP Directory" description: "AgentBIT has an open MCP server with 101 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/agentbit-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AgentBIT MCP server | Agent MCP Directory > AgentBIT has an open MCP server with 101 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/agentbit-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # AgentBIT: MCP server, CLI and agent surfaces Yes: AgentBIT runs a public MCP server at agentbit.app that listed 101 tools to a client with no credentials on 4 November 2026. Examples: agentbit\_discover, agentbit\_route, agentbit.address\_eip55. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | AgentBIT | | --- | --- | | Domain | agentbit.app | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for agentbit.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agentbit.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | agentbit 1.7.0 | | Capabilities | tools | | Tools | 101 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 714 ms over 1 attempt | ### Tools listed 101 tools; the first 40 names are recorded - agentbit\_discover - agentbit\_route - agentbit.address\_eip55 - agentbit.agent\_counter - agentbit.agent\_list - agentbit.agent\_memory - agentbit.ai\_ask - agentbit.ai\_classify - agentbit.ai\_extract - agentbit.ai\_summarize - agentbit.ai\_translate - agentbit.amazon\_search - agentbit.browser\_render - agentbit.business\_identity - agentbit.company\_brief - agentbit.company\_enrich - agentbit.company\_research - agentbit.content\_moderate - agentbit.contract\_audit - agentbit.convert\_csv\_json - agentbit.convert\_json\_csv - agentbit.convert\_xml\_json - agentbit.counterparty\_risk - agentbit.counterparty\_verify - agentbit.crypto\_trader\_kit - agentbit.decode\_base58 - agentbit.decode\_base64 - agentbit.decode\_hex - agentbit.decode\_url - agentbit.defi\_yields - agentbit.discover - agentbit.dns\_inspect - agentbit.domain\_dossier - agentbit.domain\_intel - agentbit.email\_deliverability - agentbit.encode\_base58 - agentbit.encode\_base64 - agentbit.encode\_hex - agentbit.encode\_url - agentbit.endpoint\_monitor ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:20Z https://agentbit.app/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1132 ms - 20:01:57Z https://agentbit.app/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 714 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://agentbit.app/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AgentBIT. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: agentbit.app (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.agentbit/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agentbit-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=agentbit), read 4 November 2026 - [AgentBIT website](https://agentbit.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AgentData MCP server | Agent MCP Directory" description: "AgentData: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/agentdata-run site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AgentData MCP server | Agent MCP Directory > AgentData: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/agentdata-run Site: Agent MCP Directory Last reviewed: 2026-11-05 # AgentData: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AgentData at mcp.useagentdata.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AgentData | | --- | --- | | Domain | agentdata.run | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for agentdata.run when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.useagentdata.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,083 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:21Z https://mcp.useagentdata.com/mcp sent initialize result auth-required (HTTP 401) 1541 ms - 20:01:59Z https://mcp.useagentdata.com/mcp sent initialize result auth-required (HTTP 401) 2083 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.useagentdata.com/.well-known/oauth-protected-resource/mcp", scope="agentdata" | | Protected resource metadata | mcp.useagentdata.com | | Authorization server metadata | useagentdata.com | | Registration endpoint | https://useagentdata.com/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.useagentdata.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.useagentdata.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://useagentdata.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AgentData. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agentdata-run/index.md) ## Sources - [AgentData website](https://agentdata.run), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AgentHub MCP server | Agent MCP Directory" description: "Does AgentHub have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/agenthublabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AgentHub MCP server | Agent MCP Directory > Does AgentHub have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/agenthublabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AgentHub: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for AgentHub (agenthublabs.com), so the connector had nothing to connect to. Ora's cached score for agenthublabs.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | AgentHub (registry title: agenthublabs.com) | | --- | --- | | Domain | agenthublabs.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for agenthublabs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for AgentHub. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for agenthublabs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for AgentHub. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agenthublabs-com/index.md) ## Sources - [Ora score page for agenthublabs.com](https://ora.ai/score/agenthublabs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/leaderboard) - [Where AgentHub was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [AgentHub website](https://agenthublabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AgenticWebScore MCP server | Agent MCP Directory" description: "AgenticWebScore has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/agenticwebscore-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AgenticWebScore MCP server | Agent MCP Directory > AgenticWebScore has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/agenticwebscore-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AgenticWebScore: MCP server, CLI and agent surfaces Yes: AgenticWebScore runs a public MCP server at agenticwebscore.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: scan\_site, get\_score, list\_checks. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | AgenticWebScore | | --- | --- | | Domain | agenticwebscore.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for agenticwebscore.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agenticwebscore.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | com.agenticwebscore/scan 0.3.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 151 ms over 1 attempt | ### Tools listed 4 tools - scan\_site - get\_score - list\_checks - get\_report ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:21Z https://agenticwebscore.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 830 ms - 20:01:57Z https://agenticwebscore.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 151 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://agenticwebscore.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AgenticWebScore. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: agenticwebscore.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.agenticwebscore/scan | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agenticwebscore-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=agenticwebscore), read 4 November 2026 - [AgenticWebScore website](https://agenticwebscore.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Agilitycms MCP server | Agent MCP Directory" description: "Agilitycms: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/agilitycms-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Agilitycms MCP server | Agent MCP Directory > Agilitycms: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/agilitycms-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Agilitycms: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Agilitycms at mcp.agilitycms.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Agilitycms | | --- | --- | | Domain | agilitycms.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for agilitycms.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.agilitycms.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 869 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:22Z https://mcp.agilitycms.com/api/mcp sent initialize result auth-required (HTTP 401) 1928 ms - 20:01:58Z https://mcp.agilitycms.com/api/mcp sent initialize result auth-required (HTTP 401) 869 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.agilitycms.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.agilitycms.com | | Authorization server metadata | mcp.agilitycms.com | | Registration endpoint | https://mcp.agilitycms.com/api/auth/register | ### The sign-in route, step by step 1. Request `https://mcp.agilitycms.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.agilitycms.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.agilitycms.com/api/auth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Agilitycms. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.agilitycms/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agilitycms-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=agilitycms), read 4 November 2026 - [Agilitycms website](https://agilitycms.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ahrefs MCP server | Agent MCP Directory" description: "Ahrefs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ahrefs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ahrefs MCP server | Agent MCP Directory > Ahrefs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ahrefs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ahrefs: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Ahrefs at api.ahrefs.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Ahrefs | | --- | --- | | Domain | ahrefs.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,176 on the list of 4 November 2026 | | Ora score | 72, grade B; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ahrefs.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.ahrefs.com/mcp/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,110 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:58Z https://api.ahrefs.com/mcp/mcp sent initialize result auth-required (HTTP 401) 661 ms - 20:01:34Z https://api.ahrefs.com/mcp/mcp sent initialize result auth-required (HTTP 401) 1110 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.ahrefs.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.ahrefs.com | | Authorization server metadata | api.ahrefs.com | | Registration endpoint | https://api.ahrefs.com/mcp/register | ### The sign-in route, step by step 1. Request `https://api.ahrefs.com/mcp/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.ahrefs.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.ahrefs.com/mcp/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ahrefs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.ahrefs/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ahrefs-com/index.md) ## Sources - [Ora score page for ahrefs.com](https://ora.ai/score/ahrefs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Where Ahrefs was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.ahrefs%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ahrefs), read 4 November 2026 - [Ahrefs website](https://ahrefs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "aictrl MCP server | Agent MCP Directory" description: "aictrl: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aictrl-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # aictrl MCP server | Agent MCP Directory > aictrl: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/aictrl-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # aictrl: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for aictrl at aictrl.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | aictrl | | --- | --- | | Domain | aictrl.dev | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for aictrl.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://aictrl.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 852 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:21Z https://aictrl.dev/mcp sent initialize result auth-required (HTTP 401) 1124 ms - 20:01:58Z https://aictrl.dev/mcp sent initialize result auth-required (HTTP 401) 852 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource="https://aictrl.dev/mcp", resource_metadata="https://aictrl.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | aictrl.dev | | Authorization server metadata | aictrl.dev | | Registration endpoint | https://aictrl.dev/oauth/register | ### The sign-in route, step by step 1. Request `https://aictrl.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://aictrl.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://aictrl.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for aictrl. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.aictrl/aictrl | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aictrl-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=aictrl), read 4 November 2026 - [aictrl website](https://aictrl.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Aider MCP server | Agent MCP Directory" description: "Does Aider have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aider-chat site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Aider MCP server | Agent MCP Directory > Does Aider have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/aider-chat Site: Agent MCP Directory Last reviewed: 2026-11-05 # Aider: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Aider (aider.chat), so the connector had nothing to connect to. Ora's cached score for aider.chat is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Aider | | --- | --- | | Domain | aider.chat | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for aider.chat, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Aider. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for aider.chat, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Aider. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aider-chat/index.md) ## Sources - [Ora score page for aider.chat](https://ora.ai/score/aider.chat?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/leaderboard) - [Where Aider was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Aider website](https://aider.chat), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "aikstockdata MCP server | Agent MCP Directory" description: "aikstockdata has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aikstockdata-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # aikstockdata MCP server | Agent MCP Directory > aikstockdata has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/aikstockdata-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # aikstockdata: MCP server, CLI and agent surfaces Yes: aikstockdata runs a public MCP server at mcp.aikstockdata.com that listed 12 tools to a client with no credentials on 4 November 2026. Examples: get\_today, search\_stock, get\_stock. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | aikstockdata (registry title: aikstockdata: Korean Stock Data) | | --- | --- | | Domain | aikstockdata.com | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for aikstockdata.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.aikstockdata.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | aikstockdata-mcp 2.1.2 | | Capabilities | tools | | Tools | 12 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 128 ms over 1 attempt | ### Tools listed 12 tools - get\_today - search\_stock - get\_stock - get\_rankings - get\_market\_summary - get\_data\_urls - get\_earnings - get\_history - get\_disclosure\_impact - get\_earnings\_calendar - get\_disclosures - list\_stocks ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:21Z https://mcp.aikstockdata.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 656 ms - 20:01:58Z https://mcp.aikstockdata.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 128 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.aikstockdata.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for aikstockdata. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: aikstockdata.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.aikstockdata/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aikstockdata-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=aikstockdata), read 4 November 2026 - [aikstockdata website](https://aikstockdata.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AI Mail MCP server | Agent MCP Directory" description: "AI Mail MCP: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/aimailmcp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AI Mail MCP server | Agent MCP Directory > AI Mail MCP: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/aimailmcp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AI Mail MCP: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AI Mail MCP at aimailmcp.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AI Mail MCP | | --- | --- | | Domain | aimailmcp.com | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for aimailmcp.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://aimailmcp.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 902 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:23Z https://aimailmcp.com/mcp sent initialize result auth-required (HTTP 401) 1578 ms - 20:01:59Z https://aimailmcp.com/mcp sent initialize result auth-required (HTTP 401) 902 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://aimailmcp.com/.well-known/oauth-protected-resource" | | Protected resource metadata | aimailmcp.com | | Authorization server metadata | aimailmcp.com | | Registration endpoint | https://aimailmcp.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://aimailmcp.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://aimailmcp.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://aimailmcp.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AI Mail MCP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.aimailmcp/mail | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aimailmcp-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=aimailmcp), read 4 November 2026 - [AI Mail MCP website](https://aimailmcp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Airbrake MCP server | Agent MCP Directory" description: "Does Airbrake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/airbrake-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Airbrake MCP server | Agent MCP Directory > Does Airbrake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/airbrake-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Airbrake: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Airbrake (airbrake.io), so the connector had nothing to connect to. Ora's cached score for airbrake.io is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Airbrake (registry title: airbrake.io) | | --- | --- | | Domain | airbrake.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for airbrake.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Airbrake. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for airbrake.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Airbrake. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/airbrake-io/index.md) ## Sources - [Ora score page for airbrake.io](https://ora.ai/score/airbrake.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where Airbrake was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Airbrake website](https://airbrake.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Airbyte MCP server | Agent MCP Directory" description: "Airbyte: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/airbyte-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Airbyte MCP server | Agent MCP Directory > Airbyte: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/airbyte-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Airbyte: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Airbyte at mcp.airbyte.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Airbyte | | --- | --- | | Domain | airbyte.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 79, grade B; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for airbyte.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.airbyte.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,170 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:23Z https://mcp.airbyte.com/mcp sent initialize result auth-required (HTTP 401) 1764 ms - 20:01:59Z https://mcp.airbyte.com/mcp sent initialize result auth-required (HTTP 401) 1170 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer scope="openid email profile", resource_metadata="https://mcp.airbyte.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.airbyte.com | | Authorization server metadata | mcp.airbyte.com | | Registration endpoint | https://mcp.airbyte.com/register | ### The sign-in route, step by step 1. Request `https://mcp.airbyte.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.airbyte.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.airbyte.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Airbyte. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: airbyte.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/airbyte-com/index.md) ## Sources - [Ora score page for airbyte.com](https://ora.ai/score/airbyte.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/score) - [Airbyte website](https://airbyte.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Airport Lounge List MCP server | Agent MCP Directory" description: "Airport Lounge List: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/airportloungelist-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Airport Lounge List MCP server | Agent MCP Directory > Airport Lounge List: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/airportloungelist-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Airport Lounge List: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Airport Lounge List at mcp.airportloungelist.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Airport Lounge List | | --- | --- | | Domain | airportloungelist.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for airportloungelist.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.airportloungelist.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 429 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:23Z https://mcp.airportloungelist.com/mcp sent initialize result auth-required (HTTP 401) 860 ms - 20:01:59Z https://mcp.airportloungelist.com/mcp sent initialize result auth-required (HTTP 401) 429 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer scope="read", resource_metadata="https://mcp.airportloungelist.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.airportloungelist.com | | Authorization server metadata | mcp.airportloungelist.com | | Registration endpoint | https://mcp.airportloungelist.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.airportloungelist.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.airportloungelist.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.airportloungelist.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Airport Lounge List. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.airportloungelist.mcp/lounges | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/airportloungelist-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=airportloungelist), read 4 November 2026 - [Airport Lounge List website](https://airportloungelist.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Airtable MCP server | Agent MCP Directory" description: "Airtable: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/airtable-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Airtable MCP server | Agent MCP Directory > Airtable: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/airtable-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Airtable: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Airtable at mcp.airtable.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Airtable | | --- | --- | | Domain | airtable.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,917 on the list of 4 November 2026 | | Ora score | 57, grade C; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for airtable.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.airtable.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 705 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:00Z https://mcp.airtable.com/mcp sent initialize result auth-required (HTTP 401) 622 ms - 20:01:36Z https://mcp.airtable.com/mcp sent initialize result auth-required (HTTP 401) 705 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.airtable.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.airtable.com | | Authorization server metadata | airtable.com | | Registration endpoint | https://airtable.com/oauth2/v1/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.airtable.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.airtable.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://airtable.com/oauth2/v1/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Airtable. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: airtable.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.airtable/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/airtable-com/index.md) ## Sources - [Ora score page for airtable.com](https://ora.ai/score/airtable.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Where Airtable was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=airtable), read 4 November 2026 - [Airtable website](https://airtable.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Airweave MCP server | Agent MCP Directory" description: "Airweave: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/airweave-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Airweave MCP server | Agent MCP Directory > Airweave: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/airweave-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Airweave: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Airweave; the connector's guess at mcp.airweave.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Airweave (registry title: airweave.ai) | | --- | --- | | Domain | airweave.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 78, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for airweave.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.airweave.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,327 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:24Z https://mcp.airweave.ai/mcp sent initialize result auth-required (HTTP 401) 1247 ms - 20:02:00Z https://mcp.airweave.ai/mcp sent initialize result auth-required (HTTP 401) 1327 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.airweave.ai | | Authorization server metadata | mcp.airweave.ai | | Registration endpoint | https://mcp.airweave.ai/register | ### The sign-in route, step by step 1. Request `https://mcp.airweave.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.airweave.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.airweave.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Airweave. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/airweave-ai/index.md) ## Sources - [Ora score page for airweave.ai](https://ora.ai/score/airweave.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Airweave was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Airweave website](https://airweave.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AIS Trail MCP server | Agent MCP Directory" description: "AIS Trail has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aistrail-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AIS Trail MCP server | Agent MCP Directory > AIS Trail has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/aistrail-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AIS Trail: MCP server, CLI and agent surfaces Yes: AIS Trail runs a public MCP server at api.aistrail.com that listed 11 tools to a client with no credentials on 4 November 2026. Examples: search\_vessels, get\_vessel, vessels\_in\_area. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | AIS Trail | | --- | --- | | Domain | aistrail.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for aistrail.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.aistrail.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | aistrail-ais 1.5.2 | | Capabilities | tools | | Tools | 11 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 404 ms over 1 attempt | ### Tools listed 11 tools - search\_vessels - get\_vessel - vessels\_in\_area - vessels\_near - vessel\_track - data\_status - find\_port - vessel\_port\_calls - port\_calls - vessel\_events - lookup\_vessels ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:23Z https://api.aistrail.com/mcp sent initialize, notifications/initialized, tools/list result initialized-no-tools (HTTP 200) 630 ms - 20:02:00Z https://api.aistrail.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 404 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.aistrail.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AIS Trail. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.aistrail/ais | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aistrail-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=aistrail), read 4 November 2026 - [AIS Trail website](https://aistrail.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Aiven MCP server | Agent MCP Directory" description: "Does Aiven have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aiven-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Aiven MCP server | Agent MCP Directory > Does Aiven have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/aiven-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Aiven: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Aiven (aiven.io), so the connector had nothing to connect to. Ora's cached score for aiven.io is 76, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Aiven (registry title: Aiven MCP) | | --- | --- | | Domain | aiven.io | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | None found | | Ora score | 76, grade B; Ora scanned the domain on 25 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for aiven.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Aiven. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for aiven.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (io.aiven/mcp) | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Aiven. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: aiven.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.aiven/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aiven-io/index.md) ## Sources - [Ora score page for aiven.io](https://ora.ai/score/aiven.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 September 2026, read from GET /api/leaderboard) - [Where Aiven was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.aiven%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=aiven), read 4 November 2026 - [Aiven website](https://aiven.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Akiflow MCP server | Agent MCP Directory" description: "Akiflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/akiflow-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Akiflow MCP server | Agent MCP Directory > Akiflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/akiflow-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Akiflow: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Akiflow at mcp.akiflow.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Akiflow | | --- | --- | | Domain | akiflow.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for akiflow.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.akiflow.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 486 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:24Z https://mcp.akiflow.com/mcp sent initialize result auth-required (HTTP 401) 410 ms - 20:02:00Z https://mcp.akiflow.com/mcp sent initialize result auth-required (HTTP 401) 486 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Akiflow MCP", resource_metadata="https://mcp.akiflow.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.akiflow.com | | Authorization server metadata | web.akiflow.com | | Registration endpoint | https://web.akiflow.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.akiflow.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.akiflow.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://web.akiflow.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Akiflow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.akiflow/akiflow | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/akiflow-com/index.md) ## Sources - [Ora score page for akiflow.com](https://ora.ai/score/akiflow.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Where Akiflow was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.akiflow%2Fakiflow), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=akiflow), read 4 November 2026 - [Akiflow website](https://akiflow.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Alchemy MCP server | Agent MCP Directory" description: "Alchemy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/alchemy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Alchemy MCP server | Agent MCP Directory > Alchemy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/alchemy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Alchemy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Alchemy at mcp.alchemy.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Alchemy (registry title: Alchemy MCP Server) | | --- | --- | | Domain | alchemy.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 7,936 on the list of 4 November 2026 | | Ora score | 78, grade B; Ora scanned the domain on 14 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for alchemy.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.alchemy.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,181 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:13Z https://mcp.alchemy.com/mcp sent initialize result auth-required (HTTP 401) 540 ms - 20:01:53Z https://mcp.alchemy.com/mcp sent initialize result auth-required (HTTP 401) 1181 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.alchemy.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.alchemy.com | | Authorization server metadata | auth.alchemy.com | | Registration endpoint | https://auth.alchemy.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.alchemy.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.alchemy.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.alchemy.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Alchemy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.alchemy/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/alchemy-com/index.md) ## Sources - [Ora score page for alchemy.com](https://ora.ai/score/alchemy.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 September 2026, read from GET /api/score) - [Where Alchemy was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.alchemy%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=alchemy), read 4 November 2026 - [Alchemy website](https://alchemy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AlfaNest MCP server | Agent MCP Directory" description: "AlfaNest: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/alfanestlabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AlfaNest MCP server | Agent MCP Directory > AlfaNest: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/alfanestlabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AlfaNest: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AlfaNest at relay.alfanestlabs.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AlfaNest (registry title: AlfaNest Relay) | | --- | --- | | Domain | alfanestlabs.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for alfanestlabs.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://relay.alfanestlabs.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 494 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:24Z https://relay.alfanestlabs.com/mcp sent initialize result auth-required (HTTP 401) 700 ms - 20:02:00Z https://relay.alfanestlabs.com/mcp sent initialize result auth-required (HTTP 401) 494 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="AlfaNest Relay", resource_metadata="https://relay.alfanestlabs.com/.well-known/oauth-protected-resource" | | Protected resource metadata | relay.alfanestlabs.com | | Authorization server metadata | relay.alfanestlabs.com | | Registration endpoint | https://relay.alfanestlabs.com/oauth/register | ### The sign-in route, step by step 1. Request `https://relay.alfanestlabs.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://relay.alfanestlabs.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://relay.alfanestlabs.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AlfaNest. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.alfanestlabs/relay | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/alfanestlabs-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=alfanestlabs), read 4 November 2026 - [AlfaNest website](https://alfanestlabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Alidns MCP server | Agent MCP Directory" description: "Does Alidns have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/alidns-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Alidns MCP server | Agent MCP Directory > Does Alidns have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/alidns-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Alidns: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Alidns (alidns.com), so the connector had nothing to connect to. The company was added from the shared crawl, which found /.well-known/mcp.json on the domain. A company can be added by submitting an endpoint. ## Fact sheet | Company | Alidns (registry title: alidns.com) | | --- | --- | | Domain | alidns.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | None found | | Tranco rank | 268 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for alidns.com when asked on 5 November 2026 | | Company found through | the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Alidns. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for alidns.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Alidns. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card (older path) | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | agents.json | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | OAuth authorization server metadata | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/alidns-com/index.md) ## Sources - [Where Alidns was found](https://alidns.com/.well-known/mcp.json), read 4 November 2026 - [Alidns website](https://alidns.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Allbirds MCP server | Agent MCP Directory" description: "Allbirds has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/allbirds-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Allbirds MCP server | Agent MCP Directory > Allbirds has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/allbirds-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Allbirds: MCP server, CLI and agent surfaces Yes: Allbirds runs a public MCP server at www.allbirds.com that listed 1 tool to a client with no credentials on 4 November 2026. Examples: search\_shop\_policies\_and\_faqs. It speaks streamable-http, protocol 2024-11-05. Ora's cached score for allbirds.com is 65, grade C, read on 5 November 2026. ## Fact sheet | Company | Allbirds | | --- | --- | | Domain | allbirds.com | | Category | Consumer (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 65, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for allbirds.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.allbirds.com/api/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | storefront-renderer 0.1.0 | | Capabilities | tools, prompts, resources, logging | | Tools | 1 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 827 ms over 1 attempt | | Documentation | shopify.dev | ### Tools listed 1 tool - search\_shop\_policies\_and\_faqs ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:24Z https://www.allbirds.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 671 ms - 20:02:00Z https://www.allbirds.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 827 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.allbirds.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Allbirds. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: allbirds.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/allbirds-com/index.md) ## Sources - [Allbirds MCP documentation](https://shopify.dev/docs/apps/build/storefront-mcp), read 4 November 2026 - [Ora score page for allbirds.com](https://ora.ai/score/allbirds.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Allbirds website](https://allbirds.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Almxpp MCP server | Agent MCP Directory" description: "Almxpp has an open MCP server with 104 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/almxpp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Almxpp MCP server | Agent MCP Directory > Almxpp has an open MCP server with 104 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/almxpp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Almxpp: MCP server, CLI and agent surfaces Yes: Almxpp runs a public MCP server at api.almxpp.com that listed 104 tools to a client with no credentials on 4 November 2026. Examples: validate\_best\_practices, find\_extensions, ado\_create\_bug\_from\_test. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Almxpp (registry title: ALM X++ MCP Server) | | --- | --- | | Domain | almxpp.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for almxpp.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.almxpp.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | ALMXPPMCP 1.6.548 | | Capabilities | logging, prompts, resources, tools | | Tools | 104 | | Resources | 4 | | Prompts | 4 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,221 ms over 2 attempts | | Result | initialize error: Protocol version '2026-07-28' is not available through the initialize handshake. | ### Tools listed 104 tools; the first 40 names are recorded - validate\_best\_practices - find\_extensions - ado\_create\_bug\_from\_test - dmf\_import\_file - search\_d365\_code - dmf\_transform\_excel - generate\_query - ado\_wiki\_delete\_page - appinsights\_diagnose\_slowness - ado\_wiki\_list - get\_object\_details - ado\_query\_workitems - dmf\_apply\_entity\_filter - ado\_update\_workitem - find\_references - ado\_gap\_fit\_analysis - batch\_search - ado\_read\_attachment - erp\_read\_session - trace\_field\_lineage - plan\_and\_execute - find\_similar\_implementations - recommend\_extension\_strategy - diff\_model\_versions - find\_related\_objects - ado\_review\_xpp\_pr - lesson\_save - dmf\_create\_data\_project - find\_entity\_for\_table - summarize\_for\_stakeholder - ado\_create\_regression\_suite - suggest\_refactoring - resync\_devops\_index - erp\_list\_tools - ado\_wiki\_get\_page - dmf - find\_callers - healthcheck - ado\_analyze\_pr\_impact - find\_error\_patterns ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:25Z https://api.almxpp.com/mcp sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1353 ms - 20:02:01Z https://api.almxpp.com/mcp sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1221 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.almxpp.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Almxpp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.almxpp.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/almxpp-com/index.md) ## Sources - [Where Almxpp was found](https://github.com/mcp/alimbenhelal-pro/ALM-XPP-MCP), read 4 November 2026 - [Almxpp website](https://almxpp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Alterlab MCP server | Agent MCP Directory" description: "Alterlab has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/alterlab-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Alterlab MCP server | Agent MCP Directory > Alterlab has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/alterlab-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Alterlab: MCP server, CLI and agent surfaces Yes: Alterlab runs a public MCP server at mcp.alterlab.io that listed 15 tools to a client with no credentials on 4 November 2026. Examples: alterlab\_scrape, alterlab\_extract, alterlab\_screenshot. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Alterlab | | --- | --- | | Domain | alterlab.io | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for alterlab.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.alterlab.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | alterlab 1.0.0 | | Capabilities | tools | | Tools | 15 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 510 ms over 1 attempt | ### Tools listed 15 tools - alterlab\_scrape - alterlab\_extract - alterlab\_screenshot - alterlab\_crawl - alterlab\_search - alterlab\_map - alterlab\_batch\_scrape - alterlab\_batch - alterlab\_estimate\_cost - alterlab\_pricing - alterlab\_feedback - alterlab\_create\_account - alterlab\_create\_api\_key - search\_alterlab - read\_alterlab\_page ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:24Z https://mcp.alterlab.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 544 ms - 20:02:00Z https://mcp.alterlab.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 510 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.alterlab.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Alterlab. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.alterlab/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/alterlab-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=alterlab), read 4 November 2026 - [Alterlab website](https://alterlab.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AltoRank MCP server | Agent MCP Directory" description: "AltoRank: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/altorank-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AltoRank MCP server | Agent MCP Directory > AltoRank: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/altorank-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # AltoRank: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AltoRank at app.altorank.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AltoRank | | --- | --- | | Domain | altorank.co | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for altorank.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.altorank.co/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 697 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:25Z https://app.altorank.co/api/mcp sent initialize result auth-required (HTTP 401) 838 ms - 20:02:01Z https://app.altorank.co/api/mcp sent initialize result auth-required (HTTP 401) 697 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.altorank.co/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | app.altorank.co | | Authorization server metadata | app.altorank.co | | Registration endpoint | https://app.altorank.co/api/oauth/register | ### The sign-in route, step by step 1. Request `https://app.altorank.co/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.altorank.co/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.altorank.co/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AltoRank. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.altorank/altorank | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/altorank-co/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=altorank), read 4 November 2026 - [AltoRank website](https://altorank.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "amCharts MCP server | Agent MCP Directory" description: "amCharts has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/amcharts-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # amCharts MCP server | Agent MCP Directory > amCharts has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/amcharts-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # amCharts: MCP server, CLI and agent surfaces Yes: amCharts runs a public MCP server at mcp.amcharts.com that listed 12 tools to a client with no credentials on 4 November 2026. Examples: list\_chart\_types, get\_chart\_reference, get\_core\_reference. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | amCharts (registry title: amCharts 5) | | --- | --- | | Domain | amcharts.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for amcharts.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.amcharts.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | amcharts5 1.9.4 | | Capabilities | tools, resources | | Tools | 12 | | Resources | 14 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,544 ms over 1 attempt | ### Tools listed 12 tools - list\_chart\_types - get\_chart\_reference - get\_core\_reference - search\_docs - get\_section - get\_quick\_start - search\_all - get\_doc - get\_api\_reference - list\_examples - get\_example - list\_geodata ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:27Z https://mcp.amcharts.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 2967 ms - 20:02:03Z https://mcp.amcharts.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 2544 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.amcharts.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for amCharts. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/amcharts-com/index.md) ## Sources - [amCharts website](https://amcharts.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Amika MCP server | Agent MCP Directory" description: "Does Amika have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/amika-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Amika MCP server | Agent MCP Directory > Does Amika have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/amika-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Amika: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Amika (amika.dev), so the connector had nothing to connect to. Ora's cached score for amika.dev is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Amika (registry title: amika.dev) | | --- | --- | | Domain | amika.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 3 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for amika.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Amika. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for amika.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Amika. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/amika-dev/index.md) ## Sources - [Ora score page for amika.dev](https://ora.ai/score/amika.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 October 2026, read from GET /api/leaderboard) - [Where Amika was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Amika website](https://amika.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Amplify MCP server | Agent MCP Directory" description: "Amplify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/amplify-is site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Amplify MCP server | Agent MCP Directory > Amplify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/amplify-is Site: Agent MCP Directory Last reviewed: 2026-11-05 # Amplify: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Amplify at app.amplify.is answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Amplify | | --- | --- | | Domain | amplify.is | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for amplify.is when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.amplify.is/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 140 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:25Z https://app.amplify.is/mcp sent initialize result auth-required (HTTP 401) 280 ms - 20:02:01Z https://app.amplify.is/mcp sent initialize result auth-required (HTTP 401) 140 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://app.amplify.is/.well-known/oauth-protected-resource", scope="read build publish" | | Protected resource metadata | app.amplify.is | | Authorization server metadata | app.amplify.is | | Registration endpoint | https://app.amplify.is/oauth/register | ### The sign-in route, step by step 1. Request `https://app.amplify.is/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.amplify.is/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.amplify.is/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Amplify. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: amplify.is (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/amplify-is/index.md) ## Sources - [Amplify website](https://amplify.is), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Amplitude MCP server | Agent MCP Directory" description: "Amplitude: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/amplitude-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Amplitude MCP server | Agent MCP Directory > Amplitude: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/amplitude-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Amplitude: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Amplitude at mcp.amplitude.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Amplitude | | --- | --- | | Domain | amplitude.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 243 on the list of 4 November 2026 | | Ora score | 91, grade A; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for amplitude.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.amplitude.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,962 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://mcp.amplitude.com/mcp sent initialize result auth-required (HTTP 401) 1777 ms - 20:01:29Z https://mcp.amplitude.com/mcp sent initialize result auth-required (HTTP 401) 1962 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.amplitude.com/.well-known/oauth-protected-resource", error="invalid_request", error_description="Missing authorization header" | | Protected resource metadata | mcp.amplitude.com | | Authorization server metadata | mcp.amplitude.com | | Registration endpoint | https://mcp.amplitude.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.amplitude.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.amplitude.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.amplitude.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Amplitude. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: amplitude.com (JSON, via the shared crawl). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.amplitude/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/amplitude-com/index.md) ## Sources - [Ora score page for amplitude.com](https://ora.ai/score/amplitude.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Where Amplitude was found](https://github.com/mcp/amplitude/mcp-server-guide), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=amplitude), read 4 November 2026 - [Amplitude website](https://amplitude.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Anchore MCP server | Agent MCP Directory" description: "Does Anchore have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/anchore-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Anchore MCP server | Agent MCP Directory > Does Anchore have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/anchore-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Anchore: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Anchore (anchore.com), so the connector had nothing to connect to. Ora's cached score for anchore.com is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Anchore (registry title: anchore.com) | | --- | --- | | Domain | anchore.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 6 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for anchore.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Anchore. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for anchore.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Anchore. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/anchore-com/index.md) ## Sources - [Ora score page for anchore.com](https://ora.ai/score/anchore.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 September 2026, read from GET /api/leaderboard) - [Where Anchore was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Anchore website](https://anchore.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Andi MCP server | Agent MCP Directory" description: "Andi: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/andiai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Andi MCP server | Agent MCP Directory > Andi: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/andiai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Andi: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Andi at api.andiai.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Andi (registry title: Andi Search) | | --- | --- | | Domain | andiai.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 86, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for andiai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.andiai.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,139 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:26Z https://api.andiai.com/mcp sent initialize result auth-required (HTTP 401) 1260 ms - 20:02:02Z https://api.andiai.com/mcp sent initialize result auth-required (HTTP 401) 1139 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", error="invalid_token", resource_metadata="https://api.andiai.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.andiai.com | ### The sign-in route, step by step 1. Request `https://api.andiai.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Andi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: api.andiai.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.andiai/andi-search | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/andiai-com/index.md) ## Sources - [Ora score page for andiai.com](https://ora.ai/score/andiai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Andi was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.andiai%2Fandi-search), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=andiai), read 4 November 2026 - [Andi website](https://andiai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Anima MCP server | Agent MCP Directory" description: "Anima: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/animaapp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Anima MCP server | Agent MCP Directory > Anima: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/animaapp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Anima: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Anima at public-api.animaapp.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Anima (registry title: Anima MCP Server) | | --- | --- | | Domain | animaapp.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 67, grade C; Ora scanned the domain on 18 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for animaapp.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://public-api.animaapp.com/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,538 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:27Z https://public-api.animaapp.com/v1/mcp sent initialize result auth-required (HTTP 401) 1702 ms - 20:02:02Z https://public-api.animaapp.com/v1/mcp sent initialize result auth-required (HTTP 401) 1538 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://public-api.animaapp.com/.well-known/oauth-protected-resource" | | Protected resource metadata | public-api.animaapp.com | | Authorization server metadata | public-api.animaapp.com | | Registration endpoint | https://public-api.animaapp.com/oauth/register | ### The sign-in route, step by step 1. Request `https://public-api.animaapp.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://public-api.animaapp.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://public-api.animaapp.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Anima. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.github.AnimaApp/anima | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/animaapp-com/index.md) ## Sources - [Ora score page for animaapp.com](https://ora.ai/score/animaapp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=animaapp), read 4 November 2026 - [Anima website](https://animaapp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AnomalyArmor MCP server | Agent MCP Directory" description: "AnomalyArmor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/anomalyarmor-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AnomalyArmor MCP server | Agent MCP Directory > AnomalyArmor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/anomalyarmor-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # AnomalyArmor: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AnomalyArmor at mcp.anomalyarmor.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AnomalyArmor | | --- | --- | | Domain | anomalyarmor.ai | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 92, grade A; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for anomalyarmor.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.anomalyarmor.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 954 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:27Z https://mcp.anomalyarmor.ai/mcp sent initialize result auth-required (HTTP 401) 1716 ms - 20:02:02Z https://mcp.anomalyarmor.ai/mcp sent initialize result auth-required (HTTP 401) 954 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.anomalyarmor.ai | | Authorization server metadata | clerk.anomalyarmor.ai | | Registration endpoint | https://clerk.anomalyarmor.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.anomalyarmor.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.anomalyarmor.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AnomalyArmor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.anomalyarmor.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: anomalyarmor.ai/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: anomalyarmor.ai/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.anomalyarmor/armor-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/anomalyarmor-ai/index.md) ## Sources - [Ora score page for anomalyarmor.ai](https://ora.ai/score/anomalyarmor.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Where AnomalyArmor was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.anomalyarmor%2Farmor-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=anomalyarmor), read 4 November 2026 - [AnomalyArmor website](https://anomalyarmor.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ansvar MCP server | Agent MCP Directory" description: "Ansvar: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ansvar-eu site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ansvar MCP server | Agent MCP Directory > Ansvar: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ansvar-eu Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ansvar: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Ansvar at gateway.ansvar.eu answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Ansvar (registry title: Ansvar: EU Compliance & Legal Intelligence) | | --- | --- | | Domain | ansvar.eu | | Category | Security (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for ansvar.eu when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://gateway.ansvar.eu/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 971 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:27Z https://gateway.ansvar.eu/mcp sent initialize result auth-required (HTTP 401) 1002 ms - 20:02:02Z https://gateway.ansvar.eu/mcp sent initialize result auth-required (HTTP 401) 971 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://gateway.ansvar.eu/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | gateway.ansvar.eu | | Authorization server metadata | auth.ansvar.eu | | Registration endpoint | https://auth.ansvar.eu/realms/ansvar/clients-registrations/openid-connect | ### The sign-in route, step by step 1. Request `https://gateway.ansvar.eu/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://gateway.ansvar.eu/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.ansvar.eu/realms/ansvar/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ansvar. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: eu.ansvar/dutch-law, eu.ansvar/eu-regulations, eu.ansvar/french-law and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ansvar-eu/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ansvar), read 4 November 2026 - [Ansvar website](https://ansvar.eu), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Antevo MCP server | Agent MCP Directory" description: "Antevo has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/antevo-ch site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Antevo MCP server | Agent MCP Directory > Antevo has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/antevo-ch Site: Agent MCP Directory Last reviewed: 2026-11-05 # Antevo: MCP server, CLI and agent surfaces Yes: Antevo runs a public MCP server at trademark.antevo.ch that listed 16 tools to a client with no credentials on 4 November 2026. Examples: screen\_mark, check\_names, suggest\_classes. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Antevo (registry title: The 07:00 Brief) | | --- | --- | | Domain | antevo.ch | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for antevo.ch when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://trademark.antevo.ch/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | antevo-trademark 1.0.0 | | Capabilities | prompts, resources, tools | | Tools | 16 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 687 ms over 1 attempt | ### Tools listed 16 tools - screen\_mark - check\_names - suggest\_classes - holder\_read - opposition\_window - filing\_landscape - my\_conflicts - my\_deadlines - my\_watches - company\_file - follow\_filer - watch\_mark - dismiss\_conflict - filer\_activity - run\_investigation - get\_credit\_balance ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:27Z https://trademark.antevo.ch/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 637 ms - 20:02:03Z https://trademark.antevo.ch/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 687 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://trademark.antevo.ch/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Antevo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ch.antevo/0700-brief, ch.antevo/executive, ch.antevo/mandates and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/antevo-ch/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=antevo), read 4 November 2026 - [Antevo website](https://antevo.ch), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Anthropic MCP server | Agent MCP Directory" description: "Does Anthropic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/anthropic-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Anthropic MCP server | Agent MCP Directory > Does Anthropic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/anthropic-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Anthropic: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Anthropic (anthropic.com), so the connector had nothing to connect to. A CLI is on record: @anthropic-ai/claude-code on npm. Ora's cached score for anthropic.com is 71, grade B, read on 5 November 2026. ## Fact sheet | Company | Anthropic | | --- | --- | | Domain | anthropic.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 327 on the list of 4 November 2026 | | Ora score | 71, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for anthropic.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Anthropic. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for anthropic.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | @anthropic-ai/claude-code on npm (page) | | --- | --- | | Exists | yes | | Latest version | 2.1.318 | | Last publish | 3 November 2026 | | Command names | claude | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/anthropic-com/index.md) ## Sources - [Ora score page for anthropic.com](https://ora.ai/score/anthropic.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Anthropic was found](https://docs.anthropic.com/en/docs/agents-and-tools/mcp-connector), read 4 November 2026 - [Anthropic website](https://anthropic.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Antwork MCP server | Agent MCP Directory" description: "Antwork: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/antwork-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Antwork MCP server | Agent MCP Directory > Antwork: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/antwork-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Antwork: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Antwork at api.antwork.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Antwork | | --- | --- | | Domain | antwork.io | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 55, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for antwork.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.antwork.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 489 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:27Z https://api.antwork.io/mcp sent initialize result auth-required (HTTP 401) 576 ms - 20:02:03Z https://api.antwork.io/mcp sent initialize result auth-required (HTTP 401) 489 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.antwork.io/.well-known/oauth-protected-resource/mcp", resource="https://api.antwork.io/mcp", authorization_server_metadata_uri="https://api.antwork.io/.well-known/oauth-authorization-server" | | Protected resource metadata | api.antwork.io | | Authorization server metadata | api.antwork.io | | Registration endpoint | https://api.antwork.io/oauth/register | ### The sign-in route, step by step 1. Request `https://api.antwork.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.antwork.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.antwork.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Antwork. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: antwork.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.antwork/social | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/antwork-io/index.md) ## Sources - [Ora score page for antwork.io](https://ora.ai/score/antwork.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=antwork), read 4 November 2026 - [Antwork website](https://antwork.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Anurag MCP server | Agent MCP Directory" description: "Anurag has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/anuragd-me site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Anurag MCP server | Agent MCP Directory > Anurag has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/anuragd-me Site: Agent MCP Directory Last reviewed: 2026-11-05 # Anurag: MCP server, CLI and agent surfaces Yes: Anurag runs a public MCP server at metro-mcp.anuragd.me that listed 18 tools to a client with no credentials on 4 November 2026. Examples: get\_station\_predictions, search\_stations, get\_stations\_by\_line. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for anuragd.me is 54, grade C, read on 5 November 2026. ## Fact sheet | Company | Anurag | | --- | --- | | Domain | anuragd.me | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 54, grade C; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for anuragd.me, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://metro-mcp.anuragd.me/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | transit-mcp 6.1.0 | | Capabilities | extensions, tools, resources, prompts | | Tools | 18 | | Resources | 3 | | Prompts | 3 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 313 ms over 1 attempt | ### Tools listed 18 tools - get\_station\_predictions - search\_stations - get\_stations\_by\_line - get\_all\_stations - get\_station\_transfers - get\_incidents - get\_elevator\_incidents - get\_bus\_predictions - get\_bus\_routes - get\_bus\_stops - get\_bus\_positions - get\_train\_positions - get\_route\_info - find\_transit - plan\_trip - get\_departures - get\_service\_status - get\_vehicle\_status ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:28Z https://metro-mcp.anuragd.me/sse sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1019 ms - 20:02:03Z https://metro-mcp.anuragd.me/sse sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 313 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://metro-mcp.anuragd.me/sse` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Anurag. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/anuragd-me/index.md) ## Sources - [Ora score page for anuragd.me](https://ora.ai/score/anuragd.me?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/score) - [Where Anurag was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Anurag website](https://anuragd.me), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Any.do MCP server | Agent MCP Directory" description: "Any.do: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/any-do site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Any.do MCP server | Agent MCP Directory > Any.do: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/any-do Site: Agent MCP Directory Last reviewed: 2026-11-05 # Any.do: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Any.do; the connector's guess at mcp.any.do answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Any.do | | --- | --- | | Domain | any.do | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for any.do, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.any.do/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 643 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:28Z https://mcp.any.do/mcp sent initialize result auth-required (HTTP 401) 793 ms - 20:02:04Z https://mcp.any.do/mcp sent initialize result auth-required (HTTP 401) 643 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.any.do/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.any.do | | Authorization server metadata | mcp.any.do | | Registration endpoint | https://mcp.any.do/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.any.do/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.any.do/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.any.do/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Any.do. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.any.do (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: any.do/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/any-do/index.md) ## Sources - [Ora score page for any.do](https://ora.ai/score/any.do?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Any.do was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Any.do website](https://any.do), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Anytype MCP server | Agent MCP Directory" description: "Does Anytype have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/anytype-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Anytype MCP server | Agent MCP Directory > Does Anytype have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/anytype-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Anytype: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Anytype (anytype.io), so the connector had nothing to connect to. Ora's cached score for anytype.io is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Anytype (registry title: anytype.io) | | --- | --- | | Domain | anytype.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 18 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for anytype.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Anytype. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for anytype.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Anytype. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/anytype-io/index.md) ## Sources - [Ora score page for anytype.io](https://ora.ai/score/anytype.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 August 2026, read from GET /api/leaderboard) - [Where Anytype was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Anytype website](https://anytype.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Apex AI Academy MCP server | Agent MCP Directory" description: "Apex AI Academy has an open MCP server with 30 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/apexai-academy site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Apex AI Academy MCP server | Agent MCP Directory > Apex AI Academy has an open MCP server with 30 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/apexai-academy Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apex AI Academy: MCP server, CLI and agent surfaces Yes: Apex AI Academy runs a public MCP server at apexai.academy that listed 30 tools to a client with no credentials on 4 November 2026. Examples: list\_courses, list\_lessons, get\_lesson. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Apex AI Academy | | --- | --- | | Domain | apexai.academy | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for apexai.academy when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://apexai.academy/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | apex-ai-academy 1.0.0 | | Capabilities | tools | | Tools | 30 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,069 ms over 1 attempt | ### Tools listed 30 tools - list\_courses - list\_lessons - get\_lesson - search - latest\_news - list\_deep\_dives - get\_resources - get\_pricing - subscribe\_link - get\_premium\_lesson - get\_progress - mark\_lesson\_complete - forum\_search - forum\_read - forum\_post - forum\_hello - forum\_reply - forum\_category\_create - agent\_handoff - agent\_notes\_get - agent\_notes\_set - forum\_edit - pair\_agent - forum\_polls\_list - forum\_poll\_vote - agent\_signup - agent\_me - agent\_progress - agent\_quiz\_answer - agent\_delete\_account ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:29Z https://apexai.academy/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1283 ms - 20:02:05Z https://apexai.academy/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1069 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://apexai.academy/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Apex AI Academy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: academy.apexai/apex-ai-academy | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apexai-academy/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=apexai), read 4 November 2026 - [Apex AI Academy website](https://apexai.academy), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AWS MCP server | Agent MCP Directory" description: "AWS has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/api-aws site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AWS MCP server | Agent MCP Directory > AWS has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/api-aws Site: Agent MCP Directory Last reviewed: 2026-11-05 # AWS: MCP server, CLI and agent surfaces Yes: AWS runs a public MCP server at knowledge-mcp.global.api.aws that listed 5 tools to a client with no credentials on 4 November 2026. Examples: aws\_\_\_read\_documentation, aws\_\_\_search\_documentation, aws\_\_\_list\_regions. It speaks streamable-http, protocol 2025-03-26. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | AWS | | --- | --- | | Domain | api.aws | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 1,262 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for api.aws when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://knowledge-mcp.global.api.aws | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | AWSKnowledgeMCP 1.0.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 406 ms over 1 attempt | ### Tools listed 5 tools - aws\_\_\_read\_documentation - aws\_\_\_search\_documentation - aws\_\_\_list\_regions - aws\_\_\_get\_regional\_availability - aws\_\_\_retrieve\_skill ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://knowledge-mcp.global.api.aws sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 400 ms - 20:01:32Z https://knowledge-mcp.global.api.aws sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 406 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://knowledge-mcp.global.api.aws` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AWS. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/api-aws/index.md) ## Sources - [Where AWS was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Apify MCP server | Agent MCP Directory" description: "Apify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/apify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Apify MCP server | Agent MCP Directory > Apify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/apify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apify: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Apify at mcp.apify.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Apify | | --- | --- | | Domain | apify.com | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 96, grade A+; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for apify.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.apify.com | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,494 ms over 1 attempt | | Documentation | docs.apify.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:29Z https://mcp.apify.com sent initialize result auth-required (HTTP 401) 1524 ms - 20:02:05Z https://mcp.apify.com sent initialize result auth-required (HTTP 401) 1494 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer header. Manage tokens at https://console.apify.com/account/integrations" | | Protected resource metadata | mcp.apify.com | | Authorization server metadata | console-backend.apify.com | | Registration endpoint | https://console-backend.apify.com/oauth/apps | | Client ID metadata documents | supported | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.apify.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.apify.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://console-backend.apify.com/oauth/apps` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | apify-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 1.11.0 | | Last publish | 29 October 2026 | | Command names | actor, apify, apify-cli | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: apify.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: apify.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.apify/apify-mcp-server, io.github.4robot/hexadata, io.github.AndriyVK/apify-document-tools and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apify-com/index.md) ## Sources - [Apify MCP documentation](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Ora score page for apify.com](https://ora.ai/score/apify.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=apify), read 4 November 2026 - [Apify website](https://apify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "APITube MCP server | Agent MCP Directory" description: "APITube has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/apitube-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # APITube MCP server | Agent MCP Directory > APITube has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/apitube-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # APITube: MCP server, CLI and agent surfaces Yes: APITube runs a public MCP server at mcp.apitube.io that listed 2 tools to a client with no credentials on 4 November 2026. Examples: search\_news, suggest. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | APITube (registry title: APITube News) | | --- | --- | | Domain | apitube.io | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for apitube.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.apitube.io/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | APITube News MCP-Server 1.0.0 | | Capabilities | tools, prompts | | Tools | 2 | | Resources | 0 | | Prompts | 4 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 626 ms over 1 attempt | ### Tools listed 2 tools - search\_news - suggest ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:29Z https://mcp.apitube.io/ sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 708 ms - 20:02:04Z https://mcp.apitube.io/ sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 626 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.apitube.io/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for APITube. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.apitube/news | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apitube-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=apitube), read 4 November 2026 - [APITube website](https://apitube.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "APIVerve MCP server | Agent MCP Directory" description: "APIVerve: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/apiverve-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # APIVerve MCP server | Agent MCP Directory > APIVerve: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/apiverve-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # APIVerve: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for APIVerve at api.apiverve.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | APIVerve | | --- | --- | | Domain | apiverve.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for apiverve.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.apiverve.com/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 120 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:29Z https://api.apiverve.com/v1/mcp sent initialize result auth-required (HTTP 401) 256 ms - 20:02:04Z https://api.apiverve.com/v1/mcp sent initialize result auth-required (HTTP 401) 120 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.apiverve.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.apiverve.com | | Authorization server metadata | api.apiverve.com | | Registration endpoint | https://api.apiverve.com/register | ### The sign-in route, step by step 1. Request `https://api.apiverve.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.apiverve.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.apiverve.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for APIVerve. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.apiverve/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apiverve-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=apiverve), read 4 November 2026 - [APIVerve website](https://apiverve.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Apollo.io MCP server | Agent MCP Directory" description: "Apollo.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM." canonical: https://agentmcpdirectory.com/directory/apollo-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Apollo.io MCP server | Agent MCP Directory > Apollo.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM. Source: https://agentmcpdirectory.com/directory/apollo-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apollo.io: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Apollo.io at mcp.apollo.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Apollo.io | | --- | --- | | Domain | apollo.io | | Category | CRM (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 7,431 on the list of 4 November 2026 | | Ora score | 76, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for apollo.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.apollo.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,091 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:12Z https://mcp.apollo.io/mcp sent initialize result auth-required (HTTP 401) 717 ms - 20:01:51Z https://mcp.apollo.io/mcp sent initialize result auth-required (HTTP 401) 1091 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Apollo.io", resource_metadata="https://mcp.apollo.io/.well-known/oauth-protected-resource", scope="read_user_profile app_scopes people_bulk_match organizations_bulk_enrich organizations_enrich people_match webhook_result_read mixed_people_api_search organizations_job_posting mixed_companies_search organizations_search contact_write contact_update contacts_search contact_read contacts_deduplicate account_write account_update context_center_read context_center_write emailer_campaigns_search emailer_campaigns_create emailer_campaigns_update emailer_campaigns_approve emailer_campaigns_add_contact_ids emailer_campaigns_remove_or_stop_contact_ids emailer_schedules_list emailer_messages_search emailer_messages_create emailer_messages_send_now emailer_messages_email_send_status emailer_messages_get_content emailer_campaigns_activity_feed report_sync agent_task email_accounts_list | | Protected resource metadata | mcp.apollo.io | | Authorization server metadata | mcp.apollo.io | | Registration endpoint | https://mcp.apollo.io/api/v1/oauth/applications/register_oauth_client | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.apollo.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.apollo.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.apollo.io/api/v1/oauth/applications/register_oauth_client` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Apollo.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apollo-io/index.md) ## Sources - [Ora score page for apollo.io](https://ora.ai/score/apollo.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Apollo.io website](https://apollo.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Apollo GraphQL MCP server | Agent MCP Directory" description: "Apollo GraphQL has an open MCP server with 48 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/apollographql-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Apollo GraphQL MCP server | Agent MCP Directory > Apollo GraphQL has an open MCP server with 48 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/apollographql-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apollo GraphQL: MCP server, CLI and agent surfaces Yes: Apollo GraphQL runs a public MCP server at mcp.apollographql.com, found by guessing the subdomain, and it listed 48 tools to a client with no credentials on 4 November 2026. Examples: GetGraphArtifactTags, LintSchema, DeleteApiKey. It speaks streamable-http, protocol 2025-11-25. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | Apollo GraphQL (registry title: apollographql.com) | | --- | --- | | Domain | apollographql.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 80, grade B; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for apollographql.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.apollographql.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | graphos-mcp-server 1.20.0 | | Capabilities | tools | | Tools | 48 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,027 ms over 1 attempt | ### Tools listed 48 tools; the first 40 names are recorded - GetGraphArtifactTags - LintSchema - DeleteApiKey - GetLatestLaunch - PublishPersistedQueries - GetProposals - PublishReadme - GetTopOperations - GetSupergraphSchema - RunSchemaCheck - DeleteSubgraph - RunSubgraphCheck - AddProposalComment - PublishGraphSchema - RenameApiKey - ReviewProposal - GetGraphArtifact - GetSchemaChecks - GetSubgraphMetrics - DeleteGraph - GetVariantDetails - PublishProposalRevision - UpdateProposalStatus - GetLintResults - GetContractConfig - GetPersistedQueryListStatus - GetClientMetrics - CreateApiKey - GetSubgraphSchema - TagGraphArtifact - ApolloConnectorsSpec - ApolloDocsSearch - GetProposal - GetApiKeys - PublishSubgraph - GetGraphSchema - GetLaunch - GetReadme - GetOperationMetrics - ApolloDocsRead ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:31Z https://mcp.apollographql.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1819 ms - 20:02:05Z https://mcp.apollographql.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1027 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.apollographql.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Apollo GraphQL. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apollographql-com/index.md) ## Sources - [Ora score page for apollographql.com](https://ora.ai/score/apollographql.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/score) - [Where Apollo GraphQL was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Apollo GraphQL website](https://apollographql.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Apoxy MCP server | Agent MCP Directory" description: "Does Apoxy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/apoxy-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Apoxy MCP server | Agent MCP Directory > Does Apoxy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/apoxy-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apoxy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Apoxy (apoxy.dev), so the connector had nothing to connect to. Ora's cached score for apoxy.dev is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Apoxy (registry title: apoxy.dev) | | --- | --- | | Domain | apoxy.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for apoxy.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Apoxy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for apoxy.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Apoxy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apoxy-dev/index.md) ## Sources - [Ora score page for apoxy.dev](https://ora.ai/score/apoxy.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/leaderboard) - [Where Apoxy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Apoxy website](https://apoxy.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Appcircle MCP server | Agent MCP Directory" description: "Appcircle: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/appcircle-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Appcircle MCP server | Agent MCP Directory > Appcircle: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/appcircle-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Appcircle: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Appcircle at mcp.appcircle.io asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Appcircle (registry title: Appcircle MCP) | | --- | --- | | Domain | appcircle.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 71, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for appcircle.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.appcircle.io | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 352 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:30Z https://mcp.appcircle.io sent initialize result auth-required-no-oauth (HTTP 401) 349 ms - 20:02:05Z https://mcp.appcircle.io sent initialize result auth-required-no-oauth (HTTP 401) 352 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | Bearer | ### The sign-in route, step by step 1. Request `https://mcp.appcircle.io` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Appcircle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.appcircle/appcircle-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appcircle-io/index.md) ## Sources - [Ora score page for appcircle.io](https://ora.ai/score/appcircle.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Appcircle was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.appcircle%2Fappcircle-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=appcircle), read 4 November 2026 - [Appcircle website](https://appcircle.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Appian MCP server | Agent MCP Directory" description: "Does Appian have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/appian-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Appian MCP server | Agent MCP Directory > Does Appian have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/appian-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Appian: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Appian (appian.com), so the connector had nothing to connect to. Ora's cached score for appian.com is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Appian (registry title: appian.com) | | --- | --- | | Domain | appian.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 24 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for appian.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Appian. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for appian.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Appian. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appian-com/index.md) ## Sources - [Ora score page for appian.com](https://ora.ai/score/appian.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 October 2026, read from GET /api/leaderboard) - [Where Appian was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Appian website](https://appian.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Appllama MCP server | Agent MCP Directory" description: "Appllama: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/appllama-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Appllama MCP server | Agent MCP Directory > Appllama: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/appllama-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Appllama: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Appllama at mcp.appllama.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Appllama | | --- | --- | | Domain | appllama.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 44, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for appllama.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.appllama.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 381 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:31Z https://mcp.appllama.io/mcp sent initialize result auth-required (HTTP 401) 611 ms - 20:02:05Z https://mcp.appllama.io/mcp sent initialize result auth-required (HTTP 401) 381 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.appllama.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.appllama.io | | Authorization server metadata | mcp.appllama.io | | Registration endpoint | https://mcp.appllama.io/register | ### The sign-in route, step by step 1. Request `https://mcp.appllama.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.appllama.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.appllama.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Appllama. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.appllama/appllama | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appllama-io/index.md) ## Sources - [Ora score page for appllama.io](https://ora.ai/score/appllama.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=appllama), read 4 November 2026 - [Appllama website](https://appllama.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AppmanAi MCP server | Agent MCP Directory" description: "AppmanAi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce." canonical: https://agentmcpdirectory.com/directory/appmanai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AppmanAi MCP server | Agent MCP Directory > AppmanAi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce. Source: https://agentmcpdirectory.com/directory/appmanai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AppmanAi: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AppmanAi at appmanai.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AppmanAi | | --- | --- | | Domain | appmanai.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for appmanai.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://appmanai.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 526 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:31Z https://appmanai.com/api/mcp sent initialize result auth-required (HTTP 401) 614 ms - 20:02:05Z https://appmanai.com/api/mcp sent initialize result auth-required (HTTP 401) 526 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://appmanai.com/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | appmanai.com | | Authorization server metadata | appmanai.com | | Registration endpoint | https://appmanai.com/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://appmanai.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://appmanai.com/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://appmanai.com/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AppmanAi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.appmanai/appmanai-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appmanai-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=appmanai), read 4 November 2026 - [AppmanAi website](https://appmanai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AppsFlyer MCP server | Agent MCP Directory" description: "AppsFlyer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/appsflyer-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AppsFlyer MCP server | Agent MCP Directory > AppsFlyer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/appsflyer-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AppsFlyer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AppsFlyer at mcp.appsflyer.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AppsFlyer (registry title: appsflyer.com) | | --- | --- | | Domain | appsflyer.com | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 551 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for appsflyer.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.appsflyer.com/auth/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 435 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://mcp.appsflyer.com/auth/mcp sent initialize result auth-required (HTTP 401) 309 ms - 20:01:30Z https://mcp.appsflyer.com/auth/mcp sent initialize result auth-required (HTTP 401) 435 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://mcp.appsflyer.com/.well-known/oauth-protected-resource/auth/mcp" | | Protected resource metadata | mcp.appsflyer.com | | Authorization server metadata | mcp.appsflyer.com | | Registration endpoint | https://mcp.appsflyer.com/register | ### The sign-in route, step by step 1. Request `https://mcp.appsflyer.com/auth/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.appsflyer.com/.well-known/oauth-protected-resource/auth/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.appsflyer.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AppsFlyer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.appsflyer.com (JSON, via the shared crawl). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.appsflyer/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appsflyer-com/index.md) ## Sources - [Ora score page for appsflyer.com](https://ora.ai/score/appsflyer.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where AppsFlyer was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.appsflyer%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=appsflyer), read 4 November 2026 - [AppsFlyer website](https://appsflyer.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AppSignal MCP server | Agent MCP Directory" description: "Does AppSignal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/appsignal-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AppSignal MCP server | Agent MCP Directory > Does AppSignal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/appsignal-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AppSignal: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for AppSignal (appsignal.com), so the connector had nothing to connect to. Ora's cached score for appsignal.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | AppSignal (registry title: appsignal.com) | | --- | --- | | Domain | appsignal.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for appsignal.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for AppSignal. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for appsignal.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for AppSignal. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: appsignal.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appsignal-com/index.md) ## Sources - [Ora score page for appsignal.com](https://ora.ai/score/appsignal.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where AppSignal was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [AppSignal website](https://appsignal.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "App Store Tracker MCP server | Agent MCP Directory" description: "App Store Tracker has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/appstoretracker-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # App Store Tracker MCP server | Agent MCP Directory > App Store Tracker has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/appstoretracker-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # App Store Tracker: MCP server, CLI and agent surfaces Yes: App Store Tracker runs a public MCP server at www.appstoretracker.com that listed 16 tools to a client with no credentials on 4 November 2026. Examples: search\_apps, get\_app\_details, get\_rankings. It speaks streamable-http, protocol 2024-11-05. Ora's cached score for appstoretracker.com is 43, grade D, read on 5 November 2026. ## Fact sheet | Company | App Store Tracker | | --- | --- | | Domain | appstoretracker.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 43, grade D; Ora scanned the domain on 12 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for appstoretracker.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.appstoretracker.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | appstoretracker-mcp 1.0.0 | | Capabilities | tools | | Tools | 16 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 888 ms over 1 attempt | ### Tools listed 16 tools - search\_apps - get\_app\_details - get\_rankings - add\_to\_watchlist - get\_similar\_apps - get\_reviews - get\_timeline - get\_categories - get\_ranking\_history - get\_revenue\_history - get\_keywords - get\_ads - get\_tracked\_apps - get\_keyword\_watchlist - search\_designs - list\_design\_apps ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:31Z https://www.appstoretracker.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1044 ms - 20:02:06Z https://www.appstoretracker.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 888 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.appstoretracker.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for App Store Tracker. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.appstoretracker/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appstoretracker-com/index.md) ## Sources - [Ora score page for appstoretracker.com](https://ora.ai/score/appstoretracker.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=appstoretracker), read 4 November 2026 - [App Store Tracker website](https://appstoretracker.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AppVeyor MCP server | Agent MCP Directory" description: "Does AppVeyor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/appveyor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AppVeyor MCP server | Agent MCP Directory > Does AppVeyor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/appveyor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AppVeyor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for AppVeyor (appveyor.com), so the connector had nothing to connect to. Ora's cached score for appveyor.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | AppVeyor (registry title: appveyor.com) | | --- | --- | | Domain | appveyor.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 7 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for appveyor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for AppVeyor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for appveyor.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for AppVeyor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/appveyor-com/index.md) ## Sources - [Ora score page for appveyor.com](https://ora.ai/score/appveyor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 August 2026, read from GET /api/leaderboard) - [Where AppVeyor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [AppVeyor website](https://appveyor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Apricot MCP server | Agent MCP Directory" description: "Apricot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/apricot-tools site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Apricot MCP server | Agent MCP Directory > Apricot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/apricot-tools Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apricot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Apricot at mcp.apricot.tools answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Apricot | | --- | --- | | Domain | apricot.tools | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for apricot.tools when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.apricot.tools/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 649 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:31Z https://mcp.apricot.tools/ sent initialize result auth-required (HTTP 401) 729 ms - 20:02:06Z https://mcp.apricot.tools/ sent initialize result auth-required (HTTP 401) 649 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer | | Protected resource metadata | mcp.apricot.tools | | Authorization server metadata | mcp.apricot.tools | | Registration endpoint | https://mcp.apricot.tools/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.apricot.tools/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.apricot.tools/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.apricot.tools/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Apricot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/apricot-tools/index.md) ## Sources - [Apricot website](https://apricot.tools), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Aptible MCP server | Agent MCP Directory" description: "Does Aptible have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aptible-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Aptible MCP server | Agent MCP Directory > Does Aptible have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/aptible-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Aptible: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Aptible (aptible.com), so the connector had nothing to connect to. Ora's cached score for aptible.com is 63, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Aptible | | --- | --- | | Domain | aptible.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for aptible.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Aptible. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for aptible.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Aptible. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aptible-com/index.md) ## Sources - [Ora score page for aptible.com](https://ora.ai/score/aptible.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Aptible was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Aptible website](https://aptible.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ara MCP server | Agent MCP Directory" description: "Does Ara have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/ara-so site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ara MCP server | Agent MCP Directory > Does Ara have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/ara-so Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ara: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ara (ara.so), so the connector had nothing to connect to. Ora's cached score for ara.so is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ara (registry title: ara.so) | | --- | --- | | Domain | ara.so | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ara.so, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ara. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ara.so, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ara. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ara-so/index.md) ## Sources - [Ora score page for ara.so](https://ora.ai/score/ara.so?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where Ara was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ara website](https://ara.so), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Archbee MCP server | Agent MCP Directory" description: "Does Archbee have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/archbee-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Archbee MCP server | Agent MCP Directory > Does Archbee have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/archbee-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Archbee: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Archbee (archbee.com), so the connector had nothing to connect to. Ora's cached score for archbee.com is 63, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Archbee (registry title: archbee.com) | | --- | --- | | Domain | archbee.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for archbee.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Archbee. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for archbee.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Archbee. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/archbee-com/index.md) ## Sources - [Ora score page for archbee.com](https://ora.ai/score/archbee.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/leaderboard) - [Where Archbee was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Archbee website](https://archbee.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Archil MCP server | Agent MCP Directory" description: "Does Archil have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/archil-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Archil MCP server | Agent MCP Directory > Does Archil have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/archil-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Archil: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Archil (archil.com), so the connector had nothing to connect to. Ora's cached score for archil.com is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Archil (registry title: archil.com) | | --- | --- | | Domain | archil.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for archil.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Archil. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for archil.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Archil. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/archil-com/index.md) ## Sources - [Ora score page for archil.com](https://ora.ai/score/archil.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/leaderboard) - [Where Archil was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Archil website](https://archil.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Arcmira MCP server | Agent MCP Directory" description: "Arcmira: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/arcmira-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Arcmira MCP server | Agent MCP Directory > Arcmira: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/arcmira-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Arcmira: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Arcmira at mcp.arcmira.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Arcmira (registry title: Arcmira: YouTube Transcript Search) | | --- | --- | | Domain | arcmira.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for arcmira.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.arcmira.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 213 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:32Z https://mcp.arcmira.com/mcp sent initialize result auth-required (HTTP 401) 1370 ms - 20:02:06Z https://mcp.arcmira.com/mcp sent initialize result auth-required (HTTP 401) 213 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.arcmira.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.arcmira.com | | Authorization server metadata | api.arcmira.com | | Registration endpoint | https://api.arcmira.com/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.arcmira.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.arcmira.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.arcmira.com/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Arcmira. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/arcmira-com/index.md) ## Sources - [Arcmira website](https://arcmira.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Arga Labs MCP server | Agent MCP Directory" description: "Does Arga Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/argalabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Arga Labs MCP server | Agent MCP Directory > Does Arga Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/argalabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Arga Labs: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Arga Labs (argalabs.com), so the connector had nothing to connect to. Ora's cached score for argalabs.com is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Arga Labs (registry title: argalabs.com) | | --- | --- | | Domain | argalabs.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 2 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for argalabs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Arga Labs. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for argalabs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Arga Labs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/argalabs-com/index.md) ## Sources - [Ora score page for argalabs.com](https://ora.ai/score/argalabs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 October 2026, read from GET /api/leaderboard) - [Where Arga Labs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Arga Labs website](https://argalabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Arkm MCP server | Agent MCP Directory" description: "Arkm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/arkm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Arkm MCP server | Agent MCP Directory > Arkm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/arkm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Arkm: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Arkm at mcp.arkm.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Arkm (registry title: Arkham) | | --- | --- | | Domain | arkm.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for arkm.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.arkm.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 611 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:32Z https://mcp.arkm.com/mcp sent initialize result auth-required (HTTP 401) 590 ms - 20:02:07Z https://mcp.arkm.com/mcp sent initialize result auth-required (HTTP 401) 611 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="arkham", resource_metadata="https://mcp.arkm.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.arkm.com | | Authorization server metadata | api.arkm.com | | Registration endpoint | https://api.arkm.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.arkm.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.arkm.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.arkm.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Arkm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: arkm.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.arkm/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/arkm-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=arkm), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Arrumou MCP server | Agent MCP Directory" description: "Arrumou: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/arrumou-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Arrumou MCP server | Agent MCP Directory > Arrumou: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/arrumou-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Arrumou: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Arrumou at app.arrumou.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Arrumou (registry title: Arrumou Neural) | | --- | --- | | Domain | arrumou.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for arrumou.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.arrumou.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 971 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:33Z https://app.arrumou.com/mcp sent initialize result auth-required (HTTP 401) 1113 ms - 20:02:07Z https://app.arrumou.com/mcp sent initialize result auth-required (HTTP 401) 971 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.arrumou.com/.well-known/oauth-protected-resource/mcp", error_description="Informe um token de acesso Bearer." | | Protected resource metadata | app.arrumou.com | | Authorization server metadata | app.arrumou.com | | Registration endpoint | https://app.arrumou.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://app.arrumou.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.arrumou.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.arrumou.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Arrumou. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/arrumou-com/index.md) ## Sources - [Arrumou website](https://arrumou.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Arthur MCP server | Agent MCP Directory" description: "Does Arthur have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/arthur-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Arthur MCP server | Agent MCP Directory > Does Arthur have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/arthur-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Arthur: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Arthur (arthur.ai), so the connector had nothing to connect to. Ora's cached score for arthur.ai is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Arthur (registry title: arthur.ai) | | --- | --- | | Domain | arthur.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 30 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for arthur.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Arthur. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for arthur.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Arthur. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/arthur-ai/index.md) ## Sources - [Ora score page for arthur.ai](https://ora.ai/score/arthur.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 September 2026, read from GET /api/leaderboard) - [Where Arthur was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Arthur website](https://arthur.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Artie MCP server | Agent MCP Directory" description: "Artie: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/artie-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Artie MCP server | Agent MCP Directory > Artie: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/artie-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Artie: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Artie; the connector's guess at mcp.artie.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Artie (registry title: artie.com) | | --- | --- | | Domain | artie.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 68, grade C; Ora scanned the domain on 14 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for artie.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.artie.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,590 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:34Z https://mcp.artie.com/mcp sent initialize result auth-required (HTTP 401) 1613 ms - 20:02:08Z https://mcp.artie.com/mcp sent initialize result auth-required (HTTP 401) 1590 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.artie.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.artie.com | | Authorization server metadata | loyal-explorer-16.authkit.app | | Registration endpoint | https://loyal-explorer-16.authkit.app/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.artie.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.artie.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://loyal-explorer-16.authkit.app/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Artie. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: artie.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/artie-com/index.md) ## Sources - [Ora score page for artie.com](https://ora.ai/score/artie.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 September 2026, read from GET /api/leaderboard) - [Where Artie was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Artie website](https://artie.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Artillery MCP server | Agent MCP Directory" description: "Does Artillery have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/artillery-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Artillery MCP server | Agent MCP Directory > Does Artillery have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/artillery-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Artillery: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Artillery (artillery.io), so the connector had nothing to connect to. Ora's cached score for artillery.io is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Artillery (registry title: artillery.io) | | --- | --- | | Domain | artillery.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for artillery.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Artillery. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for artillery.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Artillery. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/artillery-io/index.md) ## Sources - [Ora score page for artillery.io](https://ora.ai/score/artillery.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Artillery was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Artillery website](https://artillery.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Asana MCP server | Agent MCP Directory" description: "Asana: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/asana-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Asana MCP server | Agent MCP Directory > Asana: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/asana-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Asana: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Asana at mcp.asana.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Asana | | --- | --- | | Domain | asana.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,240 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for asana.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.asana.com/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 985 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:59Z https://mcp.asana.com/sse sent initialize result auth-required (HTTP 401) 999 ms - 20:01:35Z https://mcp.asana.com/sse sent initialize result auth-required (HTTP 401) 985 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.asana.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.asana.com | | Authorization server metadata | mcp.asana.com | | Registration endpoint | https://mcp.asana.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.asana.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.asana.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.asana.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Asana. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/asana-com/index.md) ## Sources - [Ora score page for asana.com](https://ora.ai/score/asana.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/score) - [Where Asana was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Asana website](https://asana.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ASO Atlas MCP server | Agent MCP Directory" description: "ASO Atlas: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce." canonical: https://agentmcpdirectory.com/directory/asoatlas-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ASO Atlas MCP server | Agent MCP Directory > ASO Atlas: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce. Source: https://agentmcpdirectory.com/directory/asoatlas-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ASO Atlas: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ASO Atlas at asoatlas.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ASO Atlas | | --- | --- | | Domain | asoatlas.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for asoatlas.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://asoatlas.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 632 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:33Z https://asoatlas.com/mcp sent initialize result auth-required (HTTP 401) 972 ms - 20:02:07Z https://asoatlas.com/mcp sent initialize result auth-required (HTTP 401) 632 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://asoatlas.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | asoatlas.com | | Authorization server metadata | asoatlas.com | | Registration endpoint | https://asoatlas.com/oauth/register | ### The sign-in route, step by step 1. Request `https://asoatlas.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://asoatlas.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://asoatlas.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ASO Atlas. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.asoatlas/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/asoatlas-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=asoatlas), read 4 November 2026 - [ASO Atlas website](https://asoatlas.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Assembla MCP server | Agent MCP Directory" description: "Does Assembla have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/assembla-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Assembla MCP server | Agent MCP Directory > Does Assembla have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/assembla-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Assembla: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Assembla (assembla.com), so the connector had nothing to connect to. Ora's cached score for assembla.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Assembla (registry title: assembla.com) | | --- | --- | | Domain | assembla.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 31 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for assembla.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Assembla. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for assembla.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Assembla. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/assembla-com/index.md) ## Sources - [Ora score page for assembla.com](https://ora.ai/score/assembla.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 August 2026, read from GET /api/leaderboard) - [Where Assembla was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Assembla website](https://assembla.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AssemblyAI MCP server | Agent MCP Directory" description: "AssemblyAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/assemblyai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AssemblyAI MCP server | Agent MCP Directory > AssemblyAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/assemblyai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # AssemblyAI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for AssemblyAI at mcp.assemblyai.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | AssemblyAI | | --- | --- | | Domain | assemblyai.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for assemblyai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.assemblyai.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,293 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:34Z https://mcp.assemblyai.com/mcp sent initialize result auth-required (HTTP 401) 1804 ms - 20:02:08Z https://mcp.assemblyai.com/mcp sent initialize result auth-required (HTTP 401) 1293 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.assemblyai.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.assemblyai.com | | Authorization server metadata | auth.assemblyai.com | | Registration endpoint | https://auth.assemblyai.com/v1/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.assemblyai.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.assemblyai.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.assemblyai.com/v1/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AssemblyAI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.assemblyai.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.assemblyai/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/assemblyai-com/index.md) ## Sources - [Ora score page for assemblyai.com](https://ora.ai/score/assemblyai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where AssemblyAI was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.assemblyai%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=assemblyai), read 4 November 2026 - [AssemblyAI website](https://assemblyai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "assistant-ui MCP server | Agent MCP Directory" description: "Does assistant-ui have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/assistant-ui-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # assistant-ui MCP server | Agent MCP Directory > Does assistant-ui have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/assistant-ui-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # assistant-ui: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for assistant-ui (assistant-ui.com), so the connector had nothing to connect to. Ora's cached score for assistant-ui.com is 79, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | assistant-ui (registry title: assistant-ui.com) | | --- | --- | | Domain | assistant-ui.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 79, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for assistant-ui.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for assistant-ui. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for assistant-ui.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for assistant-ui. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/assistant-ui-com/index.md) ## Sources - [Ora score page for assistant-ui.com](https://ora.ai/score/assistant-ui.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where assistant-ui was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [assistant-ui website](https://assistant-ui.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Astro MCP server | Agent MCP Directory" description: "Astro has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/astro-build site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Astro MCP server | Agent MCP Directory > Astro has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/astro-build Site: Agent MCP Directory Last reviewed: 2026-11-05 # Astro: MCP server, CLI and agent surfaces Yes: Astro runs a public MCP server at mcp.docs.astro.build that listed 1 tool to a client with no credentials on 4 November 2026. Examples: search\_astro\_docs. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for astro.build is 52, grade C, read on 5 November 2026. ## Fact sheet | Company | Astro | | --- | --- | | Domain | astro.build | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 52, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for astro.build, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.docs.astro.build/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Astro Docs server 1.0.0 | | Capabilities | logging, tools | | Tools | 1 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 486 ms over 1 attempt | ### Tools listed 1 tool - search\_astro\_docs ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:34Z https://mcp.docs.astro.build/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 486 ms - 20:02:08Z https://mcp.docs.astro.build/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 486 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.docs.astro.build/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Astro. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/astro-build/index.md) ## Sources - [Ora score page for astro.build](https://ora.ai/score/astro.build?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/score) - [Where Astro was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Astro website](https://astro.build), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "AthenaHQ MCP server | Agent MCP Directory" description: "AthenaHQ has an open MCP server with 113 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/athenahq-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # AthenaHQ MCP server | Agent MCP Directory > AthenaHQ has an open MCP server with 113 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/athenahq-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # AthenaHQ: MCP server, CLI and agent surfaces Yes: AthenaHQ runs a public MCP server at api.athenahq.ai that listed 113 tools to a client with no credentials on 4 November 2026. Examples: open\_ai\_access, check\_public\_ai\_access, get\_prompt\_schedules. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for athenahq.ai is 67, grade C, read on 5 November 2026. ## Fact sheet | Company | AthenaHQ | | --- | --- | | Domain | athenahq.ai | | Category | Marketing (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 67, grade C; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for athenahq.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.athenahq.ai/api/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | athenahq 0.1.0 | | Capabilities | resources, tools | | Tools | 113 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,816 ms over 1 attempt | ### Tools listed 113 tools; the first 40 names are recorded - open\_ai\_access - check\_public\_ai\_access - get\_prompt\_schedules - get\_ai\_search\_value - get\_prompts - get\_prompt\_tags - get\_personas - get\_topics - get\_competitors - get\_content\_hub\_sheets - get\_tracked\_content - list\_content - get\_content\_detail - get\_content\_citation\_prompts - list\_websites - get\_locations - get\_date\_range - get\_responses - get\_response\_streaming\_status - get\_response\_detail - get\_saved\_views - get\_group\_saved\_views - get\_credits\_organization - get\_credits\_website - get\_groups - get\_group\_detail - get\_share\_of\_voice\_cumulative - get\_share\_of\_voice\_time\_series - get\_citation\_rate\_cumulative - get\_citation\_rate\_time\_series - get\_mention\_rate\_cumulative - get\_mention\_rate\_time\_series - get\_position\_cumulative - get\_position\_time\_series - get\_position\_distribution - query\_metrics - query\_rows - list\_pitches - get\_pitch - get\_sources ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:35Z https://api.athenahq.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1753 ms - 20:02:09Z https://api.athenahq.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1816 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.athenahq.ai/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for AthenaHQ. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.athenahq/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/athenahq-ai/index.md) ## Sources - [Ora score page for athenahq.ai](https://ora.ai/score/athenahq.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/score) - [Where AthenaHQ was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.athenahq%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=athenahq), read 4 November 2026 - [AthenaHQ website](https://athenahq.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Atlassian MCP server | Agent MCP Directory" description: "Atlassian: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/atlassian-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Atlassian MCP server | Agent MCP Directory > Atlassian: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/atlassian-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Atlassian: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Atlassian at mcp.atlassian.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Atlassian | | --- | --- | | Domain | atlassian.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 595 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for atlassian.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.atlassian.com/v1/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 771 ms over 1 attempt | | Documentation | support.atlassian.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://mcp.atlassian.com/v1/mcp sent initialize result auth-required (HTTP 401) 551 ms - 20:01:30Z https://mcp.atlassian.com/v1/mcp sent initialize result auth-required (HTTP 401) 771 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token" | | Authorization server metadata | mcp.atlassian.com | | Registration endpoint | https://mcp.atlassian.com/v1/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.atlassian.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.atlassian.com/v1/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Atlassian. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.atlassian/atlassian-mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/atlassian-com/index.md) ## Sources - [Atlassian MCP documentation](https://support.atlassian.com/rovo/docs/getting-started-with-the-atlassian-remote-mcp-server/), read 4 November 2026 - [Ora score page for atlassian.com](https://ora.ai/score/atlassian.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=atlassian), read 4 November 2026 - [Atlassian website](https://atlassian.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Atom.com MCP server | Agent MCP Directory" description: "Atom.com has an open MCP server with 22 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/atom-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Atom.com MCP server | Agent MCP Directory > Atom.com has an open MCP server with 22 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/atom-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Atom.com: MCP server, CLI and agent surfaces Yes: Atom.com runs a public MCP server at mcp.atom.com that listed 22 tools to a client with no credentials on 4 November 2026. Examples: brainstorm\_names, search\_brandable\_domains, check\_domain\_availability. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for atom.com is 71, grade B, read on 5 November 2026. ## Fact sheet | Company | Atom.com (registry title: Atom.com: Premium Domains) | | --- | --- | | Domain | atom.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 2,522 on the list of 4 November 2026 | | Ora score | 71, grade B; Ora scanned the domain on 26 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for atom.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.atom.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | atom-marketplace-mcp-server 2.0.0 | | Capabilities | tools, resources | | Tools | 22 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,327 ms over 1 attempt | ### Tools listed 22 tools - brainstorm\_names - search\_brandable\_domains - check\_domain\_availability - generate\_domain\_names - appraise\_domain - get\_domain\_details - screen\_trademark\_conflicts - get\_checkout\_link - register\_domain - purchase\_domain - register\_domain\_spt - buy\_ai\_tokens - get\_ai\_tokens\_pay\_link - get\_domain\_register\_pay\_link - get\_domain\_purchase\_pay\_link - get\_domain\_register\_pay\_link\_guest - get\_domain\_purchase\_pay\_link\_guest - get\_domain\_purchase\_coinbase\_pay\_link - get\_add\_funds\_coinbase\_pay\_link - get\_domain\_register\_coinbase\_pay\_link - get\_coinbase\_payment\_status - create\_registrant\_contact ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:00Z https://mcp.atom.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1124 ms - 20:01:36Z https://mcp.atom.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1327 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.atom.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Atom.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: atom.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.atom/premium-domains | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/atom-com/index.md) ## Sources - [Ora score page for atom.com](https://ora.ai/score/atom.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=atom), read 4 November 2026 - [Atom.com website](https://atom.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Attio MCP server | Agent MCP Directory" description: "Attio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/attio-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Attio MCP server | Agent MCP Directory > Attio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/attio-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Attio: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Attio at mcp.attio.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Attio | | --- | --- | | Domain | attio.com | | Category | CRM (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 86, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for attio.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.attio.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 339 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:34Z https://mcp.attio.com/mcp sent initialize result auth-required (HTTP 401) 325 ms - 20:02:08Z https://mcp.attio.com/mcp sent initialize result auth-required (HTTP 401) 339 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.attio.com/.well-known/oauth-protected-resource", scope="openid offline_access mcp" | | Protected resource metadata | mcp.attio.com | | Authorization server metadata | app.attio.com | | Registration endpoint | https://app.attio.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.attio.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.attio.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.attio.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Attio. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: api.attio.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: attio.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: attio.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: attio.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/attio-com/index.md) ## Sources - [Ora score page for attio.com](https://ora.ai/score/attio.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Attio was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Attio website](https://attio.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Audioscrape MCP server | Agent MCP Directory" description: "Audioscrape: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/audioscrape-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Audioscrape MCP server | Agent MCP Directory > Audioscrape: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/audioscrape-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Audioscrape: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Audioscrape at mcp.audioscrape.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Audioscrape | | --- | --- | | Domain | audioscrape.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for audioscrape.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.audioscrape.com | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 387 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:34Z https://mcp.audioscrape.com sent initialize result auth-required (HTTP 401) 463 ms - 20:02:08Z https://mcp.audioscrape.com sent initialize result auth-required (HTTP 401) 387 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="MCP", resource_metadata="https://mcp.audioscrape.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.audioscrape.com | | Authorization server metadata | mcp.audioscrape.com | | Registration endpoint | https://mcp.audioscrape.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.audioscrape.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.audioscrape.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.audioscrape.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Audioscrape. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.audioscrape/audio-intelligence | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/audioscrape-com/index.md) ## Sources - [Where Audioscrape was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=audioscrape), read 4 November 2026 - [Audioscrape website](https://audioscrape.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP servers: API key | Agent MCP Directory" description: "19 MCP endpoints with an API key, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said." canonical: https://agentmcpdirectory.com/directory/auth/api-key site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP servers: API key | Agent MCP Directory > 19 MCP endpoints with an API key, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said. Source: https://agentmcpdirectory.com/directory/auth/api-key Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: API key 19 endpoints use an API key: 0 listed tools to a client with no credentials and 0 answered with a sign-in challenge (tools not seen, not counted). Rows run from Appcircle to testRigor. The server answered 401 or 403 and asks for a key or bearer token with no OAuth metadata for an agent to follow. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Appcircle appcircle.io | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Bitculator bitculator.com | Credential wall API key | – | | – | not read | 2026-11-04 | | Cavyro cavyro.com | Credential wall API key | – | 73 B | yes | not read | 2026-11-04 | | Contentstack contentstack.com | Credential wall API key | – | 67 C | – | no | 2026-11-04 | | Devtron devtron.ai | Credential wall API key | – | 48 C | – | no | 2026-11-04 | | Hookstep hookstep.in | Credential wall API key | – | | – | not read | 2026-11-04 | | Klavis klavis.ai | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Mezmo mezmo.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | Netdata netdata.cloud | Credential wall API key | – | | – | not read | 2026-11-04 | | Northflank northflank.com | Credential wall API key | – | 53 C | – | no | 2026-11-04 | | Oids tryoids.com | Credential wall API key | – | | – | not read | 2026-11-04 | | OneSchema oneschema.co | Credential wall API key | – | 56 C | – | no | 2026-11-04 | | PageProofer pageproofer.com | Credential wall API key | – | | – | not read | 2026-11-04 | | PrintFriendly printfriendly.com | Credential wall API key | – | | yes | not read | 2026-11-04 | | Screenshot Scout screenshotscout.com | Credential wall API key | – | | – | not read | 2026-11-04 | | SmartGate smartgate.network | Credential wall API key | – | | – | not read | 2026-11-04 | | Sonatype sonatype.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | StackOverflow stackoverflow.com | Credential wall API key | – | 23 F | – | no | 2026-11-04 | | testRigor testrigor.com | Credential wall API key | – | 56 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/api-key/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP servers: No authentication | Agent MCP Directory" description: "263 MCP endpoints with no authentication, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said." canonical: https://agentmcpdirectory.com/directory/auth/none site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP servers: No authentication | Agent MCP Directory > 263 MCP endpoints with no authentication, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said. Source: https://agentmcpdirectory.com/directory/auth/none Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: No authentication 263 endpoints use no authentication: 263 listed tools to a client with no credentials and 0 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 1 to 100, from 1102tools to GoSQLX. The server listed its tools to a client that sent no credentials. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 1102tools 1102tools.com | Verified no auth | – | | – | not read | 2026-11-04 | | 2extract 2extract.com | Verified no auth | – | | – | not read | 2026-11-04 | | Agent Ready agent-ready.dev | Verified no auth | – | 94 A | yes | yes | 2026-11-04 | | Agentalog agentalog.com | Verified no auth | – | | yes | not read | 2026-11-04 | | AgentBIT agentbit.app | Verified no auth | – | | yes | not read | 2026-11-04 | | AgenticWebScore agenticwebscore.com | Verified no auth | – | | yes | not read | 2026-11-04 | | aikstockdata aikstockdata.com | Verified no auth | – | | yes | not read | 2026-11-04 | | AIS Trail aistrail.com | Verified no auth | – | | – | not read | 2026-11-04 | | Allbirds allbirds.com | Verified no auth | – | 65 C | – | yes | 2026-11-04 | | Almxpp almxpp.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Alterlab alterlab.io | Verified no auth | – | | – | not read | 2026-11-04 | | Amazon Web Services aws.amazon.com | Verified no auth | awscli | 60 C | – | no | 2026-11-04 | | amCharts amcharts.com | Verified no auth | – | | – | not read | 2026-11-04 | | Antevo antevo.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Anurag anuragd.me | Verified no auth | – | 54 C | – | not read | 2026-11-04 | | Apex AI Academy apexai.academy | Verified no auth | – | | – | not read | 2026-11-04 | | APITube apitube.io | Verified no auth | – | | – | not read | 2026-11-04 | | Apollo GraphQL apollographql.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 80 B | – | no | 2026-11-04 | | App Store Tracker appstoretracker.com | Verified no auth | – | 43 D | – | not read | 2026-11-04 | | Astro astro.build | Verified no auth | – | 52 C | – | no | 2026-11-04 | | AthenaHQ athenahq.ai | Verified no auth | – | 67 C | – | no | 2026-11-04 | | Atom.com atom.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Autodesk autodesk.com | Verified no auth | – | 36 D | – | no | 2026-11-04 | | AWS api.aws | Verified no auth | – | | – | not read | 2026-11-04 | | Ball Ranks ballranks.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Barevalue barevalue.com | Verified no auth | – | | – | not read | 2026-11-04 | | Beglaubigt beglaubigt.de | Verified no auth | – | 49 C | – | no | 2026-11-04 | | BestPrice bestprice.gr | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | BGPT bgpt.pro | Verified no auth | – | | – | not read | 2026-11-04 | | Bibooks bibooks.org | Verified no auth | – | | – | not read | 2026-11-04 | | Bitmovin bitmovin.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | Bowmark bowmark.ai | Verified no auth | – | | – | not read | 2026-11-04 | | BreckenWander breckenwander.com | Verified no auth | – | | – | not read | 2026-11-04 | | Browser Use browser-use.com | Verified no auth | – | 91 A | yes | no | 2026-11-04 | | BuyWhere buywhere.ai | Verified no auth | – | | yes | not read | 2026-11-04 | | Casco casco.com | Verified no auth | – | 41 D | – | no | 2026-11-04 | | Catalystproject catalystproject.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Cerebrium cerebrium.ai | Verified no auth | – | 86 A | – | no | 2026-11-04 | | Chainstack chainstack.com | Verified no auth | – | 71 B | – | not read | 2026-11-04 | | Channel3 trychannel3.com | Verified no auth | – | 92 A | – | no | 2026-11-04 | | Ciphyr ciphyr.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Claude claude.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Clino clino.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Cloudflare cloudflare.com | Verified no auth | wrangler | 82 B | yes | yes | 2026-11-04 | | Clueso clueso.io | Verified no auth | – | 78 B | – | no | 2026-11-04 | | Clutch.co clutch.co | Verified no auth | – | 21 F | – | no | 2026-11-04 | | Codex Reset codex-reset.com | Verified no auth | – | | yes | not read | 2026-11-04 | | CometChat cometchat.com | Verified no auth | – | 56 C | – | not read | 2026-11-04 | | Commsharbor commsharbor.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Context Awesome context-awesome.com | Verified no auth | – | | – | not read | 2026-11-04 | | Context7 context7.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | | Convex convex.dev | Verified no auth; endpoint found by subdomain guess, verified by connecting | convex | 71 B | – | not read | 2026-11-04 | | Courier courier.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 57 C | – | no | 2026-11-04 | | CryptoAPIs IO cryptoapis.io | Verified no auth | – | | – | not read | 2026-11-04 | | DC Hub dchub.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | Deed deed.page | Verified no auth | – | | yes | not read | 2026-11-04 | | DeepWiki deepwiki.com | Verified no auth | – | | – | not read | 2026-11-04 | | Designesy designesy.org | Verified no auth | – | | – | not read | 2026-11-04 | | Devin devin.ai | Verified no auth | – | 67 C | yes | not read | 2026-11-04 | | Digestseo digestseo.com | Verified no auth | – | | – | not read | 2026-11-04 | | Dm dm.de | Verified no auth | – | 51 C | – | no | 2026-11-04 | | DMCA.com dmca.com | Verified no auth | – | | – | no | 2026-11-04 | | Draw draw.io | Verified no auth | – | 13 F | – | not read | 2026-11-04 | | Dreamwork dreamworkhq.com | Verified no auth | – | | – | not read | 2026-11-04 | | DropTheHassle dropthehassle.com | Verified no auth | – | | – | not read | 2026-11-04 | | Dueback dueback.co | Verified no auth | – | | – | not read | 2026-11-04 | | Easy itseasy.co | Verified no auth | – | 87 A | – | no | 2026-11-04 | | EasyGerber easygerber.com | Verified no auth | – | | – | not read | 2026-11-04 | | Editalmd editalmd.com | Verified no auth | – | | yes | not read | 2026-11-04 | | emem emem.dev | Verified no auth | – | 85 B | – | not read | 2026-11-04 | | Epinu epinu.ai | Verified no auth | – | | – | not read | 2026-11-04 | | esimgomobile esimgomobile.com | Verified no auth | – | | – | not read | 2026-11-04 | | Etherscan etherscan.io | Verified no auth | – | | – | no | 2026-11-04 | | EveryCalc everycalc.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | Exa exa.ai | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Example4 example4.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Faxette faxette.com | Verified no auth | – | | – | not read | 2026-11-04 | | Faxforagents faxforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | Ferryhopper ferryhopper.com | Verified no auth | – | | – | not read | 2026-11-04 | | Fiber AI fiber.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | | Find-A-Domain findadomain.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Findabis findabis.com | Verified no auth | – | | – | not read | 2026-11-04 | | FlickDirect flickdirect.com | Verified no auth | – | | – | not read | 2026-11-04 | | Flightpowers flightpowers.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Footgun getfootgun.com | Verified no auth | – | | – | not read | 2026-11-04 | | Forter forter.com | Verified no auth | – | 92 A | yes | no | 2026-11-04 | | Fuentio fuentio.com | Verified no auth | – | | – | not read | 2026-11-04 | | Fund Momentum fundmomentum.vc | Verified no auth | – | | yes | not read | 2026-11-04 | | FusionAuth fusionauth.io | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Gaipagents gaipagents.com | Verified no auth | – | | yes | not read | 2026-11-04 | | GameAnalytics gameanalytics.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | GenMagic genmagic.co | Verified no auth | – | | yes | not read | 2026-11-04 | | Getappniche getappniche.com | Verified no auth | – | | – | not read | 2026-11-04 | | GetMattered getmattered.com | Verified no auth | – | | – | not read | 2026-11-04 | | GitMCP gitmcp.io | Verified no auth | – | 37 D | – | not read | 2026-11-04 | | Goldsky goldsky.com | Verified no auth | – | 81 B | – | not read | 2026-11-04 | | Gomdori gomdori.app | Verified no auth | – | | – | not read | 2026-11-04 | | Google google.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | Google Cloud googleapis.com | Verified no auth | – | | – | no | 2026-11-04 | | GoSQLX gosqlx.dev | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/none/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "No authentication, page 2 | Agent MCP Directory" description: "263 MCP endpoints with no authentication, as seen by a read-only connector on 4 November 2026. Page 2 of 3. Each entry shows what the challenge said." canonical: https://agentmcpdirectory.com/directory/auth/none/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # No authentication, page 2 | Agent MCP Directory > 263 MCP endpoints with no authentication, as seen by a read-only connector on 4 November 2026. Page 2 of 3. Each entry shows what the challenge said. Source: https://agentmcpdirectory.com/directory/auth/none/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: No authentication, page 2 263 endpoints use no authentication: 263 listed tools to a client with no credentials and 0 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 101 to 200, from Greca House to Rta. The server listed its tools to a client that sent no credentials. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Greca House grecahouse.com | Verified no auth | – | | – | not read | 2026-11-04 | | GuruHotel guruhotel.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Hands for Agents handsforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | HasData hasdata.com | Verified no auth | – | | – | not read | 2026-11-04 | | Helena helena.bio | Verified no auth | – | | – | not read | 2026-11-04 | | HemmaBo hemmabo.com | Verified no auth | – | | – | not read | 2026-11-04 | | Hexclave hexclave.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 85 B | yes | no | 2026-11-04 | | Hive Intelligence hiveintelligence.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | Hookpulse hookpulse.net | Verified no auth | – | | yes | not read | 2026-11-04 | | hotglue hotglue.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Hugging Face huggingface.co | Verified no auth | huggingface_hub | 82 B | – | no | 2026-11-04 | | HVTracker hvtracker.net | Verified no auth | – | | – | not read | 2026-11-04 | | iDevice idevice.com | Verified no auth | – | | – | not read | 2026-11-04 | | iHatePosting ihateposting.com | Verified no auth | – | | – | not read | 2026-11-04 | | ImageKit imagekit.io | Verified no auth | – | 63 C | – | not read | 2026-11-04 | | Inamprotocol inamprotocol.org | Verified no auth | – | | – | not read | 2026-11-04 | | IndustryLens industry-lens.com | Verified no auth | – | | – | not read | 2026-11-04 | | Invokary invokary.com | Verified no auth | – | | – | not read | 2026-11-04 | | Isonavigator isonavigator.io | Verified no auth | – | | – | not read | 2026-11-04 | | Isto Intents istointents.com | Verified no auth | – | | – | not read | 2026-11-04 | | Javadocs.dev javadocs.dev | Verified no auth | – | 47 D | yes | not read | 2026-11-04 | | JobsPipe jobspipe.dev | Verified no auth | – | 96 A+ | yes | not read | 2026-11-04 | | JustClaw-It justclaw.it.com | Verified no auth | – | | – | not read | 2026-11-04 | | Kaiv kaiv.ai | Verified no auth | – | | – | not read | 2026-11-04 | | kari kari.com | Verified no auth | – | | – | not read | 2026-11-04 | | Keenable keenable.ai | Verified no auth | – | 68 C | yes | not read | 2026-11-04 | | Kodza kodza.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Kraken kraken.com | Verified no auth | – | 82 B | yes | no | 2026-11-04 | | Kujolang.ai kujolang.ai | Verified no auth | – | 55 C | – | not read | 2026-11-04 | | Lambdatest lambdatest.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Lazaretto lazaretto.dev | Verified no auth | – | | yes | not read | 2026-11-04 | | Lezzoo lezzoo.com | Verified no auth | – | 69 C | – | no | 2026-11-04 | | Liquilens liquilens.in | Verified no auth | – | 72 B | – | not read | 2026-11-04 | | LiveScore MCP livescoremcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Lodestarindex lodestarindex.com | Verified no auth | – | | – | not read | 2026-11-04 | | Ludo AI ludo.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Maatsii maatsii.com | Verified no auth | – | | – | not read | 2026-11-04 | | Macfax macfax.com | Verified no auth | – | | – | not read | 2026-11-04 | | Magic Hour magichour.ai | Verified no auth | – | 89 A | yes | no | 2026-11-04 | | Mailbuttons mailbuttons.com | Verified no auth | – | | – | not read | 2026-11-04 | | Mailrith mailrith.com | Verified no auth | – | 97 A+ | yes | not read | 2026-11-04 | | Manifold manifold.markets | Verified no auth | – | | – | not read | 2026-11-04 | | MAQAMI maqami.co | Verified no auth | – | | – | not read | 2026-11-04 | | Market Eyes Live marketeyeslive.com | Verified no auth | – | | – | not read | 2026-11-04 | | Mediawork mediawork.io | Verified no auth | – | | – | not read | 2026-11-04 | | Memxus memxus.com | Verified no auth | – | | – | not read | 2026-11-04 | | Microsoft microsoft.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Microsoft Learn learn.microsoft.com | Verified no auth | azure-cli | 24 F | – | not read | 2026-11-04 | | Mintlify mintlify.com | Verified no auth | mint | 74 B | – | no | 2026-11-04 | | Mirabelloconsultancy mirabelloconsultancy.com | Verified no auth | – | | – | not read | 2026-11-04 | | MnogoReels mnogo-reels.ru | Verified no auth | – | | – | not read | 2026-11-04 | | MotionSpec motionspec.dev | Verified no auth | – | | – | not read | 2026-11-04 | | NegativeEV negativeev.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Neuronto neuronto.com | Verified no auth | – | | yes | not read | 2026-11-04 | | NewsCatcher newscatcherapi.com | Verified no auth | – | 63 C | – | no | 2026-11-04 | | Noonlaunch noonlaunch.com | Verified no auth | – | 61 C | yes | not read | 2026-11-04 | | Notaiochianese notaiochianese.it | Verified no auth | – | | – | not read | 2026-11-04 | | Nslookup nslookup.io | Verified no auth | – | | – | not read | 2026-11-04 | | NUM itsnum.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Obolusfinanz obolusfinanz.de | Verified no auth | – | | – | not read | 2026-11-04 | | Offline Protocol offlineprotocol.com | Verified no auth | – | | – | not read | 2026-11-04 | | Okfindex okfindex.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Okibi okibi.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | | OpenAccountants openaccountants.com | Verified no auth | – | 64 C | – | not read | 2026-11-04 | | OpenZeppelin openzeppelin.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Optionsahoy optionsahoy.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Ora ora.ai | Verified no auth | – | 95 A+ | yes | yes | 2026-11-04 | | Pageaudit pageaudit.online | Verified no auth | – | | yes | not read | 2026-11-04 | | PakBus pakbus.app | Verified no auth | – | | – | not read | 2026-11-04 | | PatchDesign.AI patchdesign.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Paytm paytm.com | Verified no auth | – | 52 C | – | no | 2026-11-04 | | Peek.com peek.com | Verified no auth | – | 39 D | – | not read | 2026-11-04 | | PensionHunter pensionhunter.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Pexafy pexafy.com | Verified no auth | – | | – | not read | 2026-11-04 | | PicSee picsee.io | Verified no auth | – | | – | not read | 2026-11-04 | | Pontofato pontofato.com | Verified no auth | – | | yes | not read | 2026-11-04 | | PostData postdata.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | Postel postel.app | Verified no auth | – | | – | not read | 2026-11-04 | | Powmcp powmcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Predictionmarketspicks predictionmarketspicks.com | Verified no auth | – | | – | not read | 2026-11-04 | | PreShiftIQ preshiftiq.com | Verified no auth | – | | – | not read | 2026-11-04 | | Primitive primitive.dev | Verified no auth | – | 96 A+ | yes | yes | 2026-11-04 | | Probativegrowth probativegrowth.com | Verified no auth | – | | – | not read | 2026-11-04 | | PropelAuth propelauth.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Ptpge ptpge.org | Verified no auth | – | | – | not read | 2026-11-04 | | Pulse thepulse.markets | Verified no auth | – | | – | not read | 2026-11-04 | | Pushary pushary.com | Verified no auth | – | 79 B | – | not read | 2026-11-04 | | Radar Cnpj radar-cnpj.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Rapier rapier.website | Verified no auth | – | | – | not read | 2026-11-04 | | Redpanda redpanda.com | Verified no auth | – | 68 C | – | no | 2026-11-04 | | RegEvidenceHub regevidencehub.com | Verified no auth | – | | – | not read | 2026-11-04 | | Reka reka.ai | Verified no auth | – | 77 B | – | no | 2026-11-04 | | Relvato relvato.com | Verified no auth | – | | – | not read | 2026-11-04 | | Remote MCP remote-mcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | ReplyOnTheFly replyonthefly.com | Verified no auth | – | | – | not read | 2026-11-04 | | ReputeMap reputemap.com | Verified no auth | – | | – | not read | 2026-11-04 | | Resemble AI resemble.ai | Verified no auth | – | 74 B | – | not read | 2026-11-04 | | RestaurantDoctorAI restaurantdoctorai.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Rokha rokha.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Rta rta.lat | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/none/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "No authentication, page 3 | Agent MCP Directory" description: "263 MCP endpoints with no authentication, as seen by a read-only connector on 4 November 2026. Page 3 of 3. Each entry shows what the challenge said." canonical: https://agentmcpdirectory.com/directory/auth/none/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # No authentication, page 3 | Agent MCP Directory > 263 MCP endpoints with no authentication, as seen by a read-only connector on 4 November 2026. Page 3 of 3. Each entry shows what the challenge said. Source: https://agentmcpdirectory.com/directory/auth/none/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: No authentication, page 3 263 endpoints use no authentication: 263 listed tools to a client with no credentials and 0 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 201 to 263, from SanctionsKit to Ziptax. The server listed its tools to a client that sent no credentials. ## Rows 201 to 263 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | SanctionsKit sanctionskit.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Scalix Cloud scalix.world | Verified no auth | – | | – | not read | 2026-11-04 | | Scento scento.com | Verified no auth | – | 82 B | – | not read | 2026-11-04 | | Scholar Sidekick scholar-sidekick.com | Verified no auth | – | 98 A+ | yes | not read | 2026-11-04 | | ScrapingBee scrapingbee.com | Verified no auth | – | 61 C | – | not read | 2026-11-04 | | Seam seam.co | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 53 C | – | no | 2026-11-04 | | Search Fragments searchfragments.com | Verified no auth | – | | – | not read | 2026-11-04 | | Seller Profit Doctor sellerprofitdoctor.com | Verified no auth | – | | – | not read | 2026-11-04 | | SEOmatic seomatic.ai | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | SerpApi serpapi.com | Verified no auth | – | 59 C | – | not read | 2026-11-04 | | ShipStatic shipstatic.com | Verified no auth | – | | – | not read | 2026-11-04 | | Shortimize shortimize.com | Verified no auth | – | | – | not read | 2026-11-04 | | Siemens siemens.com | Verified no auth | – | 56 C | – | no | 2026-11-04 | | Sitepulsar sitepulsar.ai | Verified no auth | – | | yes | not read | 2026-11-04 | | SkyAccess skyaccess.com | Verified no auth | – | | – | not read | 2026-11-04 | | SlideForge slideforge.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Soracom soracom.com | Verified no auth | – | | – | not read | 2026-11-04 | | Speakeroo speakeroo.app | Verified no auth | – | 73 B | – | not read | 2026-11-04 | | Spicrawl spicrawl.com | Verified no auth | – | | – | not read | 2026-11-04 | | SRIFT srift.app | Verified no auth | – | | yes | not read | 2026-11-04 | | Steellantern steellantern.com | Verified no auth | – | | – | not read | 2026-11-04 | | Studocu studocu.com | Verified no auth | – | 40 D | – | no | 2026-11-04 | | SubwayInfo NYC subwayinfo.nyc | Verified no auth | – | | yes | not read | 2026-11-04 | | Sugra sugra.ai | Verified no auth | – | 49 C | – | not read | 2026-11-04 | | SuperAnnotate superannotate.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 54 C | – | no | 2026-11-04 | | SurfacedBy AI surfacedby.com | Verified no auth | – | | – | not read | 2026-11-04 | | Svelte svelte.dev | Verified no auth | – | 58 C | – | not read | 2026-11-04 | | TableJourney tablejourney.com | Verified no auth | – | | yes | not read | 2026-11-04 | | TakeMeUp.cv takemeup.cv | Verified no auth | – | | – | not read | 2026-11-04 | | TapTax taptax.co.uk | Verified no auth | – | | – | not read | 2026-11-04 | | Techfabric techfabric.com | Verified no auth | – | | – | not read | 2026-11-04 | | Telnyx telnyx.com | Verified no auth | – | 99 A+ | yes | yes | 2026-11-04 | | TempGuru tempguru.co | Verified no auth | – | | – | not read | 2026-11-04 | | Terminal Tax terminal.tax | Verified no auth | – | | – | not read | 2026-11-04 | | The White Report thewhitereport.com | Verified no auth | – | | – | not read | 2026-11-04 | | There's An AI For That theresanaiforthat.com | Verified no auth | – | 9 F | – | not read | 2026-11-04 | | Tomiseregi tomiseregi.si | Verified no auth | – | | – | not read | 2026-11-04 | | TracePass tracepass.eu | Verified no auth | – | | yes | not read | 2026-11-04 | | trivago trivago.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | Turbo Notify turbonotify.com | Verified no auth | – | | – | not read | 2026-11-04 | | TweetSave tweetsave.org | Verified no auth | – | | – | not read | 2026-11-04 | | Twilio twilio.com | Verified no auth | twilio-cli | 85 B | – | no | 2026-11-04 | | Upstash upstash.com | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Usercentrics usercentrics.eu | Verified no auth | – | | – | yes | 2026-11-04 | | Vaaya vaaya.ai | Verified no auth | – | 90 A | yes | not read | 2026-11-04 | | VibeMarketing vibemarketing.ninja | Verified no auth | – | | – | not read | 2026-11-04 | | Viridisconservation viridisconservation.com | Verified no auth | – | | – | not read | 2026-11-04 | | VISEON viseon.io | Verified no auth | – | | – | not read | 2026-11-04 | | Vybenetwork vybenetwork.com | Verified no auth | – | | – | not read | 2026-11-04 | | Web3Juice web3juice.com | Verified no auth | – | | – | not read | 2026-11-04 | | WebinarIgnition webinarignition.com | Verified no auth | – | | – | not read | 2026-11-04 | | WebZum webzum.com | Verified no auth | – | | – | not read | 2026-11-04 | | WITAN Markets witan.markets | Verified no auth | – | | yes | not read | 2026-11-04 | | Wolfram wolfram.com | Verified no auth | – | | – | no | 2026-11-04 | | WRDO wrdo.co.za | Verified no auth | – | 48 C | – | not read | 2026-11-04 | | Xenition xenition.com | Verified no auth | – | | – | not read | 2026-11-04 | | Xquik xquik.com | Verified no auth | – | 92 A | yes | not read | 2026-11-04 | | YouSpot youspot.com | Verified no auth | – | 98 A+ | yes | yes | 2026-11-04 | | ZeroEval zeroeval.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 65 C | – | no | 2026-11-04 | | Zinc zinc.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | | Zip-Codes.com zip-codes.com | Verified no auth | – | | – | not read | 2026-11-04 | | Zip1 zip1.io | Verified no auth | – | | – | not read | 2026-11-04 | | Ziptax zip.tax | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/none/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP servers: OAuth without client registration | Agent MCP Directory" description: "16 MCP endpoints with OAuth without client registration, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said." canonical: https://agentmcpdirectory.com/directory/auth/oauth site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP servers: OAuth without client registration | Agent MCP Directory > 16 MCP endpoints with OAuth without client registration, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said. Source: https://agentmcpdirectory.com/directory/auth/oauth Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: OAuth without client registration 16 endpoints use OAuth without client registration: 0 listed tools to a client with no credentials and 16 answered with a sign-in challenge (tools not seen, not counted). Rows run from Andi to Zoom. The server publishes OAuth metadata but no registration endpoint, so a client must be registered by hand or identified by a client ID metadata document. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Andi andiai.com | Sign-in required OAuth; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Bigdata.com bigdata.com | Sign-in required OAuth; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | Box box.com | Sign-in required OAuth; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Cloudglue cloudglue.dev | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | ConfigCat configcat.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 51 C | – | no | 2026-11-04 | | GitHub github.com | Sign-in required OAuth; tools not seen, not counted | – | 65 C | yes | no | 2026-11-04 | | Githubcopilot githubcopilot.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | HubSpot hubspot.com | Sign-in required OAuth; tools not seen, not counted | @hubspot/cli | 72 B | – | no | 2026-11-04 | | Inttegro inttegro.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Microsoft 365 cloud.microsoft | Sign-in required OAuth; tools not seen, not counted | – | | – | no | 2026-11-04 | | Pantheon pantheon.io | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Render render.com | Sign-in required OAuth; tools not seen, not counted | – | 82 B | yes | yes | 2026-11-04 | | Sherweb sherweb.com | Sign-in required OAuth; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | Slack slack.com | Sign-in required OAuth; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Uptime.com :) uptime.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 59 C | – | no | 2026-11-04 | | Zoom zoom.us | Sign-in required OAuth; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/oauth/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP servers: OAuth with client registration | Agent MCP Directory" description: "517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said." canonical: https://agentmcpdirectory.com/directory/auth/oauth-dcr site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP servers: OAuth with client registration | Agent MCP Directory > 517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said. Source: https://agentmcpdirectory.com/directory/auth/oauth-dcr Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: OAuth with client registration 517 endpoints use OAuth with client registration: 0 listed tools to a client with no credentials and 517 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 1 to 100, from 0xArchive to Conveo. The server publishes OAuth metadata and a registration endpoint. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 0xArchive 0xarchive.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 94 A | yes | not read | 2026-11-04 | | 3Dsellers 3dsellers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Aaly aaly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Account Executive Jobs accountexecutivejobs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Adkit adkit.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | Adlicio tryadlicio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | yes | not read | 2026-11-04 | | Ads Uploader adsuploader.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AgentData agentdata.run | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Agilitycms agilitycms.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ahrefs ahrefs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | AI Mail MCP aimailmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | aictrl aictrl.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Airbyte airbyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Airport Lounge List airportloungelist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Airtable airtable.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Airweave airweave.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 78 B | – | no | 2026-11-04 | | Akiflow akiflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Alai getalai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Alchemy alchemy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | AlfaNest alfanestlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AltoRank altorank.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Amplify amplify.is | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Amplitude amplitude.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | yes | no | 2026-11-04 | | Anima animaapp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | AnomalyArmor anomalyarmor.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | yes | no | 2026-11-04 | | Ansvar ansvar.eu | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Antwork antwork.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | yes | not read | 2026-11-04 | | Any.do any.do | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | yes | no | 2026-11-04 | | Apify apify.com | Sign-in required OAuth DCR; tools not seen, not counted | apify-cli | 96 A+ | yes | no | 2026-11-04 | | APIVerve apiverve.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Apollo.io apollo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Appllama appllama.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 44 D | – | not read | 2026-11-04 | | AppmanAi appmanai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AppsFlyer appsflyer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Apricot apricot.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Arcmira arcmira.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Arkm arkm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Arrumou arrumou.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Artie artie.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Asana asana.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | ASO Atlas asoatlas.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AssemblyAI assemblyai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | yes | no | 2026-11-04 | | Atlassian atlassian.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Attio attio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Audioscrape audioscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Autosana autosana.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Avalara avalara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | not read | 2026-11-04 | | aVenture aventure.vc | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | not read | 2026-11-04 | | Avo avo.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Axiom axiom.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | Basecamp basecamp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Basedash basedash.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Baserow baserow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Beancount.io beancount.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | beehiiv beehiiv.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | BeliefState beliefstate.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Bird bird.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | no | 2026-11-04 | | Bitly bitly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Bitrise bitrise.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | BlindPay blindpay.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | BlogSEO blogseo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | brainattic brainattic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | briq briq.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Browserless browserless.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | yes | 2026-11-04 | | Browserstack browserstack.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Bubble bubble.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 40 D | – | no | 2026-11-04 | | Bugasura bugasura.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | not read | 2026-11-04 | | Buildkite buildkite.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | BulkPublish bulkpublish.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | Calendly calendly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | call4me call4.me | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Canva canva.com | Sign-in required OAuth DCR; tools not seen, not counted | @canva/cli | 42 D | – | no | 2026-11-04 | | Capacities capacities.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Carbon getcarbon.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Carrick carrick.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Causely causely.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Celigo celigo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | not read | 2026-11-04 | | CertScore.ai certscore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Charming charm.ing | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | yes | not read | 2026-11-04 | | Chatfuel chatfuel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | no | 2026-11-04 | | Chatway chatway.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Checkout.com checkout.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Chili Piper chilipiper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | Circleback circleback.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | CircleCI circleci.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | yes | 2026-11-04 | | Clean Notes cleannotes.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Clera getclera.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | ClickUp clickup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Close close.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Cloudchipr cloudchipr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Cloudinary cloudinary.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Cogram cogram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | CoinMarketCap coinmarketcap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | COLA Cloud colacloud.us | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Common Paper commonpaper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | Confident AI confident-ai.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 90 A | – | no | 2026-11-04 | | ConnectMachine connectmachine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Connie connie.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Contentful contentful.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | contentful-cli | 74 B | – | no | 2026-11-04 | | Conveo conveo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/oauth-dcr/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "OAuth with client registration, page 2 | Agent MCP Directory" description: "517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 2 of 6." canonical: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # OAuth with client registration, page 2 | Agent MCP Directory > 517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 2 of 6. Source: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: OAuth with client registration, page 2 517 endpoints use OAuth with client registration: 0 listed tools to a client with no credentials and 517 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 101 to 200, from CookieYes to HypAware. The server publishes OAuth metadata and a registration endpoint. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | CookieYes cookieyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | CoreNexis API corenexis.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | COROS coros.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | | Corsair corsair.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Cortex cortex.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Costory costory.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Coval coval.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 65 C | – | no | 2026-11-04 | | Cpln cpln.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Craft craft.do | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Crakseo crakseo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Cronitor cronitor.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | cubic cubic.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | CustomDomain™ customdomain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | cyon cyon.ch | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Cypress Cloud cypress.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Dabloons dabloons.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dart dartai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | yes | 2026-11-04 | | Datadog datadoghq.com | Sign-in required OAuth DCR; tools not seen, not counted | @datadog/datadog-ci | 69 C | – | no | 2026-11-04 | | DeepSource deepsource.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Depot depot.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Desktopcommander desktopcommander.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DevCycle devcycle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Dialer getdialer.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DialMCP dialmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Didit One didit.me | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | – | no | 2026-11-04 | | DigitalOcean digitalocean.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 74 B | – | no | 2026-11-04 | | Divblox divblox.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DocNexus docnexus.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DocSpring docspring.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dodo Payments dodopayments.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | not read | 2026-11-04 | | Draftbit draftbit.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Dragoneye dragoneye.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | DSers dsers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | EAN-Search.org ean-search.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Easyship easyship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Edgaze edgaze.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Egnyte egnyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | ElevenFlo elevenflo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ElevenLabs elevenlabs.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Elfsight AI elfsight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Embrace embrace.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 38 D | – | no | 2026-11-04 | | EmpirioLabs AI empiriolabs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Encord encord.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 69 C | – | no | 2026-11-04 | | Eodly eodly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | not read | 2026-11-04 | | Epidemic Sound epidemicsound.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | eResource Scheduler eresourcescheduler.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Evermuse evermuse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Explorium explorium.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Expo expo.dev | Sign-in required OAuth DCR; tools not seen, not counted | eas-cli | 66 C | – | no | 2026-11-04 | | Extend extend.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | FairValid fairvalid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fastero fastero.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fathom fathom.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | Figma figma.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | FinancialFilings financialfilings.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fireflies.ai fireflies.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Firmafakta firmafakta.se | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flagsmith flagsmith.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 47 D | – | no | 2026-11-04 | | FlightQueue flightqueue.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | FlightSeatMap flightseatmap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Floot floot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | FlowLeap flowleap.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flowra flowra.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fly fly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | no | 2026-11-04 | | FlyBest flybest.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Follore follore.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Formasty formasty.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | Frase frase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 89 A | yes | no | 2026-11-04 | | Freestyle freestyle.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | yes | no | 2026-11-04 | | Frihet frihet.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | FullEnrich fullenrich.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | not read | 2026-11-04 | | fynk fynk.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | | Gamedev gamedev.pl | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Gamma gamma.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | GitBook gitbook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 86 A | – | no | 2026-11-04 | | GitLab gitlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | GlanceAI glance.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Glassflow glassflow.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Glif glif.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | yes | no | 2026-11-04 | | Globalping globalping.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | GoCardless gocardless.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Grafana grafana.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Granola granola.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Graphcms graphcms.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Graphify graphify.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | GrowthBook growthbook.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | Gryz gryz.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Guru getguru.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | Harness harness.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 75 B | – | no | 2026-11-04 | | Hcti hcti.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | HelixDB helix-db.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 82 B | yes | no | 2026-11-04 | | Hermoso hermoso.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Heroku heroku.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | heroku | 73 B | – | no | 2026-11-04 | | Hitsteps hitsteps.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Honeycomb honeycomb.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | Hostinger hostinger.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | yes | 2026-11-04 | | Hubstaff hubstaff.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Huddo huddo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Hydrant hydrant.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | HypAware hypaware.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "OAuth with client registration, page 3 | Agent MCP Directory" description: "517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 3 of 6." canonical: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # OAuth with client registration, page 3 | Agent MCP Directory > 517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 3 of 6. Source: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: OAuth with client registration, page 3 517 endpoints use OAuth with client registration: 0 listed tools to a client with no credentials and 517 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 201 to 300, from HYPD AI to ONES. ## Rows 201 to 300 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | HYPD AI hypd.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | Hyperresearch hyperresearch.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | not read | 2026-11-04 | | Hypotize hypotize.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Icons8 icons8.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | IFTTT ifttt.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | imzala.net imzala.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | incident.io incident.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 64 C | – | no | 2026-11-04 | | Indeed indeed.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 25 F | – | no | 2026-11-04 | | Infobip infobip.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | InsForge insforge.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | – | no | 2026-11-04 | | Instant instantdb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Intercom intercom.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | Interfere interfere.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Invideo invideo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 54 C | – | not read | 2026-11-04 | | ISMS Copilot ismscopilot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | yes | not read | 2026-11-04 | | Jam.dev jam.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | JANCTION janction.jp | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Jitsu jitsu.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | no | 2026-11-04 | | Jotform jotform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | JumpCloud jumpcloud.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | JustCall justcall.host | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kajabi kajabi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | no | 2026-11-04 | | Kema kema-studio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kiln kiln3d.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kin kinlab.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kinsta® kinsta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Komodor komodor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Kong konghq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Kragos kragos.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lanesurf lanesurf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | yes | no | 2026-11-04 | | Layrcake layrcake.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lazybird lazybird.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Leadbase leadbase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Leadpages leadpages.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | yes | no | 2026-11-04 | | Leash lea.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Letterly letterly.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LFG lfg.gm | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Limrun limrun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | Linear linear.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Lingo.dev lingo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | Listenetic listenetic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LiveCRM livecrm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LLM Pulse llmpulse.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | | Local MCP local-mcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Localcmd localcmd.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Locus paywithlocus.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | yes | no | 2026-11-04 | | LogRocket logrocket.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Longbridge longbridge.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | not read | 2026-11-04 | | Lucid lucid.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lumman lumman.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lusha lusha.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Luw.ai luw.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | mabl mabl.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Mailkite mailkite.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Make make.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Manufact manufact.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | yes | no | 2026-11-04 | | Mapbox mapbox.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | MCP Telegram mcp-telegram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | MCPEmails mcpemails.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | mcprush.com mcprush.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Measuremy measuremy.site | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Medplum medplum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 43 D | – | no | 2026-11-04 | | Medusa medusajs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Mellow Hub mellow.world | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mem mem.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Memocore memocore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mercado Pago mercadopago.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Minds getminds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Minicor minicor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | MiningBridge miningbridge.in | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Miro miro.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Mnemoverse mnemoverse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mobbin mobbin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | not read | 2026-11-04 | | Momentic momentic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | monday monday.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | yes | 2026-11-04 | | MorningStar morningstar.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Mural mural.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Mux mux.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | mypromind mypromind.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Nanonets nanonets.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Neon neon.com | Sign-in required OAuth DCR; tools not seen, not counted | neonctl | 88 A | yes | no | 2026-11-04 | | Neon neon.tech | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | Netlify netlify.com | Sign-in required OAuth DCR; tools not seen, not counted | netlify-cli | 92 A | yes | no | 2026-11-04 | | New Relic newrelic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | ngrok ngrok.com | Sign-in required OAuth DCR; tools not seen, not counted | ngrok | 90 A | yes | no | 2026-11-04 | | Nimble nimble.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Nitrosend nitrosend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | | Nomas nomas.fyi | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Notion notion.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | – | no | 2026-11-04 | | Notion notion.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Novadata novadata.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Noveum noveum.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | not read | 2026-11-04 | | NVIDIA nvidia.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Oakallow oakallow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Octagon octagonai.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | OctoPerf octoperf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | Omnara omnara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | Omnidim omnidim.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | yes | not read | 2026-11-04 | | OneContext onecontext.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ONES ones.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "OAuth with client registration, page 4 | Agent MCP Directory" description: "517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 4 of 6." canonical: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/4 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # OAuth with client registration, page 4 | Agent MCP Directory > 517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 4 of 6. Source: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/4 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: OAuth with client registration, page 4 517 endpoints use OAuth with client registration: 0 listed tools to a client with no credentials and 517 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 301 to 400, from Onlook to Sequencer. The server publishes OAuth metadata and a registration endpoint. ## Rows 301 to 400 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Onlook onlook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Openlayer openlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | OpenWork openworklabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | OpsLevel opslevel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | OpusClip opus.pro | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | Orangescrum orangescrum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | OrgGen AI orggen.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Otter.ai otter.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Outlit outlit.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | no | 2026-11-04 | | Outset outset.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | OwlCAD owlcad.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Oximy oximy.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Paddle paddle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Padlet padlet.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Pageree pageree.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PaidSync.ai paidsync.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Palisade palisade.email | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Pally pally.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | PandaDoc pandadoc.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Parad1gm parad1gm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Parallel parallel.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Parse.ly parsely.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Pathrule pathrule.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PAVE pavecfi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PayPal paypal.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Perspective AI getperspective.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | not read | 2026-11-04 | | Picsart picsart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Pipeboard pipeboard.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | Pith pith.day | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Pixelesq pixelesq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | not read | 2026-11-04 | | PixelFlow pixelflow.so | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Plaid plaid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Plori plori.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | not read | 2026-11-04 | | POEditor poeditor.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Polar Signals polarsignals.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Poly poly.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Porkbun porkbun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | – | no | 2026-11-04 | | Port IO port.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | Posteverywhere posteverywhere.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | – | not read | 2026-11-04 | | PostHog posthog.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Postman postman.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Posy posy.page | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Precip precip.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | PredictLeads predictleads.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | Prembly prembly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Prisma prisma.io | Sign-in required OAuth DCR; tools not seen, not counted | prisma | 82 B | yes | no | 2026-11-04 | | Process Street process.st | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | ProLevelMax prolevelmax.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Prominara prominara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | Prompeteer prompeteer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Publora publora.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Qualityclouds qualityclouds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Qualityclouds qualityclouds.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Quicknode quicknode.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Quillm quillm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Quorum AI quorum.dog | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Railway railway.com | Sign-in required OAuth DCR; tools not seen, not counted | @railway/cli | 89 A | yes | not read | 2026-11-04 | | Ramp ramp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Rampify rampify.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rankability rankability.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | Raygun raygun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Read AI read.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | Realeyes realeyes.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RegAI regai.tw | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ResumeQuick resumequick.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rivet rivet.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Roboflow roboflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | RoboSystems robosystems.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RocketReach rocketreach.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | Rocketship deployrocketship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rootly rootly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Rulebase rulebase.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Runcaptain runcaptain.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 57 C | – | no | 2026-11-04 | | Runcomfy runcomfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Runpulse runpulse.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Rus.sh rus.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sadiqoon sadiqoon.uk | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Saifs saifs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Salvy salvy.com.br | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Sanity sanity.io | Sign-in required OAuth DCR; tools not seen, not counted | @sanity/cli | 72 B | – | no | 2026-11-04 | | Say It Again sayitagain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sazabi sazabi.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Scavio scavio.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scorecard scorecard.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scoutapm scoutapm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Screenforge screenforge.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ScreensDesign screensdesign.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | ScreenVerb screenverb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scripe scripe.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | SearchAPI searchapi.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | SearchConsole.ai searchconsole.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Searcherries searcherries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sellfy sellfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Semgrep semgrep.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Sendmux sendmux.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | – | not read | 2026-11-04 | | SendPulse sendpulse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | SentinelX sentinelx.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sentry sentry.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | Sentry sentry.io | Sign-in required OAuth DCR; tools not seen, not counted | @sentry/cli | 79 B | – | no | 2026-11-04 | | Sequencer sequencer.media | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/4/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "OAuth with client registration, page 5 | Agent MCP Directory" description: "517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 5 of 6." canonical: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/5 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # OAuth with client registration, page 5 | Agent MCP Directory > 517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 5 of 6. Source: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/5 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: OAuth with client registration, page 5 517 endpoints use OAuth with client registration: 0 listed tools to a client with no credentials and 517 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 401 to 500, from Serpstat to WarpBuild. The server publishes OAuth metadata and a registration endpoint. ## Rows 401 to 500 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Serpstat serpstat.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Server4Agent server4agent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ShapelessAI shapelessai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Shipbook shipbook.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shippo shippo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Short.io short.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shortcut shortcut.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | yes | no | 2026-11-04 | | ShortSync shortsync.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SimpleBackups simplebackups.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SimplePDF simplepdf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | yes | no | 2026-11-04 | | Simplescraper simplescraper.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Since.dev since.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sisense sisense.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Sitelemetry sitelemetry.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sixtyfour sixtyfour.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | SkillDB skilldb.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SKU.io sku.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Skydropx skydropx.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 41 D | – | no | 2026-11-04 | | Skyvern skyvern.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | no | 2026-11-04 | | SmartBear smartbear.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Social Growth Engineers socialgrowthengineers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sociality.io sociality.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | Socialync socialync.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sofya sofya.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Spacefast spacefast.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | not read | 2026-11-04 | | Spike spike.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | SpriteCook spritecook.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Square square.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 26 F | – | not read | 2026-11-04 | | Square squareup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Startup Ignition startupignition.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Statsig statsig.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Stillwind stillwind.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | StoriesIG storiesig.info | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Streamkap streamkap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Stripe stripe.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Structura structura.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Studio99 studio99.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Studiomeyer studiomeyer.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | yes | not read | 2026-11-04 | | Supabase supabase.com | Sign-in required OAuth DCR; tools not seen, not counted | supabase | 93 A | yes | no | 2026-11-04 | | superglue superglue.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Supernova.io supernova.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | SuprSend suprsend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Symbioza symbioza.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Synth AI usesynth.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Tallyfy tallyfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Tapcart tapcart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | Taplio taplio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Taskfolk taskfolk.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Tavus tavus.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Taxapp taxapp.nz | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Teamwork.com teamwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Tempo tempo.new | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Tenet Industries tenetindustries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | | Tesorio tesorio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | The Brains brains.ceo | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | The Bridge thebridge.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | The Context Company thecontext.company | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 58 C | – | no | 2026-11-04 | | ThoughtSpot thoughtspot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | ThousandEyes thousandeyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | tl;dv tldv.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | not read | 2026-11-04 | | Todoist todoist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Todoist todoist.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Traveler.md traveler.md | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | yes | not read | 2026-11-04 | | Treza trezalabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Truthifi truthifi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Turkishtechlab turkishtechlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Twelfth twelfth.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | yes | not read | 2026-11-04 | | Twelve Data twelvedata.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | txscribe txscribe.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Typeform typeform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Uizze uizze.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ulapcybo ulapcybo.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ultralayer ultralayer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Unblocked getunblocked.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Unlayer unlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Unlimitless unlimitless.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Unsiloed AI unsiloed.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Unstructured unstructured.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Upload-Post upload-post.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Upscrape upscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Upsolve AI upsolve.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | UptimeRobot uptimerobot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Upwork upwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | UX Pilot uxpilot.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | not read | 2026-11-04 | | UXKIN uxkin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Valkyrlabs valkyrlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vanta vanta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Veles getveles.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | Vercel vercel.com | Sign-in required OAuth DCR; tools not seen, not counted | vercel | 91 A | yes | no | 2026-11-04 | | Veridu veridu.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | VeriTeknik veriteknik.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Versive getversive.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | VibeSEO vibeseo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vidova vidova.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | Vike vike.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Visa visa.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | Vooban vooban.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vultr vultr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | Wall Marketing wall.marketing | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WarpBuild warpbuild.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/5/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "OAuth with client registration, page 6 | Agent MCP Directory" description: "517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 6 of 6." canonical: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/6 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # OAuth with client registration, page 6 | Agent MCP Directory > 517 MCP endpoints with OAuth with client registration, as seen by a read-only connector on 4 November 2026. Page 6 of 6. Source: https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/6 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: OAuth with client registration, page 6 517 endpoints use OAuth with client registration: 0 listed tools to a client with no credentials and 517 answered with a sign-in challenge (tools not seen, not counted). This page lists rows 501 to 517, from Watchgoose to Zomato. The server publishes OAuth metadata and a registration endpoint. ## Rows 501 to 517 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Watchgoose watchgoose.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | yes | not read | 2026-11-04 | | Webflow webflow.com | Sign-in required OAuth DCR; tools not seen, not counted | @webflow/webflow-cli | 78 B | – | not read | 2026-11-04 | | Webhound webhound.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | Whalesync whalesync.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Whimsical whimsical.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | | WhitePact whitepact.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Wix wix.com | Sign-in required OAuth DCR; tools not seen, not counted | @wix/cli | 64 C | – | no | 2026-11-04 | | WorkOS workos.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | WP Agent getwpagent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WPWriter wpwriter.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | XMemo xmemo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | not read | 2026-11-04 | | Zapier zapier.com | Sign-in required OAuth DCR; tools not seen, not counted | zapier-platform-cli | 84 B | – | no | 2026-11-04 | | Zenable zenable.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Zentrik zentrik.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | not read | 2026-11-04 | | zeroheight zeroheight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Zine zine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Zomato zomato.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 16 F | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/oauth-dcr/page/6/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP servers: Auth not determined | Agent MCP Directory" description: "2 MCP endpoints with an undetermined auth type, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said." canonical: https://agentmcpdirectory.com/directory/auth/unknown site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP servers: Auth not determined | Agent MCP Directory > 2 MCP endpoints with an undetermined auth type, as seen by a read-only connector on 4 November 2026. Each entry shows what the challenge said. Source: https://agentmcpdirectory.com/directory/auth/unknown Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth type: Auth not determined 2 endpoints use an undetermined auth type: 0 listed tools to a client with no credentials and 0 answered with a sign-in challenge (tools not seen, not counted). Rows run from Award Travel Finder to Storyblok. The connector could not tell what the endpoint wants, usually because it did not answer. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Award Travel Finder awardtravelfinder.com | No tools listed | – | | – | not read | 2026-11-04 | | Storyblok storyblok.com | No tools listed | – | 67 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auth/unknown/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Autodesk MCP server | Agent MCP Directory" description: "Autodesk has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/autodesk-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Autodesk MCP server | Agent MCP Directory > Autodesk has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/autodesk-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Autodesk: MCP server, CLI and agent surfaces Yes: Autodesk runs a public MCP server at api.aps.autodesk.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: get\_available\_products, search\_help\_content. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for autodesk.com is 36, grade D, read on 5 November 2026. ## Fact sheet | Company | Autodesk (registry title: Autodesk Product Help MCP) | | --- | --- | | Domain | autodesk.com | | Category | Real Estate & Construction (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 326 on the list of 4 November 2026 | | Ora score | 36, grade D; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for autodesk.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.aps.autodesk.com/knowledge/public/v1/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | autodesk-knowledge-public-v1-mcp-server 1.0.13 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,581 ms over 1 attempt | ### Tools listed 2 tools - get\_available\_products - search\_help\_content ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://api.aps.autodesk.com/knowledge/public/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2485 ms - 20:01:31Z https://api.aps.autodesk.com/knowledge/public/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2581 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.aps.autodesk.com/knowledge/public/v1/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Autodesk. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.autodesk.aps.api/product-help-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/autodesk-com/index.md) ## Sources - [Ora score page for autodesk.com](https://ora.ai/score/autodesk.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Autodesk was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.autodesk.aps.api%2Fproduct-help-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=autodesk), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Automattic MCP server | Agent MCP Directory" description: "Does Automattic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/automattic-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Automattic MCP server | Agent MCP Directory > Does Automattic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/automattic-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Automattic: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Automattic (automattic.com), so the connector had nothing to connect to. Ora's cached score for automattic.com is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Automattic (registry title: automattic.com) | | --- | --- | | Domain | automattic.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,216 on the list of 4 November 2026 | | Ora score | 53, grade C; Ora scanned the domain on 30 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for automattic.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Automattic. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for automattic.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Automattic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/automattic-com/index.md) ## Sources - [Ora score page for automattic.com](https://ora.ai/score/automattic.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 August 2026, read from GET /api/score) - [Where Automattic was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Automattic website](https://automattic.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Autosana MCP server | Agent MCP Directory" description: "Autosana: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/autosana-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Autosana MCP server | Agent MCP Directory > Autosana: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/autosana-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Autosana: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Autosana; the connector's guess at mcp.autosana.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Autosana (registry title: autosana.ai) | | --- | --- | | Domain | autosana.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for autosana.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.autosana.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 889 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:35Z https://mcp.autosana.ai/mcp sent initialize result auth-required (HTTP 401) 1287 ms - 20:02:09Z https://mcp.autosana.ai/mcp sent initialize result auth-required (HTTP 401) 889 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.autosana.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.autosana.ai | | Authorization server metadata | jwvmttqclexlhnhfxuyq.supabase.co | | Registration endpoint | https://jwvmttqclexlhnhfxuyq.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://mcp.autosana.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.autosana.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://jwvmttqclexlhnhfxuyq.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Autosana. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/autosana-ai/index.md) ## Sources - [Ora score page for autosana.ai](https://ora.ai/score/autosana.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Autosana was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Autosana website](https://autosana.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Auvik MCP server | Agent MCP Directory" description: "Does Auvik have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/auvik-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Auvik MCP server | Agent MCP Directory > Does Auvik have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/auvik-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auvik: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Auvik (auvik.com), so the connector had nothing to connect to. Ora's cached score for auvik.com is 54, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Auvik (registry title: auvik.com) | | --- | --- | | Domain | auvik.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 1,878 on the list of 4 November 2026 | | Ora score | 54, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for auvik.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Auvik. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for auvik.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Auvik. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/auvik-com/index.md) ## Sources - [Ora score page for auvik.com](https://ora.ai/score/auvik.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where Auvik was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Auvik website](https://auvik.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Avalara MCP server | Agent MCP Directory" description: "Avalara: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/avalara-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Avalara MCP server | Agent MCP Directory > Avalara: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/avalara-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Avalara: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Avalara at mcp.avalara.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Avalara (registry title: Avalara Tax Content) | | --- | --- | | Domain | avalara.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 57, grade C; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for avalara.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.avalara.com/bl | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,885 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:37Z https://mcp.avalara.com/bl sent initialize result auth-required (HTTP 401) 3091 ms - 20:02:11Z https://mcp.avalara.com/bl sent initialize result auth-required (HTTP 401) 2885 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.avalara.com/.well-known/oauth-protected-resource/bl" | | Protected resource metadata | mcp.avalara.com | | Authorization server metadata | identity.avalara.com | | Registration endpoint | https://identity.avalara.com/register/public | ### The sign-in route, step by step 1. Request `https://mcp.avalara.com/bl` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.avalara.com/.well-known/oauth-protected-resource/bl` to find the authorization server. 3. Register a client at the registration endpoint `https://identity.avalara.com/register/public` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Avalara. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.avalara/atc, com.avalara/avatax, com.avalara/bl and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/avalara-com/index.md) ## Sources - [Ora score page for avalara.com](https://ora.ai/score/avalara.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=avalara), read 4 November 2026 - [Avalara website](https://avalara.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "aVenture MCP server | Agent MCP Directory" description: "aVenture: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/aventure-vc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # aVenture MCP server | Agent MCP Directory > aVenture: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/aventure-vc Site: Agent MCP Directory Last reviewed: 2026-11-05 # aVenture: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for aVenture at mcp.aventure.vc answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | aVenture | | --- | --- | | Domain | aventure.vc | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 34, grade D; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for aventure.vc, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.aventure.vc/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,286 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:37Z https://mcp.aventure.vc/mcp sent initialize result auth-required (HTTP 401) 1899 ms - 20:02:10Z https://mcp.aventure.vc/mcp sent initialize result auth-required (HTTP 401) 1286 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.aventure.vc/.well-known/oauth-protected-resource/mcp", scope="openid profile email offline_access" | | Protected resource metadata | mcp.aventure.vc | | Authorization server metadata | clerk.aventure.vc | | Registration endpoint | https://clerk.aventure.vc/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.aventure.vc/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.aventure.vc/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.aventure.vc/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for aVenture. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aventure-vc/index.md) ## Sources - [Ora score page for aventure.vc](https://ora.ai/score/aventure.vc?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/score) - [Where aVenture was found](https://github.com/mcp/aventurevc/aventure-mcp), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Aviator MCP server | Agent MCP Directory" description: "Does Aviator have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aviator-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Aviator MCP server | Agent MCP Directory > Does Aviator have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/aviator-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Aviator: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Aviator (aviator.co), so the connector had nothing to connect to. Ora's cached score for aviator.co is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Aviator (registry title: aviator.co) | | --- | --- | | Domain | aviator.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 31 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for aviator.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Aviator. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for aviator.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Aviator. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aviator-co/index.md) ## Sources - [Ora score page for aviator.co](https://ora.ai/score/aviator.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 August 2026, read from GET /api/leaderboard) - [Where Aviator was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Aviator website](https://aviator.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Avo MCP server | Agent MCP Directory" description: "Avo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/avo-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Avo MCP server | Agent MCP Directory > Avo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/avo-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Avo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Avo; the connector's guess at mcp.avo.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Avo (registry title: avo.app) | | --- | --- | | Domain | avo.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 45, grade D; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for avo.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.avo.app/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 685 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:36Z https://mcp.avo.app/mcp sent initialize result auth-required (HTTP 401) 1114 ms - 20:02:09Z https://mcp.avo.app/mcp sent initialize result auth-required (HTTP 401) 685 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.avo.app/.well-known/oauth-protected-resource", scope="read write" | | Protected resource metadata | mcp.avo.app | | Authorization server metadata | api.avo.app | | Registration endpoint | https://api.avo.app/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.avo.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.avo.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.avo.app/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Avo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/avo-app/index.md) ## Sources - [Ora score page for avo.app](https://ora.ai/score/avo.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/leaderboard) - [Where Avo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Avo website](https://avo.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Award Travel Finder MCP server | Agent MCP Directory" description: "Award Travel Finder answered the MCP handshake and listed no tools, so it is not counted. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/awardtravelfinder-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Award Travel Finder MCP server | Agent MCP Directory > Award Travel Finder answered the MCP handshake and listed no tools, so it is not counted. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/awardtravelfinder-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Award Travel Finder: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Award Travel Finder at mcp.awardtravelfinder.com completed the handshake on 4 November 2026 but listed no tools, so there is nothing for an agent to call. The row stays so the result can be re-checked next edition. ## Fact sheet | Company | Award Travel Finder | | --- | --- | | Domain | awardtravelfinder.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | No tools listed | | Ora score | none: Ora returned no cached score for awardtravelfinder.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.awardtravelfinder.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | AwardTravelFinder 3.0.0 | | Capabilities | extensions, logging, prompts, resources, tools | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,688 ms over 1 attempt | | Result | tools/list: no response (HTTP 401) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:37Z https://mcp.awardtravelfinder.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result initialized-no-tools (HTTP 200) 1402 ms - 20:02:11Z https://mcp.awardtravelfinder.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result initialized-no-tools (HTTP 200) 1688 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.awardtravelfinder.com/mcp`. The connector could not tell what it wants: tools/list: no response (HTTP 401). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Award Travel Finder. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.awardtravelfinder/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/awardtravelfinder-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=awardtravelfinder), read 4 November 2026 - [Award Travel Finder website](https://awardtravelfinder.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Amazon Web Services MCP server | Agent MCP Directory" description: "Amazon Web Services has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/aws-amazon-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Amazon Web Services MCP server | Agent MCP Directory > Amazon Web Services has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/aws-amazon-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Amazon Web Services: MCP server, CLI and agent surfaces Yes: Amazon Web Services runs a public MCP server at knowledge-mcp.global.api.aws that listed 5 tools to a client with no credentials on 4 November 2026. Examples: aws\_\_\_read\_documentation, aws\_\_\_search\_documentation, aws\_\_\_list\_regions. It speaks streamable-http, protocol 2025-03-26. A CLI is on record: awscli on pypi. ## Fact sheet | Company | Amazon Web Services | | --- | --- | | Domain | aws.amazon.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 60, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for aws.amazon.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://knowledge-mcp.global.api.aws | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | AWSKnowledgeMCP 1.0.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 286 ms over 1 attempt | | Documentation | awslabs.github.io | ### Tools listed 5 tools - aws\_\_\_read\_documentation - aws\_\_\_search\_documentation - aws\_\_\_list\_regions - aws\_\_\_get\_regional\_availability - aws\_\_\_retrieve\_skill ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:36Z https://knowledge-mcp.global.api.aws sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 326 ms - 20:02:10Z https://knowledge-mcp.global.api.aws sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 286 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://knowledge-mcp.global.api.aws` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | awscli on pypi (page) | | --- | --- | | Exists | yes | | Latest version | 1.46.2 | | Last publish | 21 October 2026 | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/aws-amazon-com/index.md) ## Sources - [Amazon Web Services MCP documentation](https://awslabs.github.io/mcp/servers/aws-knowledge-mcp-server), read 4 November 2026 - [awscli on pypi](https://pypi.org/project/awscli/), read 4 November 2026 - [Ora score page for aws.amazon.com](https://ora.ai/score/aws.amazon.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Amazon Web Services website](https://aws.amazon.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Axiom MCP server | Agent MCP Directory" description: "Axiom: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/axiom-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Axiom MCP server | Agent MCP Directory > Axiom: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/axiom-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Axiom: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Axiom at mcp.axiom.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Axiom | | --- | --- | | Domain | axiom.co | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for axiom.co, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.axiom.co/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 521 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:36Z https://mcp.axiom.co/mcp sent initialize result auth-required (HTTP 401) 498 ms - 20:02:10Z https://mcp.axiom.co/mcp sent initialize result auth-required (HTTP 401) 521 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.axiom.co/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.axiom.co | | Authorization server metadata | authorization.axiom.co | | Registration endpoint | https://authorization.axiom.co/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.axiom.co/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.axiom.co/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://authorization.axiom.co/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Axiom. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.axiom/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/axiom-co/index.md) ## Sources - [Ora score page for axiom.co](https://ora.ai/score/axiom.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=axiom), read 4 November 2026 - [Axiom website](https://axiom.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Axolo MCP server | Agent MCP Directory" description: "Does Axolo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/axolo-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Axolo MCP server | Agent MCP Directory > Does Axolo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/axolo-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Axolo: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Axolo (axolo.co), so the connector had nothing to connect to. Ora's cached score for axolo.co is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Axolo (registry title: axolo.co) | | --- | --- | | Domain | axolo.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 18 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for axolo.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Axolo. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for axolo.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Axolo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/axolo-co/index.md) ## Sources - [Ora score page for axolo.co](https://ora.ai/score/axolo.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 August 2026, read from GET /api/leaderboard) - [Where Axolo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Axolo website](https://axolo.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Azure MCP server | Agent MCP Directory" description: "Does Azure have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/azure-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Azure MCP server | Agent MCP Directory > Does Azure have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/azure-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Azure: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Azure (azure.com), so the connector had nothing to connect to. Ora's cached score for azure.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Azure (registry title: azure.com) | | --- | --- | | Domain | azure.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 18 on the list of 4 November 2026 | | Ora score | 58, grade C; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for azure.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Azure. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for azure.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Azure. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/azure-com/index.md) ## Sources - [Ora score page for azure.com](https://ora.ai/score/azure.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/score) - [Where Azure was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Azure website](https://azure.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Microsoft Azure MCP server | Agent MCP Directory" description: "Does Microsoft Azure have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/azure-microsoft-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Microsoft Azure MCP server | Agent MCP Directory > Does Microsoft Azure have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/azure-microsoft-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Microsoft Azure: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Microsoft Azure (azure.microsoft.com), so the connector had nothing to connect to. Ora's cached score for azure.microsoft.com is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Microsoft Azure | | --- | --- | | Domain | azure.microsoft.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 11 May 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for azure.microsoft.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Microsoft Azure. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for azure.microsoft.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Microsoft Azure. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/azure-microsoft-com/index.md) ## Sources - [Ora score page for azure.microsoft.com](https://ora.ai/score/azure.microsoft.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 May 2026, read from GET /api/leaderboard) - [Where Microsoft Azure was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Microsoft Azure website](https://azure.microsoft.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Backendless MCP server | Agent MCP Directory" description: "Does Backendless have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/backendless-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Backendless MCP server | Agent MCP Directory > Does Backendless have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/backendless-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Backendless: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Backendless (backendless.com), so the connector had nothing to connect to. Ora's cached score for backendless.com is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Backendless (registry title: backendless.com) | | --- | --- | | Domain | backendless.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for backendless.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Backendless. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for backendless.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Backendless. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/backendless-com/index.md) ## Sources - [Ora score page for backendless.com](https://ora.ai/score/backendless.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Where Backendless was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Backendless website](https://backendless.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ball Ranks MCP server | Agent MCP Directory" description: "Ball Ranks has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ballranks-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ball Ranks MCP server | Agent MCP Directory > Ball Ranks has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ballranks-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ball Ranks: MCP server, CLI and agent surfaces Yes: Ball Ranks runs a public MCP server at ballranks.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: get\_week\_rankings, get\_season\_rankings, get\_player\_rankings. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Ball Ranks (registry title: Ball Ranks Fantasy Sports) | | --- | --- | | Domain | ballranks.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for ballranks.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ballranks.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | ball-ranks-public-api 1.1.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,029 ms over 1 attempt | ### Tools listed 4 tools - get\_week\_rankings - get\_season\_rankings - get\_player\_rankings - get\_player\_projections ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:39Z https://ballranks.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2237 ms - 20:02:12Z https://ballranks.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2029 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://ballranks.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ball Ranks. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: ballranks.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ballranks-com/index.md) ## Sources - [Ball Ranks website](https://ballranks.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Barevalue MCP server | Agent MCP Directory" description: "Barevalue has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/barevalue-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Barevalue MCP server | Agent MCP Directory > Barevalue has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/barevalue-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Barevalue: MCP server, CLI and agent surfaces Yes: Barevalue runs a public MCP server at barevalue.com that listed 14 tools to a client with no credentials on 4 November 2026. Examples: barevalue\_register, barevalue\_pricing, barevalue\_api\_status. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Barevalue | | --- | --- | | Domain | barevalue.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for barevalue.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://barevalue.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | barevalue 1.16.3 | | Capabilities | tools | | Tools | 14 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,166 ms over 1 attempt | ### Tools listed 14 tools - barevalue\_register - barevalue\_pricing - barevalue\_api\_status - barevalue\_account - barevalue\_estimate - barevalue\_validate - barevalue\_upload - barevalue\_submit\_url - barevalue\_status - barevalue\_content - barevalue\_feedback - barevalue\_request\_revision - barevalue\_updates - barevalue\_list\_orders ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:38Z https://barevalue.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1378 ms - 20:02:12Z https://barevalue.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1166 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://barevalue.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Barevalue. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/barevalue-com/index.md) ## Sources - [Barevalue website](https://barevalue.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Base44 MCP server | Agent MCP Directory" description: "Does Base44 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/base44-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Base44 MCP server | Agent MCP Directory > Does Base44 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/base44-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Base44: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Base44 (base44.com), so the connector had nothing to connect to. Ora's cached score for base44.com is 86, grade A, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Base44 | | --- | --- | | Domain | base44.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 86, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for base44.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Base44. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for base44.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Base44. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/base44-com/index.md) ## Sources - [Ora score page for base44.com](https://ora.ai/score/base44.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Base44 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Base44 website](https://base44.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Basecamp MCP server | Agent MCP Directory" description: "Basecamp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/basecamp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Basecamp MCP server | Agent MCP Directory > Basecamp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/basecamp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Basecamp: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Basecamp at mcp.basecamp.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Basecamp | | --- | --- | | Domain | basecamp.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 6,105 on the list of 4 November 2026 | | Ora score | 45, grade D; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for basecamp.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.basecamp.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 403 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:09Z https://mcp.basecamp.com/mcp sent initialize result auth-required (HTTP 401) 377 ms - 20:01:48Z https://mcp.basecamp.com/mcp sent initialize result auth-required (HTTP 401) 403 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.basecamp.com/.well-known/oauth-protected-resource/mcp", scope="mcp full", DPoP algs="ES256" | | Protected resource metadata | mcp.basecamp.com | | Authorization server metadata | app.basecamp.com | | Registration endpoint | https://app.basecamp.com/oauth/clients | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.basecamp.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.basecamp.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.basecamp.com/oauth/clients` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Basecamp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.basecamp/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/basecamp-com/index.md) ## Sources - [Ora score page for basecamp.com](https://ora.ai/score/basecamp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where Basecamp was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.basecamp%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=basecamp), read 4 November 2026 - [Basecamp website](https://basecamp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Basedash MCP server | Agent MCP Directory" description: "Basedash: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/basedash-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Basedash MCP server | Agent MCP Directory > Basedash: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/basedash-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Basedash: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Basedash at charts.basedash.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Basedash | | --- | --- | | Domain | basedash.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 74, grade B; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for basedash.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://charts.basedash.com/api/public/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,104 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:38Z https://charts.basedash.com/api/public/mcp sent initialize result auth-required (HTTP 401) 1299 ms - 20:02:12Z https://charts.basedash.com/api/public/mcp sent initialize result auth-required (HTTP 401) 1104 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="basedash-mcp", resource_metadata="https://charts.basedash.com/.well-known/oauth-protected-resource/api/public/mcp" | | Protected resource metadata | charts.basedash.com | | Authorization server metadata | charts.basedash.com | | Registration endpoint | https://charts.basedash.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://charts.basedash.com/api/public/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://charts.basedash.com/.well-known/oauth-protected-resource/api/public/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://charts.basedash.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Basedash. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.basedash/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/basedash-com/index.md) ## Sources - [Ora score page for basedash.com](https://ora.ai/score/basedash.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Where Basedash was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.basedash%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=basedash), read 4 November 2026 - [Basedash website](https://basedash.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Baserow MCP server | Agent MCP Directory" description: "Baserow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/baserow-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Baserow MCP server | Agent MCP Directory > Baserow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/baserow-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Baserow: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Baserow at api.baserow.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Baserow | | --- | --- | | Domain | baserow.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for baserow.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.baserow.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 409 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:37Z https://api.baserow.io/mcp sent initialize result auth-required (HTTP 401) 518 ms - 20:02:11Z https://api.baserow.io/mcp sent initialize result auth-required (HTTP 401) 409 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.baserow.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.baserow.io | | Authorization server metadata | api.baserow.io | | Registration endpoint | https://api.baserow.io/oauth/register/ | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.baserow.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.baserow.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.baserow.io/oauth/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Baserow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.baserow/baserow | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/baserow-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=baserow), read 4 November 2026 - [Baserow website](https://baserow.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Beam MCP server | Agent MCP Directory" description: "Does Beam have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/beam-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Beam MCP server | Agent MCP Directory > Does Beam have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/beam-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # Beam: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Beam (beam.cloud), so the connector had nothing to connect to. Ora's cached score for beam.cloud is 74, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Beam (registry title: beam.cloud) | | --- | --- | | Domain | beam.cloud | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 74, grade B; Ora scanned the domain on 14 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for beam.cloud, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Beam. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for beam.cloud, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Beam. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/beam-cloud/index.md) ## Sources - [Ora score page for beam.cloud](https://ora.ai/score/beam.cloud?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 October 2026, read from GET /api/leaderboard) - [Where Beam was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Beam website](https://beam.cloud), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Beancount.io MCP server | Agent MCP Directory" description: "Beancount.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/beancount-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Beancount.io MCP server | Agent MCP Directory > Beancount.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/beancount-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Beancount.io: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Beancount.io at beancount.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Beancount.io | | --- | --- | | Domain | beancount.io | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 70, grade B; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for beancount.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://beancount.io/api-gateway/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 768 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:39Z https://beancount.io/api-gateway/mcp sent initialize result auth-required (HTTP 401) 1282 ms - 20:02:12Z https://beancount.io/api-gateway/mcp sent initialize result auth-required (HTTP 401) 768 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://beancount.io/.well-known/oauth-protected-resource" | | Protected resource metadata | beancount.io | | Authorization server metadata | beancount.io | | Registration endpoint | https://beancount.io/api-gateway/oauth/reg | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://beancount.io/api-gateway/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://beancount.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://beancount.io/api-gateway/oauth/reg` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Beancount.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: beancount.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.beancount/beancount | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/beancount-io/index.md) ## Sources - [Ora score page for beancount.io](https://ora.ai/score/beancount.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=beancount), read 4 November 2026 - [Beancount.io website](https://beancount.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bear MCP server | Agent MCP Directory" description: "Does Bear have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/bear-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bear MCP server | Agent MCP Directory > Does Bear have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/bear-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bear: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Bear (bear.app), so the connector had nothing to connect to. Ora's cached score for bear.app is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Bear (registry title: bear.app) | | --- | --- | | Domain | bear.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 7 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bear.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Bear. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bear.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Bear. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bear-app/index.md) ## Sources - [Ora score page for bear.app](https://ora.ai/score/bear.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 October 2026, read from GET /api/leaderboard) - [Where Bear was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bear website](https://bear.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "beehiiv MCP server | Agent MCP Directory" description: "beehiiv: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media." canonical: https://agentmcpdirectory.com/directory/beehiiv-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # beehiiv MCP server | Agent MCP Directory > beehiiv: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media. Source: https://agentmcpdirectory.com/directory/beehiiv-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # beehiiv: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for beehiiv at mcp.beehiiv.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | beehiiv | | --- | --- | | Domain | beehiiv.com | | Category | Gaming & Media (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 5,743 on the list of 4 November 2026 | | Ora score | 88, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for beehiiv.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.beehiiv.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,052 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:09Z https://mcp.beehiiv.com/mcp sent initialize result auth-required (HTTP 401) 600 ms - 20:01:46Z https://mcp.beehiiv.com/mcp sent initialize result auth-required (HTTP 401) 1052 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.beehiiv.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.beehiiv.com | | Authorization server metadata | mcp.beehiiv.com | | Registration endpoint | https://mcp.beehiiv.com/register | ### The sign-in route, step by step 1. Request `https://mcp.beehiiv.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.beehiiv.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.beehiiv.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for beehiiv. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.beehiiv.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.beehiiv/beehiiv | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/beehiiv-com/index.md) ## Sources - [Ora score page for beehiiv.com](https://ora.ai/score/beehiiv.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=beehiiv), read 4 November 2026 - [beehiiv website](https://beehiiv.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Beglaubigt MCP server | Agent MCP Directory" description: "Beglaubigt has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/beglaubigt-de site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Beglaubigt MCP server | Agent MCP Directory > Beglaubigt has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/beglaubigt-de Site: Agent MCP Directory Last reviewed: 2026-11-05 # Beglaubigt: MCP server, CLI and agent surfaces Yes: Beglaubigt runs a public MCP server at mcp.beglaubigt.de that listed 1 tool to a client with no credentials on 4 November 2026. Examples: create\_incorporation. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for beglaubigt.de is 49, grade C, read on 5 November 2026. ## Fact sheet | Company | Beglaubigt | | --- | --- | | Domain | beglaubigt.de | | Category | Legal & Compliance (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 49, grade C; Ora scanned the domain on 1 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for beglaubigt.de, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.beglaubigt.de/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | beglaubigt-mcp 0.2.0 | | Capabilities | tools, resources | | Tools | 1 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 687 ms over 1 attempt | ### Tools listed 1 tool - create\_incorporation ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:39Z https://mcp.beglaubigt.de/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 910 ms - 20:02:12Z https://mcp.beglaubigt.de/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 687 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.beglaubigt.de/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Beglaubigt. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: de.beglaubigt/incorporation | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/beglaubigt-de/index.md) ## Sources - [Ora score page for beglaubigt.de](https://ora.ai/score/beglaubigt.de?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 September 2026, read from GET /api/score) - [Where Beglaubigt was found](https://registry.modelcontextprotocol.io/v0/servers?search=de.beglaubigt%2Fincorporation), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=beglaubigt), read 4 November 2026 - [Beglaubigt website](https://beglaubigt.de), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BeliefState MCP server | Agent MCP Directory" description: "BeliefState: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/beliefstate-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BeliefState MCP server | Agent MCP Directory > BeliefState: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/beliefstate-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # BeliefState: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for BeliefState at beliefstate.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | BeliefState | | --- | --- | | Domain | beliefstate.ai | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for beliefstate.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://beliefstate.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,750 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:41Z https://beliefstate.ai/mcp sent initialize result auth-required (HTTP 401) 2700 ms - 20:02:14Z https://beliefstate.ai/mcp sent initialize result auth-required (HTTP 401) 2750 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="BeliefState MCP", error="invalid_token", resource_metadata="https://beliefstate.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | beliefstate.ai | | Authorization server metadata | clerk.beliefstate.ai | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://beliefstate.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://beliefstate.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BeliefState. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: beliefstate.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.beliefstate/investor-research | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/beliefstate-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=beliefstate), read 4 November 2026 - [BeliefState website](https://beliefstate.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Benchspan MCP server | Agent MCP Directory" description: "Does Benchspan have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/benchspan-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Benchspan MCP server | Agent MCP Directory > Does Benchspan have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/benchspan-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Benchspan: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Benchspan (benchspan.com), so the connector had nothing to connect to. Ora's cached score for benchspan.com is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Benchspan (registry title: benchspan.com) | | --- | --- | | Domain | benchspan.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for benchspan.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Benchspan. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for benchspan.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Benchspan. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/benchspan-com/index.md) ## Sources - [Ora score page for benchspan.com](https://ora.ai/score/benchspan.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Benchspan was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Benchspan website](https://benchspan.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bento MCP server | Agent MCP Directory" description: "Does Bento have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bentoml-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bento MCP server | Agent MCP Directory > Does Bento have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/bentoml-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bento: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Bento (bentoml.com), so the connector had nothing to connect to. Ora's cached score for bentoml.com is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Bento (registry title: bentoml.com) | | --- | --- | | Domain | bentoml.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bentoml.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Bento. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bentoml.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Bento. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bentoml-com/index.md) ## Sources - [Ora score page for bentoml.com](https://ora.ai/score/bentoml.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Bento was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bento website](https://bentoml.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BestPrice MCP server | Agent MCP Directory" description: "BestPrice has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bestprice-gr site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BestPrice MCP server | Agent MCP Directory > BestPrice has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bestprice-gr Site: Agent MCP Directory Last reviewed: 2026-11-05 # BestPrice: MCP server, CLI and agent surfaces Yes: BestPrice runs a public MCP server at mcp.bestprice.gr that listed 6 tools to a client with no credentials on 4 November 2026. Examples: get\_shopping\_decision, search\_products, compare\_offers. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for bestprice.gr is 35, grade D, read on 5 November 2026. ## Fact sheet | Company | BestPrice | | --- | --- | | Domain | bestprice.gr | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 35, grade D; Ora scanned the domain on 27 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for bestprice.gr, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bestprice.gr/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | bestprice-agent-commerce 1.9.0 | | Capabilities | extensions, events, resources, tools | | Tools | 6 | | Resources | 4 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,070 ms over 1 attempt | ### Tools listed 6 tools - get\_shopping\_decision - search\_products - compare\_offers - get\_price\_history - optimize\_basket - check\_deal ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:40Z https://mcp.bestprice.gr/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1333 ms - 20:02:13Z https://mcp.bestprice.gr/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1070 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.bestprice.gr/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BestPrice. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: gr.bestprice/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bestprice-gr/index.md) ## Sources - [Ora score page for bestprice.gr](https://ora.ai/score/bestprice.gr?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bestprice), read 4 November 2026 - [BestPrice website](https://bestprice.gr), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Better Stack MCP server | Agent MCP Directory" description: "Better Stack has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/betterstack-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Better Stack MCP server | Agent MCP Directory > Better Stack has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/betterstack-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Better Stack: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Better Stack; the connector tried mcp.betterstack.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain;charset=utf-8). ## Fact sheet | Company | Better Stack (registry title: betterstack.com) | | --- | --- | | Domain | betterstack.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Ora score | 59, grade C; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for betterstack.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.betterstack.com/mcp | | --- | --- | | How it was found | mcp.betterstack.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 86 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain;charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:38Z https://mcp.betterstack.com/mcp sent initialize result no-answer (HTTP 404) 62 ms - 20:02:12Z https://mcp.betterstack.com/mcp sent initialize result no-answer (HTTP 404) 86 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.betterstack.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain;charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Better Stack. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: betterstack.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/betterstack-com/index.md) ## Sources - [Ora score page for betterstack.com](https://ora.ai/score/betterstack.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Better Stack was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Better Stack website](https://betterstack.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Betteruptime MCP server | Agent MCP Directory" description: "Does Betteruptime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/betteruptime-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Betteruptime MCP server | Agent MCP Directory > Does Betteruptime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/betteruptime-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Betteruptime: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Betteruptime (betteruptime.com), so the connector had nothing to connect to. Ora's cached score for betteruptime.com is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Betteruptime (registry title: betteruptime.com) | | --- | --- | | Domain | betteruptime.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for betteruptime.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Betteruptime. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for betteruptime.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Betteruptime. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/betteruptime-com/index.md) ## Sources - [Ora score page for betteruptime.com](https://ora.ai/score/betteruptime.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Betteruptime was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Betteruptime website](https://betteruptime.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BGPT MCP server | Agent MCP Directory" description: "BGPT has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bgpt-pro site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BGPT MCP server | Agent MCP Directory > BGPT has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bgpt-pro Site: Agent MCP Directory Last reviewed: 2026-11-05 # BGPT: MCP server, CLI and agent surfaces Yes: BGPT runs a public MCP server at bgpt.pro that listed 2 tools to a client with no credentials on 4 November 2026. Examples: search\_papers, lookup\_paper. It speaks sse, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | BGPT | | --- | --- | | Domain | bgpt.pro | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for bgpt.pro when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://bgpt.pro/mcp/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | sse | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | BGPT 2.14.7 | | Capabilities | experimental, prompts, resources, tools, tasks | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,585 ms over 2 attempts | ### Tools listed 2 tools - search\_papers - lookup\_paper ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:40Z https://bgpt.pro/mcp/sse sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1510 ms - 20:02:14Z https://bgpt.pro/mcp/sse sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1585 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://bgpt.pro/mcp/sse` over sse. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BGPT. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bgpt-pro/index.md) ## Sources - [Where BGPT was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [BGPT website](https://bgpt.pro), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bibooks MCP server | Agent MCP Directory" description: "Bibooks has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bibooks-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bibooks MCP server | Agent MCP Directory > Bibooks has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bibooks-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bibooks: MCP server, CLI and agent surfaces Yes: Bibooks runs a public MCP server at bibooks.org that listed 5 tools to a client with no credentials on 4 November 2026. Examples: search\_books, get\_book, read\_book. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Bibooks | | --- | --- | | Domain | bibooks.org | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for bibooks.org when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://bibooks.org/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | bibooks 1.1.1 | | Capabilities | prompts, resources, tools | | Tools | 5 | | Resources | 0 | | Prompts | 2 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,853 ms over 1 attempt | ### Tools listed 5 tools - search\_books - get\_book - read\_book - find\_related\_books - list\_languages ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:41Z https://bibooks.org/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1983 ms - 20:02:14Z https://bibooks.org/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1853 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://bibooks.org/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bibooks. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bibooks-org/index.md) ## Sources - [Bibooks website](https://bibooks.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bigdata.com MCP server | Agent MCP Directory" description: "Bigdata.com: sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/bigdata-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bigdata.com MCP server | Agent MCP Directory > Bigdata.com: sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/bigdata-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bigdata.com: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Bigdata.com at mcp.bigdata.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Bigdata.com | | --- | --- | | Domain | bigdata.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 63, grade C; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for bigdata.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bigdata.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 812 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:40Z https://mcp.bigdata.com/ sent initialize result auth-required (HTTP 401) 1386 ms - 20:02:13Z https://mcp.bigdata.com/ sent initialize result auth-required (HTTP 401) 812 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer | | Protected resource metadata | mcp.bigdata.com | | Authorization server metadata | clerk.bigdata.com | ### The sign-in route, step by step 1. Request `https://mcp.bigdata.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://clerk.bigdata.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bigdata.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.bigdata/bigdata-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bigdata-com/index.md) ## Sources - [Ora score page for bigdata.com](https://ora.ai/score/bigdata.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bigdata), read 4 November 2026 - [Bigdata.com website](https://bigdata.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BigPanda MCP server | Agent MCP Directory" description: "Does BigPanda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bigpanda-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BigPanda MCP server | Agent MCP Directory > Does BigPanda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/bigpanda-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # BigPanda: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for BigPanda (bigpanda.io), so the connector had nothing to connect to. Ora's cached score for bigpanda.io is 54, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | BigPanda (registry title: bigpanda.io) | | --- | --- | | Domain | bigpanda.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 54, grade C; Ora scanned the domain on 12 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bigpanda.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for BigPanda. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bigpanda.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for BigPanda. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: bigpanda.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bigpanda-io/index.md) ## Sources - [Ora score page for bigpanda.io](https://ora.ai/score/bigpanda.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 October 2026, read from GET /api/leaderboard) - [Where BigPanda was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [BigPanda website](https://bigpanda.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BigTime MCP server | Agent MCP Directory" description: "Does BigTime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bigtime-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BigTime MCP server | Agent MCP Directory > Does BigTime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/bigtime-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # BigTime: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for BigTime (bigtime.net), so the connector had nothing to connect to. Ora's cached score for bigtime.net is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | BigTime (registry title: bigtime.net) | | --- | --- | | Domain | bigtime.net | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bigtime.net, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for BigTime. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bigtime.net, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for BigTime. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: bigtime.net/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bigtime-net/index.md) ## Sources - [Ora score page for bigtime.net](https://ora.ai/score/bigtime.net?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/leaderboard) - [Where BigTime was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [BigTime website](https://bigtime.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bird MCP server | Agent MCP Directory" description: "Bird: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bird-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bird MCP server | Agent MCP Directory > Bird: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bird-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bird: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Bird at mcp.bird.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Bird | | --- | --- | | Domain | bird.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 91, grade A; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bird.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bird.com | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 842 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:41Z https://mcp.bird.com sent initialize result auth-required (HTTP 401) 1038 ms - 20:02:14Z https://mcp.bird.com sent initialize result auth-required (HTTP 401) 842 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.bird.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.bird.com | | Authorization server metadata | platform.bird.com | | Registration endpoint | https://platform.bird.com/v1/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.bird.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.bird.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://platform.bird.com/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bird. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: bird.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.bird/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bird-com/index.md) ## Sources - [Ora score page for bird.com](https://ora.ai/score/bird.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/leaderboard) - [Where Bird was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.bird%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bird), read 4 November 2026 - [Bird website](https://bird.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bitbucket MCP server | Agent MCP Directory" description: "Does Bitbucket have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bitbucket-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bitbucket MCP server | Agent MCP Directory > Does Bitbucket have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/bitbucket-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bitbucket: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Bitbucket (bitbucket.org), so the connector had nothing to connect to. Ora's cached score for bitbucket.org is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Bitbucket (registry title: bitbucket.org) | | --- | --- | | Domain | bitbucket.org | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,055 on the list of 4 November 2026 | | Ora score | 34, grade D; Ora scanned the domain on 12 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for bitbucket.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Bitbucket. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bitbucket.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Bitbucket. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bitbucket-org/index.md) ## Sources - [Ora score page for bitbucket.org](https://ora.ai/score/bitbucket.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 October 2026, read from GET /api/score) - [Where Bitbucket was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bitbucket website](https://bitbucket.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bitculator MCP server | Agent MCP Directory" description: "Bitculator: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/bitculator-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bitculator MCP server | Agent MCP Directory > Bitculator: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/bitculator-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bitculator: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Bitculator at bitculator.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Bitculator | | --- | --- | | Domain | bitculator.com | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for bitculator.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://bitculator.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 673 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:41Z https://bitculator.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 774 ms - 20:02:14Z https://bitculator.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 673 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | ApiKey realm="mcp" | ### The sign-in route, step by step 1. Request `https://bitculator.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bitculator. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.bitculator/market-data | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bitculator-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bitculator), read 4 November 2026 - [Bitculator website](https://bitculator.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bitly MCP server | Agent MCP Directory" description: "Bitly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bitly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bitly MCP server | Agent MCP Directory > Bitly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bitly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bitly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Bitly at api-ssl.bitly.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Bitly | | --- | --- | | Domain | bitly.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,755 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for bitly.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api-ssl.bitly.com/v4/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 678 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:03Z https://api-ssl.bitly.com/v4/mcp sent initialize result auth-required (HTTP 401) 796 ms - 20:01:39Z https://api-ssl.bitly.com/v4/mcp sent initialize result auth-required (HTTP 401) 678 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer as_uri="https://api-ssl.bitly.com/.well-known/oauth-protected-resource", error="invalid_token" | | Protected resource metadata | api-ssl.bitly.com | | Authorization server metadata | api-ssl.bitly.com | | Registration endpoint | https://api-ssl.bitly.com/oauth/register | ### The sign-in route, step by step 1. Request `https://api-ssl.bitly.com/v4/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api-ssl.bitly.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api-ssl.bitly.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bitly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.bitly/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bitly-com/index.md) ## Sources - [Where Bitly was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.bitly%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bitly), read 4 November 2026 - [Bitly website](https://bitly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bitmovin MCP server | Agent MCP Directory" description: "Bitmovin has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bitmovin-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bitmovin MCP server | Agent MCP Directory > Bitmovin has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bitmovin-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bitmovin: MCP server, CLI and agent surfaces Yes: Bitmovin runs a public MCP server at analytics.mcp.bitmovin.com that listed 11 tools to a client with no credentials on 4 November 2026. Examples: query, queryGroupBy, queryTotal. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for bitmovin.com is 80, grade B, read on 5 November 2026. ## Fact sheet | Company | Bitmovin (registry title: Bitmovin Observability MCP) | | --- | --- | | Domain | bitmovin.com | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 80, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for bitmovin.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://analytics.mcp.bitmovin.com | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | analytics-mcp 0.0.1 | | Capabilities | prompts, resources, tools | | Tools | 11 | | Resources | 6 | | Prompts | 3 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,486 ms over 1 attempt | ### Tools listed 11 tools - query - queryGroupBy - queryTotal - peekAllLicenses - getImpressionOverview - analyzeImpression - fetchImpressions - getAvailableMetrics - getAvailableFilters - searchMetrics - searchFilters ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:44Z https://analytics.mcp.bitmovin.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2940 ms - 20:02:16Z https://analytics.mcp.bitmovin.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2486 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://analytics.mcp.bitmovin.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bitmovin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.bitmovin.mcp.analytics/analytics-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bitmovin-com/index.md) ## Sources - [Ora score page for bitmovin.com](https://ora.ai/score/bitmovin.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Bitmovin was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.bitmovin.mcp.analytics%2Fanalytics-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bitmovin), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bitrise MCP server | Agent MCP Directory" description: "Bitrise: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/bitrise-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bitrise MCP server | Agent MCP Directory > Bitrise: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/bitrise-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bitrise: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Bitrise; the connector's guess at mcp.bitrise.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Bitrise | | --- | --- | | Domain | bitrise.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 68, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bitrise.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bitrise.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,115 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:42Z https://mcp.bitrise.io/mcp sent initialize result auth-required (HTTP 401) 1680 ms - 20:02:15Z https://mcp.bitrise.io/mcp sent initialize result auth-required (HTTP 401) 1115 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.bitrise.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.bitrise.io | | Authorization server metadata | oauth.bitrise.io | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.bitrise.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.bitrise.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bitrise. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bitrise-io/index.md) ## Sources - [Ora score page for bitrise.io](https://ora.ai/score/bitrise.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where Bitrise was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bitrise website](https://bitrise.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BittleBits MCP server | Agent MCP Directory" description: "BittleBits has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/bittlebits-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BittleBits MCP server | Agent MCP Directory > BittleBits has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/bittlebits-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # BittleBits: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for BittleBits (bittlebits.ai), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: ENOTFOUND. The row is kept so the claim is visible and can be re-checked next edition. ## Fact sheet | Company | BittleBits (registry title: BittleBits GEO Assistant) | | --- | --- | | Domain | bittlebits.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for bittlebits.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://bittlebits.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 6 ms over 1 attempt | | Result | ENOTFOUND | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:41Z https://bittlebits.ai/mcp sent initialize result no-answer 139 ms - 20:02:14Z https://bittlebits.ai/mcp sent initialize result no-answer 6 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://bittlebits.ai/mcp`. The connector could not tell what it wants: ENOTFOUND. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BittleBits. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.bittlebits/bittlebits | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bittlebits-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bittlebits), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Blacksmith MCP server | Agent MCP Directory" description: "Does Blacksmith have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/blacksmith-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Blacksmith MCP server | Agent MCP Directory > Does Blacksmith have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/blacksmith-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Blacksmith: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Blacksmith (blacksmith.sh), so the connector had nothing to connect to. Ora's cached score for blacksmith.sh is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Blacksmith (registry title: blacksmith.sh) | | --- | --- | | Domain | blacksmith.sh | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for blacksmith.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Blacksmith. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for blacksmith.sh, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Blacksmith. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/blacksmith-sh/index.md) ## Sources - [Ora score page for blacksmith.sh](https://ora.ai/score/blacksmith.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/leaderboard) - [Where Blacksmith was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Blacksmith website](https://blacksmith.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bland MCP server | Agent MCP Directory" description: "Does Bland have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bland-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bland MCP server | Agent MCP Directory > Does Bland have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/bland-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bland: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Bland (bland.com), so the connector had nothing to connect to. Ora's cached score for bland.com is 60, grade C, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Bland (registry title: bland.com) | | --- | --- | | Domain | bland.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bland.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Bland. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bland.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Bland. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.bland.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bland-com/index.md) ## Sources - [Ora score page for bland.com](https://ora.ai/score/bland.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Bland was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bland website](https://bland.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Blaxel MCP server | Agent MCP Directory" description: "Does Blaxel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/blaxel-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Blaxel MCP server | Agent MCP Directory > Does Blaxel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/blaxel-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Blaxel: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Blaxel (blaxel.ai), so the connector had nothing to connect to. Ora's cached score for blaxel.ai is 80, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Blaxel (registry title: blaxel.ai) | | --- | --- | | Domain | blaxel.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 80, grade B; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for blaxel.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Blaxel. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for blaxel.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Blaxel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/blaxel-ai/index.md) ## Sources - [Ora score page for blaxel.ai](https://ora.ai/score/blaxel.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Blaxel was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Blaxel website](https://blaxel.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BlindPay MCP server | Agent MCP Directory" description: "BlindPay: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/blindpay-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BlindPay MCP server | Agent MCP Directory > BlindPay: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/blindpay-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # BlindPay: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for BlindPay at mcp.blindpay.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | BlindPay | | --- | --- | | Domain | blindpay.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 90, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for blindpay.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.blindpay.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 815 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:43Z https://mcp.blindpay.com/mcp sent initialize result auth-required (HTTP 401) 1180 ms - 20:02:15Z https://mcp.blindpay.com/mcp sent initialize result auth-required (HTTP 401) 815 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.blindpay.com/.well-known/oauth-protected-resource/mcp", scope="profile email offline_access" | | Protected resource metadata | mcp.blindpay.com | | Authorization server metadata | clerk.blindpay.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.blindpay.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.blindpay.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BlindPay. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: blindpay.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: blindpay.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.blindpay/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/blindpay-com/index.md) ## Sources - [Ora score page for blindpay.com](https://ora.ai/score/blindpay.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where BlindPay was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.blindpay%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=blindpay), read 4 November 2026 - [BlindPay website](https://blindpay.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BlogSEO MCP server | Agent MCP Directory" description: "BlogSEO: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/blogseo-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BlogSEO MCP server | Agent MCP Directory > BlogSEO: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/blogseo-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # BlogSEO: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for BlogSEO at mcp.blogseo.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | BlogSEO | | --- | --- | | Domain | blogseo.io | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for blogseo.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.blogseo.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 895 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:43Z https://mcp.blogseo.io/mcp sent initialize result auth-required (HTTP 401) 1173 ms - 20:02:15Z https://mcp.blogseo.io/mcp sent initialize result auth-required (HTTP 401) 895 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.blogseo.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.blogseo.io | | Authorization server metadata | kccqmbkylzrrhibpxtbk.supabase.co | | Registration endpoint | https://kccqmbkylzrrhibpxtbk.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://mcp.blogseo.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.blogseo.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://kccqmbkylzrrhibpxtbk.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BlogSEO. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.blogseo/blogseo | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/blogseo-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=blogseo), read 4 November 2026 - [BlogSEO website](https://blogseo.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Blueprism MCP server | Agent MCP Directory" description: "Does Blueprism have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/blueprism-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Blueprism MCP server | Agent MCP Directory > Does Blueprism have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/blueprism-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Blueprism: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Blueprism (blueprism.com), so the connector had nothing to connect to. Ora's cached score for blueprism.com is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Blueprism (registry title: blueprism.com) | | --- | --- | | Domain | blueprism.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for blueprism.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Blueprism. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for blueprism.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Blueprism. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/blueprism-com/index.md) ## Sources - [Ora score page for blueprism.com](https://ora.ai/score/blueprism.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/leaderboard) - [Where Blueprism was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Blueprism website](https://blueprism.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bolna AI MCP server | Agent MCP Directory" description: "Bolna AI has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/bolna-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bolna AI MCP server | Agent MCP Directory > Bolna AI has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/bolna-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bolna AI: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Bolna AI; the connector tried mcp.bolna.ai as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). ## Fact sheet | Company | Bolna AI | | --- | --- | | Domain | bolna.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Ora score | 63, grade C; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bolna.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bolna.ai/mcp | | --- | --- | | How it was found | mcp.bolna.ai was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 491 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:43Z https://mcp.bolna.ai/mcp sent initialize result no-answer (HTTP 404) 608 ms - 20:02:15Z https://mcp.bolna.ai/mcp sent initialize result no-answer (HTTP 404) 491 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.bolna.ai/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bolna AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bolna-ai/index.md) ## Sources - [Ora score page for bolna.ai](https://ora.ai/score/bolna.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/leaderboard) - [Where Bolna AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bolna AI website](https://bolna.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bolt MCP server | Agent MCP Directory" description: "Does Bolt have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/bolt-new site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bolt MCP server | Agent MCP Directory > Does Bolt have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/bolt-new Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bolt: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Bolt (bolt.new), so the connector had nothing to connect to. Ora's cached score for bolt.new is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Bolt | | --- | --- | | Domain | bolt.new | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bolt.new, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Bolt. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bolt.new, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Bolt. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bolt-new/index.md) ## Sources - [Ora score page for bolt.new](https://ora.ai/score/bolt.new?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where Bolt was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bolt website](https://bolt.new), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Botcity MCP server | Agent MCP Directory" description: "Does Botcity have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/botcity-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Botcity MCP server | Agent MCP Directory > Does Botcity have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/botcity-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Botcity: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Botcity (botcity.dev), so the connector had nothing to connect to. Ora's cached score for botcity.dev is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Botcity (registry title: botcity.dev) | | --- | --- | | Domain | botcity.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for botcity.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Botcity. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for botcity.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Botcity. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/botcity-dev/index.md) ## Sources - [Ora score page for botcity.dev](https://ora.ai/score/botcity.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Botcity was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Botcity website](https://botcity.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bowmark MCP server | Agent MCP Directory" description: "Bowmark has an open MCP server with 26 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bowmark-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bowmark MCP server | Agent MCP Directory > Bowmark has an open MCP server with 26 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bowmark-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bowmark: MCP server, CLI and agent surfaces Yes: Bowmark runs a public MCP server at api.bowmark.ai that listed 26 tools to a client with no credentials on 4 November 2026. Examples: get\_library, run, run\_view. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Bowmark | | --- | --- | | Domain | bowmark.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for bowmark.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.bowmark.ai/mcp/registry | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | bowmark 8.208.2 | | Capabilities | tools, resources, prompts | | Tools | 26 | | Resources | 2 | | Prompts | 1 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,911 ms over 1 attempt | ### Tools listed 26 tools - get\_library - run - run\_view - jig\_open - jig\_list - jig\_update - jig\_view - jig\_cache - jig\_seen - jig\_perf - jig\_look - jig\_call - session\_call - session\_close - report - get\_usage - support - list\_secrets - request\_secret - get\_secret\_link - list\_connections - add\_connection - wait\_for\_sign\_in - lease\_ip - delete\_connection - logout\_connection ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:45Z https://api.bowmark.ai/mcp/registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2181 ms - 20:02:17Z https://api.bowmark.ai/mcp/registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1911 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.bowmark.ai/mcp/registry` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bowmark. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.bowmark/bowmark | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bowmark-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bowmark), read 4 November 2026 - [Bowmark website](https://bowmark.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Box MCP server | Agent MCP Directory" description: "Box: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/box-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Box MCP server | Agent MCP Directory > Box: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/box-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Box: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Box at mcp.box.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Box | | --- | --- | | Domain | box.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Tranco rank | 668 on the list of 4 November 2026 | | Ora score | 80, grade B; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for box.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.box.com | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,618 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.box.com sent initialize result auth-required (HTTP 401) 2617 ms - 20:01:33Z https://mcp.box.com sent initialize result auth-required (HTTP 401) 2618 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer realm="Service", error="invalid_request", error_description="The access token was not found.", resource_metadata="https://mcp.box.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.box.com | | Authorization server metadata | api.box.com | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.box.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://api.box.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Box. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/box-com/index.md) ## Sources - [Ora score page for box.com](https://ora.ai/score/box.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/score) - [Where Box was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Box website](https://box.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "brainattic MCP server | Agent MCP Directory" description: "brainattic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/brainattic-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # brainattic MCP server | Agent MCP Directory > brainattic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/brainattic-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # brainattic: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for brainattic at app.brainattic.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | brainattic | | --- | --- | | Domain | brainattic.ai | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for brainattic.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.brainattic.ai/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 947 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:45Z https://app.brainattic.ai/api/mcp sent initialize result auth-required (HTTP 401) 1865 ms - 20:02:16Z https://app.brainattic.ai/api/mcp sent initialize result auth-required (HTTP 401) 947 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="A Bearer token is required.", scope="brainattic:access", resource_metadata="https://app.brainattic.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | app.brainattic.ai | | Authorization server metadata | mcp.finite-soft.com | | Registration endpoint | https://mcp.finite-soft.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://app.brainattic.ai/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.brainattic.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.finite-soft.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for brainattic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.brainattic/knowledge-base | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/brainattic-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=brainattic), read 4 November 2026 - [brainattic website](https://brainattic.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Brainboard MCP server | Agent MCP Directory" description: "Does Brainboard have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/brainboard-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Brainboard MCP server | Agent MCP Directory > Does Brainboard have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/brainboard-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Brainboard: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Brainboard (brainboard.co), so the connector had nothing to connect to. Ora's cached score for brainboard.co is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Brainboard (registry title: brainboard.co) | | --- | --- | | Domain | brainboard.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for brainboard.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Brainboard. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for brainboard.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Brainboard. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/brainboard-co/index.md) ## Sources - [Ora score page for brainboard.co](https://ora.ai/score/brainboard.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where Brainboard was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Brainboard website](https://brainboard.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "The Brains MCP server | Agent MCP Directory" description: "The Brains: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/brains-ceo site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # The Brains MCP server | Agent MCP Directory > The Brains: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/brains-ceo Site: Agent MCP Directory Last reviewed: 2026-11-05 # The Brains: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for The Brains at mcp.brains.ceo answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | The Brains | | --- | --- | | Domain | brains.ceo | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for brains.ceo when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.brains.ceo/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 8,001 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:46Z https://mcp.brains.ceo/mcp sent initialize result auth-required (HTTP 401) 2241 ms - 20:02:23Z https://mcp.brains.ceo/mcp sent initialize result auth-required (HTTP 401) 8001 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.brains.ceo/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.brains.ceo | | Authorization server metadata | mcp.brains.ceo | | Registration endpoint | https://mcp.brains.ceo/register | ### The sign-in route, step by step 1. Request `https://mcp.brains.ceo/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.brains.ceo/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.brains.ceo/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for The Brains. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/brains-ceo/index.md) ## Sources - [Where The Brains was found](https://github.com/mcp/VicPitic/the-brains), read 4 November 2026 - [The Brains website](https://brains.ceo), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BreckenWander MCP server | Agent MCP Directory" description: "BreckenWander has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/breckenwander-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BreckenWander MCP server | Agent MCP Directory > BreckenWander has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/breckenwander-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # BreckenWander: MCP server, CLI and agent surfaces Yes: BreckenWander runs a public MCP server at mcp.breckenwander.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: search\_flights, search\_hotels, search\_experiences. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | BreckenWander (registry title: BreckenWander Travel) | | --- | --- | | Domain | breckenwander.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for breckenwander.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.breckenwander.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | breckenwander 0.2.0 | | Capabilities | tools, resources | | Tools | 4 | | Resources | 4 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,074 ms over 1 attempt | ### Tools listed 4 tools - search\_flights - search\_hotels - search\_experiences - build\_trip ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:45Z https://mcp.breckenwander.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1208 ms - 20:02:17Z https://mcp.breckenwander.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1074 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.breckenwander.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BreckenWander. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.breckenwander/travel-connector | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/breckenwander-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=breckenwander), read 4 November 2026 - [BreckenWander website](https://breckenwander.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "briq MCP server | Agent MCP Directory" description: "briq: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/briq-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # briq MCP server | Agent MCP Directory > briq: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/briq-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # briq: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for briq at api.briq.cloud answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | briq | | --- | --- | | Domain | briq.cloud | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for briq.cloud when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.briq.cloud/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 923 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:45Z https://api.briq.cloud/mcp sent initialize result auth-required (HTTP 401) 1023 ms - 20:02:17Z https://api.briq.cloud/mcp sent initialize result auth-required (HTTP 401) 923 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.briq.cloud/.well-known/oauth-protected-resource/mcp", scope="briq" | | Protected resource metadata | api.briq.cloud | | Authorization server metadata | app.briq.cloud | | Registration endpoint | https://app.briq.cloud/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.briq.cloud/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.briq.cloud/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.briq.cloud/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for briq. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: cloud.briq/briq | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/briq-cloud/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=briq), read 4 November 2026 - [briq website](https://briq.cloud), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Browser Use MCP server | Agent MCP Directory" description: "Browser Use has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/browser-use-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Browser Use MCP server | Agent MCP Directory > Browser Use has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/browser-use-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Browser Use: MCP server, CLI and agent surfaces Yes: Browser Use runs a public MCP server at api.browser-use.com that listed 7 tools to a client with no credentials on 4 November 2026. Examples: run\_session, send\_task, get\_session. It speaks streamable-http, protocol 2024-11-05. Ora's cached score for browser-use.com is 91, grade A, read on 5 November 2026. ## Fact sheet | Company | Browser Use (registry title: browser-use.com) | | --- | --- | | Domain | browser-use.com | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 91, grade A; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for browser-use.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.browser-use.com/v3/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | browser-use-v3-agent 3.0.0 | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,437 ms over 1 attempt | ### Tools listed 7 tools - run\_session - send\_task - get\_session - get\_session\_messages - stop\_session - list\_sessions - list\_browser\_profiles ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:45Z https://api.browser-use.com/v3/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1589 ms - 20:02:17Z https://api.browser-use.com/v3/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1437 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.browser-use.com/v3/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Browser Use. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: docs.browser-use.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: browser-use.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.browser-use/browser-use | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/browser-use-com/index.md) ## Sources - [Ora score page for browser-use.com](https://ora.ai/score/browser-use.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/score) - [Where Browser Use was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.browser-use%2Fbrowser-use), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=browser-use), read 4 November 2026 - [Browser Use website](https://browser-use.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Browserbase MCP server | Agent MCP Directory" description: "Does Browserbase have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/browserbase-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Browserbase MCP server | Agent MCP Directory > Does Browserbase have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/browserbase-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Browserbase: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Browserbase (browserbase.com), so the connector had nothing to connect to. Ora's cached score for browserbase.com is 84, grade B, read on 5 November 2026. The company was added from the vendor's own documentation. ## Fact sheet | Company | Browserbase | | --- | --- | | Domain | browserbase.com | | Category | Agent Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 84, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for browserbase.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Browserbase. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for browserbase.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | A package named `@browserbasehq/mcp-server-browserbase` on npm appears in a registry entry. It is a local package, not a remote endpoint, so it is not counted here. ## CLI No CLI is on record for Browserbase. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/browserbase-com/index.md) ## Sources - [Ora score page for browserbase.com](https://ora.ai/score/browserbase.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/leaderboard) - [Where Browserbase was found](https://docs.browserbase.com/integrations/mcp/introduction), read 4 November 2026 - [Browserbase website](https://browserbase.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Browserbook MCP server | Agent MCP Directory" description: "Does Browserbook have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/browserbook-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Browserbook MCP server | Agent MCP Directory > Does Browserbook have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/browserbook-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Browserbook: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Browserbook (browserbook.com), so the connector had nothing to connect to. Ora's cached score for browserbook.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Browserbook (registry title: browserbook.com) | | --- | --- | | Domain | browserbook.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for browserbook.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Browserbook. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for browserbook.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Browserbook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/browserbook-com/index.md) ## Sources - [Ora score page for browserbook.com](https://ora.ai/score/browserbook.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/leaderboard) - [Where Browserbook was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Browserbook website](https://browserbook.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Browserless MCP server | Agent MCP Directory" description: "Browserless: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/browserless-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Browserless MCP server | Agent MCP Directory > Browserless: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/browserless-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Browserless: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Browserless at mcp.browserless.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Browserless | | --- | --- | | Domain | browserless.io | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 83, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for browserless.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.browserless.io/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,445 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:47Z https://mcp.browserless.io/mcp sent initialize result auth-required (HTTP 401) 1593 ms - 20:02:18Z https://mcp.browserless.io/mcp sent initialize result auth-required (HTTP 401) 1445 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.browserless.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="No Browserless API token provided. Pass it as Authorization: Bearer header, ?token= query parameter, or authenticate via OAuth." | | Protected resource metadata | mcp.browserless.io | | Authorization server metadata | mcp.browserless.io | | Registration endpoint | https://mcp.browserless.io/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.browserless.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.browserless.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.browserless.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Browserless. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: browserless.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.browserless/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/browserless-io/index.md) ## Sources - [Ora score page for browserless.io](https://ora.ai/score/browserless.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Browserless was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.browserless%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=browserless), read 4 November 2026 - [Browserless website](https://browserless.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Browserstack MCP server | Agent MCP Directory" description: "Browserstack: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/browserstack-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Browserstack MCP server | Agent MCP Directory > Browserstack: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/browserstack-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Browserstack: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Browserstack at mcp.browserstack.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Browserstack | | --- | --- | | Domain | browserstack.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 9,719 on the list of 4 November 2026 | | Ora score | 60, grade C; Ora scanned the domain on 12 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for browserstack.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.browserstack.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,152 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:15Z https://mcp.browserstack.com/mcp sent initialize result auth-required (HTTP 401) 1192 ms - 20:01:54Z https://mcp.browserstack.com/mcp sent initialize result auth-required (HTTP 401) 1152 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://mcp.browserstack.com/mcp", resource_metadata="https://mcp.browserstack.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.browserstack.com | | Authorization server metadata | mcp.browserstack.com | | Registration endpoint | https://mcp.browserstack.com/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.browserstack.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.browserstack.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.browserstack.com/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Browserstack. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: browserstack.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/browserstack-com/index.md) ## Sources - [Ora score page for browserstack.com](https://ora.ai/score/browserstack.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 October 2026, read from GET /api/score) - [Where Browserstack was found](https://github.com/mcp/browserstack/mcp-server), read 4 November 2026 - [Browserstack website](https://browserstack.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bubble MCP server | Agent MCP Directory" description: "Bubble: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bubble-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bubble MCP server | Agent MCP Directory > Bubble: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/bubble-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bubble: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Bubble; the connector's guess at mcp.bubble.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Bubble (registry title: bubble.io) | | --- | --- | | Domain | bubble.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 40, grade D; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bubble.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bubble.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 747 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:46Z https://mcp.bubble.io/mcp sent initialize result auth-required (HTTP 401) 816 ms - 20:02:18Z https://mcp.bubble.io/mcp sent initialize result auth-required (HTTP 401) 747 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", scope="apps:create apps:list app:code:read app:code:write app:test:logs app:live:logs app:plugins:install app:test:db:read app:test:db:write app:test:run-as app:live:db:read app:branch:create app:branch:manage", resource_metadata="https://mcp.bubble.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.bubble.io | | Authorization server metadata | bubble.io | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.bubble.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.bubble.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bubble. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: bubble.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bubble-io/index.md) ## Sources - [Ora score page for bubble.io](https://ora.ai/score/bubble.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where Bubble was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bubble website](https://bubble.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bucket MCP server | Agent MCP Directory" description: "Does Bucket have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bucket-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bucket MCP server | Agent MCP Directory > Does Bucket have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/bucket-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bucket: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Bucket (bucket.co), so the connector had nothing to connect to. Ora's cached score for bucket.co is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Bucket (registry title: bucket.co) | | --- | --- | | Domain | bucket.co | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 18 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bucket.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Bucket. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bucket.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Bucket. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bucket-co/index.md) ## Sources - [Ora score page for bucket.co](https://ora.ai/score/bucket.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 April 2026, read from GET /api/leaderboard) - [Where Bucket was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bucket website](https://bucket.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bugasura MCP server | Agent MCP Directory" description: "Bugasura: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/bugasura-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bugasura MCP server | Agent MCP Directory > Bugasura: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/bugasura-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bugasura: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Bugasura at mcp.bugasura.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Bugasura | | --- | --- | | Domain | bugasura.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 42, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for bugasura.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bugasura.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,515 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:47Z https://mcp.bugasura.io/mcp sent initialize result auth-required (HTTP 401) 1617 ms - 20:02:19Z https://mcp.bugasura.io/mcp sent initialize result auth-required (HTTP 401) 1515 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer scope="api", resource_metadata="https://mcp.bugasura.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.bugasura.io | | Authorization server metadata | mcp.bugasura.io | | Registration endpoint | https://mcp.bugasura.io/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.bugasura.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.bugasura.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.bugasura.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Bugasura. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.bugasura/bugasura | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bugasura-io/index.md) ## Sources - [Ora score page for bugasura.io](https://ora.ai/score/bugasura.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=bugasura), read 4 November 2026 - [Bugasura website](https://bugasura.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BugSnag MCP server | Agent MCP Directory" description: "Does BugSnag have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/bugsnag-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BugSnag MCP server | Agent MCP Directory > Does BugSnag have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/bugsnag-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # BugSnag: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for BugSnag (bugsnag.com), so the connector had nothing to connect to. Ora's cached score for bugsnag.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | BugSnag (registry title: bugsnag.com) | | --- | --- | | Domain | bugsnag.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 724 on the list of 4 November 2026 | | Ora score | 52, grade C; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for bugsnag.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for BugSnag. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bugsnag.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for BugSnag. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bugsnag-com/index.md) ## Sources - [Ora score page for bugsnag.com](https://ora.ai/score/bugsnag.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Where BugSnag was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [BugSnag website](https://bugsnag.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BuildBuddy MCP server | Agent MCP Directory" description: "Does BuildBuddy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/buildbuddy-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BuildBuddy MCP server | Agent MCP Directory > Does BuildBuddy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/buildbuddy-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # BuildBuddy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for BuildBuddy (buildbuddy.io), so the connector had nothing to connect to. Ora's cached score for buildbuddy.io is 44, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | BuildBuddy (registry title: buildbuddy.io) | | --- | --- | | Domain | buildbuddy.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 44, grade D; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for buildbuddy.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for BuildBuddy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for buildbuddy.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for BuildBuddy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/buildbuddy-io/index.md) ## Sources - [Ora score page for buildbuddy.io](https://ora.ai/score/buildbuddy.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/leaderboard) - [Where BuildBuddy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [BuildBuddy website](https://buildbuddy.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Builder.io MCP server | Agent MCP Directory" description: "Does Builder.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/builder-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Builder.io MCP server | Agent MCP Directory > Does Builder.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/builder-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Builder.io: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Builder.io (builder.io), so the connector had nothing to connect to. Ora's cached score for builder.io is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Builder.io | | --- | --- | | Domain | builder.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for builder.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Builder.io. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for builder.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Builder.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: builder.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/builder-io/index.md) ## Sources - [Ora score page for builder.io](https://ora.ai/score/builder.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where Builder.io was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Builder.io website](https://builder.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BuildJet MCP server | Agent MCP Directory" description: "Does BuildJet have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/buildjet-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BuildJet MCP server | Agent MCP Directory > Does BuildJet have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/buildjet-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # BuildJet: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for BuildJet (buildjet.com), so the connector had nothing to connect to. Ora's cached score for buildjet.com is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | BuildJet (registry title: buildjet.com) | | --- | --- | | Domain | buildjet.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for buildjet.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for BuildJet. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for buildjet.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for BuildJet. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/buildjet-com/index.md) ## Sources - [Ora score page for buildjet.com](https://ora.ai/score/buildjet.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/leaderboard) - [Where BuildJet was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [BuildJet website](https://buildjet.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Buildkite MCP server | Agent MCP Directory" description: "Buildkite: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/buildkite-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Buildkite MCP server | Agent MCP Directory > Buildkite: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/buildkite-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Buildkite: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Buildkite at mcp.buildkite.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Buildkite | | --- | --- | | Domain | buildkite.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for buildkite.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.buildkite.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 778 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:47Z https://mcp.buildkite.com/mcp sent initialize result auth-required (HTTP 401) 796 ms - 20:02:19Z https://mcp.buildkite.com/mcp sent initialize result auth-required (HTTP 401) 778 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://mcp.buildkite.com", error="access_denied", error_description="Authentication required", resource_metadata="https://mcp.buildkite.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.buildkite.com | | Authorization server metadata | mcp.buildkite.com | | Registration endpoint | https://mcp.buildkite.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.buildkite.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.buildkite.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.buildkite.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Buildkite. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/buildkite-com/index.md) ## Sources - [Ora score page for buildkite.com](https://ora.ai/score/buildkite.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/leaderboard) - [Where Buildkite was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Buildkite website](https://buildkite.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Buildwithglide MCP server | Agent MCP Directory" description: "Does Buildwithglide have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/buildwithglide-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Buildwithglide MCP server | Agent MCP Directory > Does Buildwithglide have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/buildwithglide-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Buildwithglide: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Buildwithglide (buildwithglide.com), so the connector had nothing to connect to. Ora's cached score for buildwithglide.com is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Buildwithglide (registry title: buildwithglide.com) | | --- | --- | | Domain | buildwithglide.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 24 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for buildwithglide.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Buildwithglide. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for buildwithglide.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Buildwithglide. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/buildwithglide-com/index.md) ## Sources - [Ora score page for buildwithglide.com](https://ora.ai/score/buildwithglide.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 September 2026, read from GET /api/leaderboard) - [Where Buildwithglide was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Buildwithglide website](https://buildwithglide.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BulkPublish MCP server | Agent MCP Directory" description: "BulkPublish: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/bulkpublish-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BulkPublish MCP server | Agent MCP Directory > BulkPublish: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/bulkpublish-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # BulkPublish: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for BulkPublish at mcp.bulkpublish.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | BulkPublish | | --- | --- | | Domain | bulkpublish.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 73, grade B; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for bulkpublish.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.bulkpublish.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 767 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:48Z https://mcp.bulkpublish.com/mcp sent initialize result auth-required (HTTP 401) 951 ms - 20:02:19Z https://mcp.bulkpublish.com/mcp sent initialize result auth-required (HTTP 401) 767 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.bulkpublish.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.bulkpublish.com | | Authorization server metadata | mcp.bulkpublish.com | | Registration endpoint | https://mcp.bulkpublish.com/register | ### The sign-in route, step by step 1. Request `https://mcp.bulkpublish.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.bulkpublish.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.bulkpublish.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BulkPublish. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bulkpublish-com/index.md) ## Sources - [Ora score page for bulkpublish.com](https://ora.ai/score/bulkpublish.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [BulkPublish website](https://bulkpublish.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Bun MCP server | Agent MCP Directory" description: "Does Bun have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/bun-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Bun MCP server | Agent MCP Directory > Does Bun have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/bun-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Bun: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Bun (bun.sh), so the connector had nothing to connect to. Ora's cached score for bun.sh is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Bun | | --- | --- | | Domain | bun.sh | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for bun.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Bun. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for bun.sh, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Bun. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/bun-sh/index.md) ## Sources - [Ora score page for bun.sh](https://ora.ai/score/bun.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/leaderboard) - [Where Bun was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Bun website](https://bun.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "BuyWhere MCP server | Agent MCP Directory" description: "BuyWhere has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/buywhere-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # BuyWhere MCP server | Agent MCP Directory > BuyWhere has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/buywhere-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # BuyWhere: MCP server, CLI and agent surfaces Yes: BuyWhere runs a public MCP server at api.buywhere.ai that listed 13 tools to a client with no credentials on 4 November 2026. Examples: search\_products, get\_product, compare\_products. It speaks streamable-http, protocol 2024-11-05. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | BuyWhere | | --- | --- | | Domain | buywhere.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for buywhere.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.buywhere.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | buywhere-catalog 1.0.0 | | Capabilities | tools | | Tools | 13 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,175 ms over 1 attempt | ### Tools listed 13 tools - search\_products - get\_product - compare\_products - get\_deals - list\_categories - find\_best\_price - find\_similar - ingest\_products - search\_products\_v2 - get\_product\_v2 - compare\_products\_v2 - get\_deals\_v2 - find\_best\_price\_v2 ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:48Z https://api.buywhere.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1278 ms - 20:02:20Z https://api.buywhere.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1175 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.buywhere.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for BuyWhere. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: api.buywhere.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/buywhere-ai/index.md) ## Sources - [Where BuyWhere was found](https://github.com/mcp/BuyWhere/buywhere-mcp), read 4 November 2026 - [BuyWhere website](https://buywhere.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Calendly MCP server | Agent MCP Directory" description: "Calendly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/calendly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Calendly MCP server | Agent MCP Directory > Calendly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/calendly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Calendly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Calendly at mcp.calendly.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Calendly | | --- | --- | | Domain | calendly.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 416 on the list of 4 November 2026 | | Ora score | 78, grade B; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for calendly.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.calendly.com | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 563 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://mcp.calendly.com sent initialize result auth-required (HTTP 401) 577 ms - 20:01:29Z https://mcp.calendly.com sent initialize result auth-required (HTTP 401) 563 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.calendly.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.calendly.com | | Authorization server metadata | calendly.com | | Registration endpoint | https://calendly.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.calendly.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.calendly.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://calendly.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Calendly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: calendly.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/calendly-com/index.md) ## Sources - [Ora score page for calendly.com](https://ora.ai/score/calendly.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/score) - [Where Calendly was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Calendly website](https://calendly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "call4me MCP server | Agent MCP Directory" description: "call4me: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/call4-me site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # call4me MCP server | Agent MCP Directory > call4me: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/call4-me Site: Agent MCP Directory Last reviewed: 2026-11-05 # call4me: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for call4me at call4.me answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | call4me | | --- | --- | | Domain | call4.me | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for call4.me when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://call4.me/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,929 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:49Z https://call4.me/mcp sent initialize result auth-required (HTTP 401) 2045 ms - 20:02:21Z https://call4.me/mcp sent initialize result auth-required (HTTP 401) 1929 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://call4.me/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | call4.me | | Authorization server metadata | call4.me | | Registration endpoint | https://call4.me/api/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://call4.me/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://call4.me/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://call4.me/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for call4me. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: call4.me (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/call4-me/index.md) ## Sources - [Where call4me was found](https://github.com/mcp/skeptrunedev/call4me), read 4 November 2026 - [call4me website](https://call4.me), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Canva MCP server | Agent MCP Directory" description: "Canva: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/canva-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Canva MCP server | Agent MCP Directory > Canva: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/canva-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Canva: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Canva at mcp.canva.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Canva | | --- | --- | | Domain | canva.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 284 on the list of 4 November 2026 | | Ora score | 42, grade D; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for canva.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.canva.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 99 ms over 1 attempt | | Documentation | www.canva.dev | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:52Z https://mcp.canva.com/mcp sent initialize result auth-required (HTTP 401) 93 ms - 20:01:28Z https://mcp.canva.com/mcp sent initialize result auth-required (HTTP 401) 99 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.canva.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.canva.com | | Authorization server metadata | mcp.canva.com | | Registration endpoint | https://mcp.canva.com/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.canva.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.canva.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.canva.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @canva/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 2.17.0 | | Last publish | 2 November 2026 | | Command names | canva | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: canva.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.canva.mcp/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/canva-com/index.md) ## Sources - [Ora score page for canva.com](https://ora.ai/score/canva.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=canva), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Capacities MCP server | Agent MCP Directory" description: "Capacities: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/capacities-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Capacities MCP server | Agent MCP Directory > Capacities: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/capacities-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Capacities: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Capacities at api.capacities.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Capacities | | --- | --- | | Domain | capacities.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 78, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for capacities.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.capacities.io/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 3,778 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:49Z https://api.capacities.io/mcp sent initialize result auth-required (HTTP 401) 1496 ms - 20:02:23Z https://api.capacities.io/mcp sent initialize result auth-required (HTTP 401) 3778 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.capacities.io/.well-known/oauth-protected-resource/mcp", scope="mcp:read mcp:write" | | Protected resource metadata | api.capacities.io | | Authorization server metadata | api.capacities.io | | Registration endpoint | https://api.capacities.io/oauth/reg | ### The sign-in route, step by step 1. Request `https://api.capacities.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.capacities.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.capacities.io/oauth/reg` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Capacities. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.capacities/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/capacities-io/index.md) ## Sources - [Ora score page for capacities.io](https://ora.ai/score/capacities.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Capacities was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.capacities%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=capacities), read 4 November 2026 - [Capacities website](https://capacities.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Carrd MCP server | Agent MCP Directory" description: "Does Carrd have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/carrd-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Carrd MCP server | Agent MCP Directory > Does Carrd have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/carrd-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Carrd: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Carrd (carrd.co), so the connector had nothing to connect to. Ora's cached score for carrd.co is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Carrd (registry title: carrd.co) | | --- | --- | | Domain | carrd.co | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 4,599 on the list of 4 November 2026 | | Ora score | 42, grade D; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for carrd.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Carrd. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for carrd.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Carrd. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/carrd-co/index.md) ## Sources - [Ora score page for carrd.co](https://ora.ai/score/carrd.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/score) - [Where Carrd was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Carrd website](https://carrd.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Carrick MCP server | Agent MCP Directory" description: "Carrick: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/carrick-tools site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Carrick MCP server | Agent MCP Directory > Carrick: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/carrick-tools Site: Agent MCP Directory Last reviewed: 2026-11-05 # Carrick: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Carrick at api.carrick.tools answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Carrick | | --- | --- | | Domain | carrick.tools | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for carrick.tools when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.carrick.tools/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 856 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:49Z https://api.carrick.tools/mcp sent initialize result auth-required (HTTP 401) 1268 ms - 20:02:20Z https://api.carrick.tools/mcp sent initialize result auth-required (HTTP 401) 856 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="carrick", error="missing_token", error_description="Bearer token required", resource_metadata="https://app.carrick.tools/.well-known/oauth-protected-resource" | | Protected resource metadata | app.carrick.tools | | Authorization server metadata | app.carrick.tools | | Registration endpoint | https://app.carrick.tools/oauth/register | ### The sign-in route, step by step 1. Request `https://api.carrick.tools/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.carrick.tools/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.carrick.tools/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Carrick. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/carrick-tools/index.md) ## Sources - [Where Carrick was found](https://github.com/mcp/carrick-tools/carrick), read 4 November 2026 - [Carrick website](https://carrick.tools), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Casco MCP server | Agent MCP Directory" description: "Casco has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/casco-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Casco MCP server | Agent MCP Directory > Casco has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/casco-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Casco: MCP server, CLI and agent surfaces Yes: Casco runs a public MCP server at casco.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: get\_cve, check\_dependencies, list\_cve\_updates. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for casco.com is 41, grade D, read on 5 November 2026. ## Fact sheet | Company | Casco (registry title: CVE Intelligence by Casco) | | --- | --- | | Domain | casco.com | | Category | Security (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 41, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for casco.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://casco.com/cve/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | com.casco/cve-intelligence 1.0.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,063 ms over 1 attempt | ### Tools listed 4 tools - get\_cve - check\_dependencies - list\_cve\_updates - list\_ecosystems ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:49Z https://casco.com/cve/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1181 ms - 20:02:20Z https://casco.com/cve/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1063 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://casco.com/cve/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Casco. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.casco/cve-intelligence | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/casco-com/index.md) ## Sources - [Ora score page for casco.com](https://ora.ai/score/casco.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Where Casco was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.casco%2Fcve-intelligence), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=casco), read 4 November 2026 - [Casco website](https://casco.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Castari MCP server | Agent MCP Directory" description: "Does Castari have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/castari-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Castari MCP server | Agent MCP Directory > Does Castari have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/castari-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Castari: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Castari (castari.com), so the connector had nothing to connect to. Ora's cached score for castari.com is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Castari (registry title: castari.com) | | --- | --- | | Domain | castari.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for castari.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Castari. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for castari.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Castari. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/castari-com/index.md) ## Sources - [Ora score page for castari.com](https://ora.ai/score/castari.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Castari was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Castari website](https://castari.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Catalystproject MCP server | Agent MCP Directory" description: "Catalystproject has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/catalystproject-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Catalystproject MCP server | Agent MCP Directory > Catalystproject has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/catalystproject-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Catalystproject: MCP server, CLI and agent surfaces Yes: Catalystproject runs a public MCP server at catalystproject.ai that listed 7 tools to a client with no credentials on 4 November 2026. Examples: find\_evidence, search\_nodes, get\_findings. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Catalystproject (registry title: Catalyst evidence graph) | | --- | --- | | Domain | catalystproject.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for catalystproject.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://catalystproject.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | catalyst-evidence-graph 0.2.0 | | Capabilities | tools, resources, prompts | | Tools | 7 | | Resources | 2 | | Prompts | 1 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,015 ms over 1 attempt | ### Tools listed 7 tools - find\_evidence - search\_nodes - get\_findings - get\_finding - get\_relations - get\_reactions - reach ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:50Z https://catalystproject.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1911 ms - 20:02:22Z https://catalystproject.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2015 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://catalystproject.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Catalystproject. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.catalystproject/evidence-graph | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/catalystproject-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=catalystproject), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Agent Tools: MCP servers and CLIs | Agent MCP Directory" description: "Agent Tools: 74 companies, 27 with tools listed and 2 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/agent-tools site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Agent Tools: MCP servers and CLIs | Agent MCP Directory > Agent Tools: 74 companies, 27 with tools listed and 2 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/agent-tools Site: Agent MCP Directory Last reviewed: 2026-11-05 # Agent Tools: MCP servers and CLIs 74 companies in Agent Tools: 27 listed tools to a client with no credentials, 38 answered with a sign-in challenge (not counted) and 2 have a CLI on record. Rows run from AgenticWebScore to Zentrik. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | AgenticWebScore agenticwebscore.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Airport Lounge List airportloungelist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AlfaNest alfanestlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Amplify amplify.is | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Antevo antevo.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Apex AI Academy apexai.academy | Verified no auth | – | | – | not read | 2026-11-04 | | Apify apify.com | Sign-in required OAuth DCR; tools not seen, not counted | apify-cli | 96 A+ | yes | no | 2026-11-04 | | APITube apitube.io | Verified no auth | – | | – | not read | 2026-11-04 | | Atom.com atom.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Audioscrape audioscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Award Travel Finder awardtravelfinder.com | No tools listed | – | | – | not read | 2026-11-04 | | Bibooks bibooks.org | Verified no auth | – | | – | not read | 2026-11-04 | | BreckenWander breckenwander.com | Verified no auth | – | | – | not read | 2026-11-04 | | Browser Use browser-use.com | Verified no auth | – | 91 A | yes | no | 2026-11-04 | | Browserbase browserbase.com | None found | – | 84 B | – | no | 2026-11-04 | | Browserless browserless.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | yes | 2026-11-04 | | Causely causely.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | COLA Cloud colacloud.us | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Composio composio.dev | None found | composio | 83 B | – | no | 2026-11-04 | | Connie connie.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Context7 context7.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | | Conveo conveo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Dabloons dabloons.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Edgaze edgaze.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Editalmd editalmd.com | Verified no auth | – | | yes | not read | 2026-11-04 | | ElevenLabs elevenlabs.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Epinu epinu.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Exa exa.ai | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Firmament getfirmament.com | No answer | – | | – | not read | 2026-11-04 | | Fuentio fuentio.com | Verified no auth | – | | – | not read | 2026-11-04 | | Gamedev gamedev.pl | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Greca House grecahouse.com | Verified no auth | – | | – | not read | 2026-11-04 | | Hydrant hydrant.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Icons8 icons8.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | imzala.net imzala.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Keenable keenable.ai | Verified no auth | – | 68 C | yes | not read | 2026-11-04 | | Kin kinlab.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Klavis klavis.ai | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Lucid lucid.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mediawork mediawork.io | Verified no auth | – | | – | not read | 2026-11-04 | | MiningBridge miningbridge.in | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mobbin mobbin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | not read | 2026-11-04 | | Nameshift nameshift.com | No answer | – | | – | no | 2026-11-04 | | Neuronto neuronto.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Noonlaunch noonlaunch.com | Verified no auth | – | 61 C | yes | not read | 2026-11-04 | | Oids tryoids.com | Credential wall API key | – | | – | not read | 2026-11-04 | | Okfindex okfindex.com | Verified no auth | – | | yes | not read | 2026-11-04 | | OneSchema oneschema.co | Credential wall API key | – | 56 C | – | no | 2026-11-04 | | Ora ora.ai | Verified no auth | – | 95 A+ | yes | yes | 2026-11-04 | | OrgGen AI orggen.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | OwlCAD owlcad.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Parallel parallel.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Peek.com peek.com | Verified no auth | – | 39 D | – | not read | 2026-11-04 | | Posteverywhere posteverywhere.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | – | not read | 2026-11-04 | | Ptpge ptpge.org | Verified no auth | – | | – | not read | 2026-11-04 | | ResumeQuick resumequick.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sadiqoon sadiqoon.uk | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ScreensDesign screensdesign.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | SearchAPI searchapi.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | Simplescraper simplescraper.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sitepulsar sitepulsar.ai | Verified no auth | – | | yes | not read | 2026-11-04 | | SmartGate smartgate.network | Credential wall API key | – | | – | not read | 2026-11-04 | | Sofya sofya.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Studiomeyer studiomeyer.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | yes | not read | 2026-11-04 | | Sugra sugra.ai | Verified no auth | – | 49 C | – | not read | 2026-11-04 | | TableJourney tablejourney.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Taskfolk taskfolk.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Terminal Tax terminal.tax | Verified no auth | – | | – | not read | 2026-11-04 | | There's An AI For That theresanaiforthat.com | Verified no auth | – | 9 F | – | not read | 2026-11-04 | | Traveler.md traveler.md | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | yes | not read | 2026-11-04 | | Unblocked getunblocked.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Unlimitless unlimitless.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | UX Pilot uxpilot.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | not read | 2026-11-04 | | Zentrik zentrik.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/agent-tools/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "AI & ML: MCP servers and CLIs | Agent MCP Directory" description: "AI & ML: 36 companies, 9 with tools listed and 5 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/ai-and-ml site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # AI & ML: MCP servers and CLIs | Agent MCP Directory > AI & ML: 36 companies, 9 with tools listed and 5 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/ai-and-ml Site: Agent MCP Directory Last reviewed: 2026-11-05 # AI & ML: MCP servers and CLIs 36 companies in AI & ML: 9 listed tools to a client with no credentials, 22 answered with a sign-in challenge (not counted) and 5 have a CLI on record. Rows run from 1102tools to Zine. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 1102tools 1102tools.com | Verified no auth | – | | – | not read | 2026-11-04 | | Anthropic anthropic.com | None found | @anthropic-ai/claude-code | 71 B | – | no | 2026-11-04 | | Antwork antwork.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | yes | not read | 2026-11-04 | | Clueso clueso.io | Verified no auth | – | 78 B | – | no | 2026-11-04 | | Desktopcommander desktopcommander.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Floot floot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Glean glean.com | None found | – | 72 B | – | no | 2026-11-04 | | Glif glif.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | yes | no | 2026-11-04 | | Google Gemini gemini.google.com | None found | @google/gemini-cli | 43 D | – | not read | 2026-11-04 | | Hugging Face huggingface.co | Verified no auth | huggingface_hub | 82 B | – | no | 2026-11-04 | | HypAware hypaware.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kodza kodza.dev | Verified no auth | – | | – | not read | 2026-11-04 | | LFG lfg.gm | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Locus paywithlocus.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | yes | no | 2026-11-04 | | mabl mabl.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Modal modal.com | None found | modal | 63 C | – | no | 2026-11-04 | | NVIDIA nvidia.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | OpenAI openai.com | None found | @openai/codex | 58 C | yes | no | 2026-11-04 | | Perspective AI getperspective.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | not read | 2026-11-04 | | Powmcp powmcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Predictionmarketspicks predictionmarketspicks.com | Verified no auth | – | | – | not read | 2026-11-04 | | Prominara prominara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | RegAI regai.tw | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Reka reka.ai | Verified no auth | – | 77 B | – | no | 2026-11-04 | | ReputeMap reputemap.com | Verified no auth | – | | – | not read | 2026-11-04 | | Roboflow roboflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Scripe scripe.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | SentinelX sentinelx.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Speakeroo speakeroo.app | Verified no auth | – | 73 B | – | not read | 2026-11-04 | | Startup Ignition startupignition.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Truthifi truthifi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Unstructured unstructured.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Versive getversive.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | Vooban vooban.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Webhound webhound.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | Zine zine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/ai-and-ml/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Climate & Energy: MCP servers and CLIs | Agent MCP Directory" description: "Climate & Energy: 1 company, 0 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/climate-and-energy site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Climate & Energy: MCP servers and CLIs | Agent MCP Directory > Climate & Energy: 1 company, 0 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/climate-and-energy Site: Agent MCP Directory Last reviewed: 2026-11-05 # Climate & Energy: MCP servers and CLIs 1 company in Climate & Energy: 0 listed tools to a client with no credentials, 1 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Precip to Precip. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Precip precip.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/climate-and-energy/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Commerce Tools: MCP servers and CLIs | Agent MCP Directory" description: "Commerce Tools: 6 companies, 0 with tools listed and 3 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/commerce-tools site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Commerce Tools: MCP servers and CLIs | Agent MCP Directory > Commerce Tools: 6 companies, 0 with tools listed and 3 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/commerce-tools Site: Agent MCP Directory Last reviewed: 2026-11-05 # Commerce Tools: MCP servers and CLIs 6 companies in Commerce Tools: 0 listed tools to a client with no credentials, 4 answered with a sign-in challenge (not counted) and 3 have a CLI on record. Rows run from Gumroad to Wix. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Gumroad gumroad.com | None found | – | 69 C | – | no | 2026-11-04 | | Medusa medusajs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Sellfy sellfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Shopify shopify.com | None found | @shopify/cli | 72 B | – | no | 2026-11-04 | | Webflow webflow.com | Sign-in required OAuth DCR; tools not seen, not counted | @webflow/webflow-cli | 78 B | – | not read | 2026-11-04 | | Wix wix.com | Sign-in required OAuth DCR; tools not seen, not counted | @wix/cli | 64 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/commerce-tools/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Communication & Support: MCP servers and CLIs | Agent MCP Directory" description: "Communication & Support: 35 companies, 14 with tools listed and 1 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/communication-and-support site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Communication & Support: MCP servers and CLIs | Agent MCP Directory > Communication & Support: 35 companies, 14 with tools listed and 1 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/communication-and-support Site: Agent MCP Directory Last reviewed: 2026-11-05 # Communication & Support: MCP servers and CLIs 35 companies in Communication & Support: 14 listed tools to a client with no credentials, 19 answered with a sign-in challenge (not counted) and 1 have a CLI on record. Rows run from Adlicio to Zoom. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Adlicio tryadlicio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | yes | not read | 2026-11-04 | | AgentBIT agentbit.app | Verified no auth | – | | yes | not read | 2026-11-04 | | AIS Trail aistrail.com | Verified no auth | – | | – | not read | 2026-11-04 | | Bitmovin bitmovin.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | Chatfuel chatfuel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | no | 2026-11-04 | | Clera getclera.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | Crakseo crakseo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | DeskCrew deskcrew.io | None found | – | | yes | not read | 2026-11-04 | | DialMCP dialmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Draw draw.io | Verified no auth | – | 13 F | – | not read | 2026-11-04 | | Evermuse evermuse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Example4 example4.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Faxette faxette.com | Verified no auth | – | | – | not read | 2026-11-04 | | Huddo huddo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Intercom intercom.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | Invokary invokary.com | Verified no auth | – | | – | not read | 2026-11-04 | | Letterly letterly.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Local MCP local-mcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Localcmd localcmd.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ludo AI ludo.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Mailbuttons mailbuttons.com | Verified no auth | – | | – | not read | 2026-11-04 | | Memxus memxus.com | Verified no auth | – | | – | not read | 2026-11-04 | | Minds getminds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Pingram pingram.io | None found | – | 88 A | – | not read | 2026-11-04 | | Postel postel.app | Verified no auth | – | | – | not read | 2026-11-04 | | Rulebase rulebase.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Salvy salvy.com.br | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Slack slack.com | Sign-in required OAuth; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | SRIFT srift.app | Verified no auth | – | | yes | not read | 2026-11-04 | | Studio99 studio99.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Turbo Notify turbonotify.com | Verified no auth | – | | – | not read | 2026-11-04 | | Twilio twilio.com | Verified no auth | twilio-cli | 85 B | – | no | 2026-11-04 | | VibeSEO vibeseo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vidova vidova.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | Zoom zoom.us | Sign-in required OAuth; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/communication-and-support/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Consumer: MCP servers and CLIs | Agent MCP Directory" description: "Consumer: 1 company, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/consumer site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Consumer: MCP servers and CLIs | Agent MCP Directory > Consumer: 1 company, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/consumer Site: Agent MCP Directory Last reviewed: 2026-11-05 # Consumer: MCP servers and CLIs 1 company in Consumer: 1 listed tools to a client with no credentials, 0 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Allbirds to Allbirds. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Allbirds allbirds.com | Verified no auth | – | 65 C | – | yes | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/consumer/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "CRM: MCP servers and CLIs | Agent MCP Directory" description: "CRM: 19 companies, 5 with tools listed and 2 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/crm site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # CRM: MCP servers and CLIs | Agent MCP Directory > CRM: 19 companies, 5 with tools listed and 2 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/crm Site: Agent MCP Directory Last reviewed: 2026-11-05 # CRM: MCP servers and CLIs 19 companies in CRM: 5 listed tools to a client with no credentials, 12 answered with a sign-in challenge (not counted) and 2 have a CLI on record. Rows run from Account Executive Jobs to Ziptax. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Account Executive Jobs accountexecutivejobs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Apollo.io apollo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Attio attio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Cavyro cavyro.com | Credential wall API key | – | 73 B | yes | not read | 2026-11-04 | | Close close.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Dm dm.de | Verified no auth | – | 51 C | – | no | 2026-11-04 | | Elfsight AI elfsight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | HubSpot hubspot.com | Sign-in required OAuth; tools not seen, not counted | @hubspot/cli | 72 B | – | no | 2026-11-04 | | Layrcake layrcake.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Leadbase leadbase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LiveCRM livecrm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Nimble nimble.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Pageree pageree.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Salesforce salesforce.com | None found | @salesforce/cli | 51 C | – | no | 2026-11-04 | | Seller Profit Doctor sellerprofitdoctor.com | Verified no auth | – | | – | not read | 2026-11-04 | | Twelfth twelfth.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | yes | not read | 2026-11-04 | | WebinarIgnition webinarignition.com | Verified no auth | – | | – | not read | 2026-11-04 | | YouSpot youspot.com | Verified no auth | – | 98 A+ | yes | yes | 2026-11-04 | | Ziptax zip.tax | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/crm/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Data & Analytics: MCP servers and CLIs | Agent MCP Directory" description: "Data & Analytics: 39 companies, 8 with tools listed and 1 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/data-and-analytics site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Data & Analytics: MCP servers and CLIs | Agent MCP Directory > Data & Analytics: 39 companies, 8 with tools listed and 1 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/data-and-analytics Site: Agent MCP Directory Last reviewed: 2026-11-05 # Data & Analytics: MCP servers and CLIs 39 companies in Data & Analytics: 8 listed tools to a client with no credentials, 28 answered with a sign-in challenge (not counted) and 1 have a CLI on record. Rows run from 0xArchive to Whalesync. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 0xArchive 0xarchive.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 94 A | yes | not read | 2026-11-04 | | Airbyte airbyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Aiven aiven.io | None found | – | 76 B | – | no | 2026-11-04 | | Alchemy alchemy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Amplitude amplitude.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | yes | no | 2026-11-04 | | AnomalyArmor anomalyarmor.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | yes | no | 2026-11-04 | | Basedash basedash.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Bigdata.com bigdata.com | Sign-in required OAuth; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | Clicon clicon.app | No answer | – | | – | not read | 2026-11-04 | | DC Hub dchub.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | DocNexus docnexus.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Explorium explorium.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Firmafakta firmafakta.se | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Hitsteps hitsteps.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Jitsu jitsu.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | no | 2026-11-04 | | Measuremy measuremy.site | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mirabelloconsultancy mirabelloconsultancy.com | Verified no auth | – | | – | not read | 2026-11-04 | | NewsCatcher newscatcherapi.com | Verified no auth | – | 63 C | – | no | 2026-11-04 | | Nitrosend nitrosend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | | Novadata novadata.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | NUM itsnum.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Outset outset.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | Parse.ly parsely.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Pixelesq pixelesq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | not read | 2026-11-04 | | PostHog posthog.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | PredictLeads predictleads.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | Rampify rampify.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Redpanda redpanda.com | Verified no auth | – | 68 C | – | no | 2026-11-04 | | SearchConsole.ai searchconsole.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Searcherries searcherries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shortimize shortimize.com | Verified no auth | – | | – | not read | 2026-11-04 | | ShortSync shortsync.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sisense sisense.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Snowflake snowflake.com | None found | snowflake-cli | 66 C | – | no | 2026-11-04 | | Sociality.io sociality.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | Techfabric techfabric.com | Verified no auth | – | | – | not read | 2026-11-04 | | ThoughtSpot thoughtspot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | Web3Juice web3juice.com | Verified no auth | – | | – | not read | 2026-11-04 | | Whalesync whalesync.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/data-and-analytics/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Developer Tools: MCP servers and CLIs | Agent MCP Directory" description: "Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/developer-tools site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Developer Tools: MCP servers and CLIs | Agent MCP Directory > Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/developer-tools Site: Agent MCP Directory Last reviewed: 2026-11-05 # Developer Tools: MCP servers and CLIs 450 companies in Developer Tools: 41 listed tools to a client with no credentials, 96 answered with a sign-in challenge (not counted) and 8 have a CLI on record. This page lists rows 1 to 100, from 3Dsellers to Dailybot. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 3Dsellers 3dsellers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | a0.dev a0.dev | None found | – | 51 C | – | no | 2026-11-04 | | Aaly aaly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Abstra abstra.io | No answer | – | 55 C | – | no | 2026-11-04 | | Actual AI actual.ai | None found | – | 81 B | yes | no | 2026-11-04 | | Aden adenhq.com | None found | – | 70 B | – | no | 2026-11-04 | | AgentData agentdata.run | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | aictrl aictrl.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Aider aider.chat | None found | – | 41 D | – | no | 2026-11-04 | | Anchore anchore.com | None found | – | 46 D | – | no | 2026-11-04 | | Andi andiai.com | Sign-in required OAuth; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Anima animaapp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Any.do any.do | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | yes | no | 2026-11-04 | | Anytype anytype.io | None found | – | 40 D | – | no | 2026-11-04 | | AppVeyor appveyor.com | None found | – | 40 D | – | no | 2026-11-04 | | Ara ara.so | None found | – | 53 C | – | no | 2026-11-04 | | Archbee archbee.com | None found | – | 63 C | – | no | 2026-11-04 | | Archil archil.com | None found | – | 62 C | – | no | 2026-11-04 | | Arga Labs argalabs.com | None found | – | 65 C | – | no | 2026-11-04 | | Artie artie.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Artillery artillery.io | None found | – | 55 C | – | no | 2026-11-04 | | Assembla assembla.com | None found | – | 52 C | – | no | 2026-11-04 | | AssemblyAI assemblyai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | yes | no | 2026-11-04 | | assistant-ui assistant-ui.com | None found | – | 79 B | – | no | 2026-11-04 | | Astro astro.build | Verified no auth | – | 52 C | – | no | 2026-11-04 | | Autosana autosana.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Aviator aviator.co | None found | – | 55 C | – | no | 2026-11-04 | | Avo avo.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | AWS api.aws | Verified no auth | – | | – | not read | 2026-11-04 | | Axiom axiom.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | Axolo axolo.co | None found | – | 41 D | – | no | 2026-11-04 | | Azure azure.com | None found | – | 58 C | – | no | 2026-11-04 | | Base44 base44.com | None found | – | 86 A | – | no | 2026-11-04 | | Beam beam.cloud | None found | – | 74 B | – | no | 2026-11-04 | | Bear bear.app | None found | – | 40 D | – | no | 2026-11-04 | | BigTime bigtime.net | None found | – | 41 D | – | no | 2026-11-04 | | Bird bird.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | no | 2026-11-04 | | Bitbucket bitbucket.org | None found | – | 34 D | – | no | 2026-11-04 | | Bitly bitly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Bitrise bitrise.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Blaxel blaxel.ai | None found | – | 80 B | – | no | 2026-11-04 | | Bolt bolt.new | None found | – | 65 C | – | no | 2026-11-04 | | Botcity botcity.dev | None found | – | 65 C | – | not read | 2026-11-04 | | Bowmark bowmark.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Brainboard brainboard.co | None found | – | 65 C | – | no | 2026-11-04 | | Browserbook browserbook.com | None found | – | 40 D | – | no | 2026-11-04 | | Browserstack browserstack.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | BuildBuddy buildbuddy.io | None found | – | 44 D | – | no | 2026-11-04 | | Builder.io builder.io | None found | – | 45 D | – | no | 2026-11-04 | | BuildJet buildjet.com | None found | – | 45 D | – | no | 2026-11-04 | | Buildwithglide buildwithglide.com | None found | – | 45 D | – | no | 2026-11-04 | | Bun bun.sh | None found | – | 49 C | – | no | 2026-11-04 | | Capacities capacities.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Cedana cedana.ai | None found | – | 34 D | – | no | 2026-11-04 | | Cekura cekura.ai | None found | – | 82 B | – | no | 2026-11-04 | | Chonkie chonkie.ai | No answer | – | 43 D | – | no | 2026-11-04 | | Ciphyr ciphyr.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Clarm clarm.com | None found | – | 69 C | yes | no | 2026-11-04 | | Claude claude.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Clidey clidey.com | None found | – | 38 D | – | no | 2026-11-04 | | Cline cline.bot | None found | – | 77 B | – | no | 2026-11-04 | | Clockify™ clockify.me | None found | – | 64 C | – | no | 2026-11-04 | | Cloudchipr cloudchipr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Cloudglue cloudglue.dev | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Cloudinary cloudinary.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Cloudthread cloudthread.io | None found | – | 41 D | – | not read | 2026-11-04 | | Clubhouse clubhouse.io | None found | – | 62 C | yes | no | 2026-11-04 | | cmux cmux.com | None found | – | 43 D | – | no | 2026-11-04 | | Coasts coasts.dev | None found | – | 40 D | – | no | 2026-11-04 | | Code Climate codeclimate.com | None found | – | 50 C | – | no | 2026-11-04 | | Codeanywhere codeanywhere.com | None found | – | 40 D | – | no | 2026-11-04 | | Codeberg.org codeberg.org | None found | – | 54 C | – | no | 2026-11-04 | | Codecov codecov.io | None found | – | 68 C | – | not read | 2026-11-04 | | Codeium codeium.com | None found | – | 49 C | – | no | 2026-11-04 | | Codemagic codemagic.io | None found | – | 58 C | – | no | 2026-11-04 | | Coder coder.com | None found | – | 70 B | – | no | 2026-11-04 | | CodeSandbox codesandbox.io | None found | – | 44 D | – | no | 2026-11-04 | | Codev co.dev | None found | – | 50 C | – | no | 2026-11-04 | | Compyle compyle.ai | None found | – | 55 C | – | no | 2026-11-04 | | Concourse CI concourse-ci.org | None found | – | 41 D | – | no | 2026-11-04 | | Conductor conductor.build | None found | – | 72 B | – | no | 2026-11-04 | | Confident AI confident-ai.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 90 A | – | no | 2026-11-04 | | ConnectMachine connectmachine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Contentful contentful.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | contentful-cli | 74 B | – | no | 2026-11-04 | | Contentstack contentstack.com | Credential wall API key | – | 67 C | – | no | 2026-11-04 | | Continue continue.dev | No answer | – | 54 C | – | no | 2026-11-04 | | Convoy getconvoy.io | None found | – | 59 C | – | no | 2026-11-04 | | CORE getcore.me | No answer | – | 55 C | – | no | 2026-11-04 | | Corsair corsair.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Cortex cortex.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Cosine cosine.sh | None found | – | 37 D | – | no | 2026-11-04 | | Cosmic cosmicjs.com | None found | – | 75 B | yes | no | 2026-11-04 | | Courier courier.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 57 C | – | no | 2026-11-04 | | Coval coval.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 65 C | – | no | 2026-11-04 | | cubic cubic.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | Cursor cursor.com | None found | – | 74 B | – | no | 2026-11-04 | | Cyberdesk cyberdesk.io | None found | – | 74 B | – | no | 2026-11-04 | | Cypress Cloud cypress.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Dagger dagger.io | None found | – | 48 C | – | no | 2026-11-04 | | Dailybot dailybot.com | None found | – | 76 B | yes | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/developer-tools/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Developer Tools, page 2 | Agent MCP Directory" description: "Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 2 of 5. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/developer-tools/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Developer Tools, page 2 | Agent MCP Directory > Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 2 of 5. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/developer-tools/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Developer Tools: MCP servers and CLIs, page 2 450 companies in Developer Tools: 41 listed tools to a client with no credentials, 96 answered with a sign-in challenge (not counted) and 8 have a CLI on record. This page lists rows 101 to 200, from dari.dev to Kollektiv. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | dari.dev dari.dev | None found | – | 42 D | – | no | 2026-11-04 | | Datasaur datasaur.ai | None found | – | 69 C | – | no | 2026-11-04 | | Dedalus Labs dedaluslabs.ai | No answer | – | 85 B | – | no | 2026-11-04 | | Deepnote deepnote.com | None found | – | 65 C | – | no | 2026-11-04 | | DeepSource deepsource.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Deno deno.com | None found | deno | 65 C | – | no | 2026-11-04 | | Designbase designbase.com | None found | – | 55 C | – | no | 2026-11-04 | | Devtron devtron.ai | Credential wall API key | – | 48 C | – | no | 2026-11-04 | | DevZero devzero.io | None found | – | 58 C | – | no | 2026-11-04 | | Dittowords dittowords.com | None found | – | 67 C | – | no | 2026-11-04 | | Docket docketqa.com | None found | – | 58 C | – | no | 2026-11-04 | | Dojah dojah.io | None found | – | 77 B | – | no | 2026-11-04 | | Double double.bot | None found | – | 54 C | – | no | 2026-11-04 | | Draftbit draftbit.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Dragoneye dragoneye.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | DrDroid drdroid.io | None found | – | 61 C | – | no | 2026-11-04 | | Duffel duffel.com | None found | – | 65 C | – | no | 2026-11-04 | | Electroneek electroneek.com | None found | – | 68 C | – | no | 2026-11-04 | | Elementary Data elementary-data.com | No answer | – | 56 C | – | no | 2026-11-04 | | Ellipsis ellipsis.dev | No answer | – | 69 C | – | no | 2026-11-04 | | Embrace embrace.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 38 D | – | no | 2026-11-04 | | Env0 env0.com | None found | – | 73 B | – | no | 2026-11-04 | | esimgomobile esimgomobile.com | Verified no auth | – | | – | not read | 2026-11-04 | | Etherscan etherscan.io | Verified no auth | – | | – | no | 2026-11-04 | | Everhour everhour.com | None found | – | 68 C | – | no | 2026-11-04 | | Evidently AI evidentlyai.com | None found | – | 58 C | – | no | 2026-11-04 | | Expo expo.dev | Sign-in required OAuth DCR; tools not seen, not counted | eas-cli | 66 C | – | no | 2026-11-04 | | Extend extend.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Fastmail fastmail.com | None found | – | 37 D | – | no | 2026-11-04 | | Fastshot fastshot.ai | None found | – | 66 C | – | no | 2026-11-04 | | Flightpowers flightpowers.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Flux fluxcd.io | None found | – | 38 D | – | no | 2026-11-04 | | Font Awesome fontawesome.com | None found | – | 56 C | – | no | 2026-11-04 | | Footgun getfootgun.com | Verified no auth | – | | – | not read | 2026-11-04 | | Freestyle freestyle.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | yes | no | 2026-11-04 | | GameAnalytics gameanalytics.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | Getdecipher getdecipher.com | None found | – | 45 D | – | no | 2026-11-04 | | Ghost ghost.org | None found | – | 70 B | – | no | 2026-11-04 | | GitBook gitbook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 86 A | – | no | 2026-11-04 | | Gitea gitea.com | None found | – | 55 C | – | no | 2026-11-04 | | GitHub github.com | Sign-in required OAuth; tools not seen, not counted | – | 65 C | yes | no | 2026-11-04 | | Githubcopilot githubcopilot.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | GitLab gitlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | GitMCP gitmcp.io | Verified no auth | – | 37 D | – | not read | 2026-11-04 | | Gitpod gitpod.io | None found | – | 41 D | – | not read | 2026-11-04 | | GlanceAI glance.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Glassflow glassflow.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Glideapps glideapps.com | No answer | – | 64 C | – | no | 2026-11-04 | | Globalping globalping.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Goldsky goldsky.com | Verified no auth | – | 81 B | – | not read | 2026-11-04 | | Greptile greptile.com | None found | – | 77 B | – | no | 2026-11-04 | | Habitica habitica.com | None found | – | 34 D | – | no | 2026-11-04 | | HackerRank hackerrank.com | None found | – | 69 C | – | no | 2026-11-04 | | hardoz hardoz.eu.cc | No answer | – | | – | not read | 2026-11-04 | | Harness harness.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 75 B | – | no | 2026-11-04 | | HARVEST.com harvest.com | None found | – | 39 D | – | no | 2026-11-04 | | Hasura hasura.io | None found | – | 51 C | – | no | 2026-11-04 | | Hatchet hatchet.run | None found | – | 53 C | – | no | 2026-11-04 | | Haystackeditor haystackeditor.com | None found | – | 44 D | – | no | 2026-11-04 | | HelixDB helix-db.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 82 B | yes | no | 2026-11-04 | | HeroUI heroui.com | None found | – | 81 B | yes | no | 2026-11-04 | | Hexclave hexclave.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 85 B | yes | no | 2026-11-04 | | Hive hive.com | None found | – | 66 C | – | no | 2026-11-04 | | Honeybadger honeybadger.io | None found | – | 72 B | – | not read | 2026-11-04 | | hoop.dev hoop.dev | None found | – | 41 D | – | no | 2026-11-04 | | hotglue hotglue.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Hubstaff hubstaff.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Hyperbeam hyperbeam.com | None found | – | 57 C | – | no | 2026-11-04 | | Hypotize hypotize.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | iHatePosting ihateposting.com | Verified no auth | – | | – | not read | 2026-11-04 | | Imgix imgix.com | None found | – | 67 C | – | no | 2026-11-04 | | IncidentFox incidentfox.ai | None found | – | 67 C | – | no | 2026-11-04 | | Inconvo inconvo.com | None found | – | 60 C | – | no | 2026-11-04 | | Infer infer.so | None found | – | 37 D | – | no | 2026-11-04 | | Infield infield.ai | None found | – | 48 C | – | no | 2026-11-04 | | Infra infra.new | None found | – | 60 C | – | no | 2026-11-04 | | Infracost infracost.io | No answer | – | 50 C | – | no | 2026-11-04 | | Inkeep inkeep.com | No answer | – | 71 B | – | no | 2026-11-04 | | InsForge insforge.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | – | no | 2026-11-04 | | Instant instantdb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Integuru integuru.ai | None found | – | 47 D | – | no | 2026-11-04 | | Interfaze interfaze.ai | None found | – | 66 C | yes | no | 2026-11-04 | | Interfere interfere.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Intuned intunedhq.com | None found | – | 63 C | – | no | 2026-11-04 | | Jam.dev jam.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | Javadocs.dev javadocs.dev | Verified no auth | – | 47 D | yes | not read | 2026-11-04 | | Jet Admin jetadmin.io | None found | – | 65 C | – | no | 2026-11-04 | | JetBrains jetbrains.com | None found | – | 62 C | – | no | 2026-11-04 | | JFrog jfrog.com | None found | – | 70 B | – | no | 2026-11-04 | | JustClaw-It justclaw.it.com | Verified no auth | – | | – | not read | 2026-11-04 | | K9s k9scli.io | None found | – | 42 D | – | no | 2026-11-04 | | Kanbanize kanbanize.com | None found | – | 43 D | – | no | 2026-11-04 | | Karate Labs karatelabs.io | None found | – | 63 C | – | no | 2026-11-04 | | Kashikoi getkashikoi.com | None found | – | 39 D | – | no | 2026-11-04 | | Keep(卡路里科技)-自律给我自由 google.keep.com | None found | – | 52 C | – | no | 2026-11-04 | | Keet trykeet.com | None found | – | 53 C | – | no | 2026-11-04 | | KERNEL kernel.sh | None found | – | 86 A | – | no | 2026-11-04 | | Keyframe Labs keyframelabs.com | None found | – | 65 C | – | no | 2026-11-04 | | Kitemaker kitemaker.co | None found | – | 34 D | – | no | 2026-11-04 | | Kollektiv thekollektiv.ai | No answer | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/developer-tools/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Developer Tools, page 3 | Agent MCP Directory" description: "Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 3 of 5. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/developer-tools/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Developer Tools, page 3 | Agent MCP Directory > Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 3 of 5. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/developer-tools/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Developer Tools: MCP servers and CLIs, page 3 450 companies in Developer Tools: 41 listed tools to a client with no credentials, 96 answered with a sign-in challenge (not counted) and 8 have a CLI on record. This page lists rows 201 to 300, from Komodor to Random Labs. ## Rows 201 to 300 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Komodor komodor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Kubecost kubecost.com | None found | – | 43 D | – | no | 2026-11-04 | | Laminar laminar.sh | None found | – | 41 D | – | no | 2026-11-04 | | Lark getlark.ai | None found | – | 56 C | – | no | 2026-11-04 | | Leantime leantime.io | None found | – | 52 C | – | no | 2026-11-04 | | Lemma uselemma.ai | None found | – | 66 C | – | no | 2026-11-04 | | Lightsprint lightsprint.ai | None found | – | 62 C | – | no | 2026-11-04 | | Lingo.dev lingo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | LiteLLM litellm.ai | None found | – | 73 B | – | no | 2026-11-04 | | Loft loft.sh | None found | – | 53 C | – | no | 2026-11-04 | | LogRocket logrocket.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Logseq logseq.com | None found | – | 38 D | – | no | 2026-11-04 | | Lotas AI lotas.ai | None found | – | 51 C | – | no | 2026-11-04 | | Luciq luciq.ai | None found | – | 77 B | – | no | 2026-11-04 | | Maatsii maatsii.com | Verified no auth | – | | – | not read | 2026-11-04 | | MagicBell magicbell.com | None found | – | 47 D | – | no | 2026-11-04 | | Magnitude magnitude.dev | None found | – | 74 B | – | no | 2026-11-04 | | Maitai trymaitai.com | None found | – | 60 C | – | no | 2026-11-04 | | Manicule manicule.dev | None found | – | 33 D | – | no | 2026-11-04 | | Manufact manufact.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | yes | no | 2026-11-04 | | Massdriver massdriver.cloud | None found | – | 63 C | – | no | 2026-11-04 | | Mastra mastra.ai | None found | – | 78 B | – | no | 2026-11-04 | | Mem mem.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Mergent mergent.co | None found | – | 59 C | – | no | 2026-11-04 | | Mergify mergify.com | None found | – | 75 B | yes | no | 2026-11-04 | | Metoro metoro.io | None found | – | 43 D | – | no | 2026-11-04 | | Mezmo mezmo.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | Microsoft Learn learn.microsoft.com | Verified no auth | azure-cli | 24 F | – | not read | 2026-11-04 | | Minded minded.com | None found | – | 58 C | – | no | 2026-11-04 | | Mindee mindee.com | None found | – | 73 B | – | no | 2026-11-04 | | Mindsdb mindsdb.com | None found | – | 51 C | – | not read | 2026-11-04 | | Mintlify mintlify.com | Verified no auth | mint | 74 B | – | no | 2026-11-04 | | Mito trymito.io | None found | – | 49 C | – | no | 2026-11-04 | | mlop mlop.ai | None found | – | 38 D | – | no | 2026-11-04 | | MobileBoost mobileboost.io | None found | – | 66 C | – | no | 2026-11-04 | | Modelence modelence.com | None found | – | 60 C | – | no | 2026-11-04 | | Momentic momentic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Morph morphllm.com | No answer | – | 82 B | – | no | 2026-11-04 | | Morphik morphik.ai | No answer | – | 70 B | – | no | 2026-11-04 | | Moss moss.dev | None found | – | 81 B | – | no | 2026-11-04 | | MovingLake movinglake.com | None found | – | 39 D | – | no | 2026-11-04 | | MuleSoft mulesoft.com | None found | – | 36 D | – | no | 2026-11-04 | | Mux mux.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Nanonets nanonets.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Neon neon.tech | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | Noloco noloco.io | None found | – | 55 C | – | no | 2026-11-04 | | Notaiochianese notaiochianese.it | Verified no auth | – | | – | not read | 2026-11-04 | | Notion HQ notionhq.com | None found | – | 56 C | – | no | 2026-11-04 | | Notte notte.cc | None found | – | 89 A | – | no | 2026-11-04 | | Noveum noveum.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | not read | 2026-11-04 | | Nuanced nuanced.dev | None found | – | 49 C | – | no | 2026-11-04 | | Nullstone nullstone.io | None found | – | 42 D | – | no | 2026-11-04 | | Nyckel nyckel.com | None found | – | 64 C | – | no | 2026-11-04 | | Ocular useocular.com | None found | – | 59 C | – | no | 2026-11-04 | | Offline Protocol offlineprotocol.com | Verified no auth | – | | – | not read | 2026-11-04 | | Okteto okteto.com | None found | – | 58 C | – | no | 2026-11-04 | | Ollama ollama.com | None found | – | 65 C | – | no | 2026-11-04 | | Omnara omnara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | Omnistrate omnistrate.com | None found | – | 56 C | – | no | 2026-11-04 | | Onenote onenote.com | None found | – | 43 D | – | no | 2026-11-04 | | Onlook onlook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Openfoundry openfoundry.ai | None found | – | 37 D | – | no | 2026-11-04 | | Openlayer openlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | OpenReplay openreplay.com | None found | – | 66 C | – | no | 2026-11-04 | | OpenZeppelin openzeppelin.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Opslane opslane.com | None found | – | 47 D | – | no | 2026-11-04 | | OpsLevel opslevel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | Outlit outlit.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | no | 2026-11-04 | | PageProofer pageproofer.com | Credential wall API key | – | | – | not read | 2026-11-04 | | Palenca palenca.com | None found | – | 42 D | – | not read | 2026-11-04 | | Palisade palisade.email | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | ParadeDB paradedb.com | None found | – | 76 B | – | no | 2026-11-04 | | Paragon useparagon.com | None found | – | 70 B | – | no | 2026-11-04 | | Parea parea.ai | None found | – | 49 C | – | no | 2026-11-04 | | Parse parse.bot | None found | – | 65 C | – | no | 2026-11-04 | | Pipekit pipekit.io | None found | – | 58 C | – | no | 2026-11-04 | | Plane plane.so | No answer | – | 78 B | yes | no | 2026-11-04 | | PlanetScale planetscale.com | None found | – | 79 B | – | no | 2026-11-04 | | Ploomber ploomber.io | None found | – | 34 D | – | not read | 2026-11-04 | | Polar Signals polarsignals.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Poly poly.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Pontofato pontofato.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Portainer portainer.io | None found | – | 70 B | – | no | 2026-11-04 | | PostData postdata.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | Postman postman.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | PreShiftIQ preshiftiq.com | Verified no auth | – | | – | not read | 2026-11-04 | | Primitive primitive.dev | Verified no auth | – | 96 A+ | yes | yes | 2026-11-04 | | PrintFriendly printfriendly.com | Credential wall API key | – | | yes | not read | 2026-11-04 | | Prisma prisma.io | Sign-in required OAuth DCR; tools not seen, not counted | prisma | 82 B | yes | no | 2026-11-04 | | Promptless promptless.ai | None found | – | 60 C | – | no | 2026-11-04 | | PropelAuth propelauth.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Qualityclouds qualityclouds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Quantstruct quantstruct.com | None found | – | 53 C | – | no | 2026-11-04 | | Queryvary queryvary.com | None found | – | 34 D | – | not read | 2026-11-04 | | Quicknode quicknode.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Quill quill.co | None found | – | 39 D | – | no | 2026-11-04 | | Radar Cnpj radar-cnpj.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Rainforest QA rainforestqa.com | None found | – | 70 B | – | no | 2026-11-04 | | Rancher rancher.com | None found | – | 40 D | – | no | 2026-11-04 | | Random Labs randomlabs.ai | None found | – | 45 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/developer-tools/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Developer Tools, page 4 | Agent MCP Directory" description: "Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 4 of 5. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/developer-tools/page/4 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Developer Tools, page 4 | Agent MCP Directory > Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 4 of 5. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/developer-tools/page/4 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Developer Tools: MCP servers and CLIs, page 4 450 companies in Developer Tools: 41 listed tools to a client with no credentials, 96 answered with a sign-in challenge (not counted) and 8 have a CLI on record. This page lists rows 301 to 400, from Readdle to TickTick. ## Rows 301 to 400 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Readdle readdle.com | None found | – | 45 D | – | no | 2026-11-04 | | ReadMe readme.com | None found | – | 64 C | – | no | 2026-11-04 | | Realeyes realeyes.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Recall.ai recall.ai | None found | – | 73 B | – | no | 2026-11-04 | | Refine refine.dev | None found | – | 46 D | – | no | 2026-11-04 | | Reflect reflect.app | None found | – | 46 D | yes | no | 2026-11-04 | | Reflex reflex.dev | None found | – | 67 C | – | no | 2026-11-04 | | Release release.com | None found | – | 52 C | – | no | 2026-11-04 | | Relvy relvy.ai | None found | – | 42 D | – | no | 2026-11-04 | | Replicas replicas.dev | None found | – | 78 B | – | no | 2026-11-04 | | Replit replit.com | No answer | – | 73 B | – | no | 2026-11-04 | | Replo replo.app | None found | – | 64 C | – | no | 2026-11-04 | | Rescuetime rescuetime.com | None found | – | 56 C | – | no | 2026-11-04 | | Resemble AI resemble.ai | Verified no auth | – | 74 B | – | not read | 2026-11-04 | | Respan respan.ai | None found | – | 72 B | – | no | 2026-11-04 | | RestaurantDoctorAI restaurantdoctorai.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Retool retool.com | None found | – | 78 B | – | no | 2026-11-04 | | Revyl revyl.ai | None found | – | 48 C | – | no | 2026-11-04 | | Rownd rownd.ai | None found | – | 34 D | – | no | 2026-11-04 | | Rulebricks rulebricks.com | None found | – | 59 C | – | no | 2026-11-04 | | Runautomat runautomat.com | No answer | – | 65 C | – | no | 2026-11-04 | | Runcaptain runcaptain.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 57 C | – | no | 2026-11-04 | | RunLocal runlocal.ai | None found | – | 44 D | – | no | 2026-11-04 | | Runtm runtm.com | None found | – | 66 C | – | no | 2026-11-04 | | Rus.sh rus.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ryvn ryvn.ai | None found | – | 60 C | – | no | 2026-11-04 | | S2 s2.dev | None found | – | 61 C | – | no | 2026-11-04 | | Sanity sanity.io | Sign-in required OAuth DCR; tools not seen, not counted | @sanity/cli | 72 B | – | no | 2026-11-04 | | Sazabi sazabi.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Scalr scalr.com | None found | – | 56 C | – | no | 2026-11-04 | | Scape scape.app | None found | – | 36 D | – | no | 2026-11-04 | | ScrapingBee scrapingbee.com | Verified no auth | – | 61 C | – | not read | 2026-11-04 | | Seam seam.co | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 53 C | – | no | 2026-11-04 | | Semgrep semgrep.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Shipbook shipbook.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shortcut shortcut.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | yes | no | 2026-11-04 | | Shuttle shuttle.dev | None found | – | 47 D | – | no | 2026-11-04 | | SigmaMind AI sigmamind.ai | None found | – | 74 B | – | no | 2026-11-04 | | Signadot signadot.com | No answer | – | 68 C | – | no | 2026-11-04 | | SigNoz signoz.io | None found | – | 71 B | – | no | 2026-11-04 | | Simplenote simplenote.com | None found | – | 40 D | – | no | 2026-11-04 | | SkyAccess skyaccess.com | Verified no auth | – | | – | not read | 2026-11-04 | | Skyhook skyhook.io | None found | – | 72 B | – | no | 2026-11-04 | | Skyvern skyvern.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | no | 2026-11-04 | | Smobi smobi.com | None found | – | 52 C | – | no | 2026-11-04 | | Sonar sonarsource.com | None found | – | 71 B | – | no | 2026-11-04 | | Sonatype sonatype.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | Soracom soracom.com | Verified no auth | – | | – | not read | 2026-11-04 | | Sourcebot sourcebot.dev | None found | – | 65 C | – | no | 2026-11-04 | | SourceForge sourceforge.net | None found | – | 69 C | – | no | 2026-11-04 | | Sourcegraph sourcegraph.com | None found | – | 55 C | – | no | 2026-11-04 | | sourcehut sourcehut.org | None found | – | 46 D | – | no | 2026-11-04 | | Spacelift spacelift.io | None found | – | 62 C | – | no | 2026-11-04 | | Specific specific.dev | None found | – | 67 C | – | no | 2026-11-04 | | Speedscale speedscale.com | None found | – | 66 C | – | no | 2026-11-04 | | Spike spike.app | None found | – | 34 D | – | no | 2026-11-04 | | Spinnaker spinnaker.io | None found | – | 39 D | – | no | 2026-11-04 | | Spurtest spurtest.com | None found | – | 56 C | – | no | 2026-11-04 | | Sre sre.ai | None found | – | 50 C | – | no | 2026-11-04 | | StableBrowse stablebrowse.com | None found | – | 54 C | – | no | 2026-11-04 | | Stably stably.ai | None found | – | 79 B | – | no | 2026-11-04 | | StackBlitz stackblitz.com | None found | – | 46 D | – | no | 2026-11-04 | | StackOverflow stackoverflow.com | Credential wall API key | – | 23 F | – | no | 2026-11-04 | | Stackup stackup.fi | None found | – | 37 D | – | no | 2026-11-04 | | stagewise stagewise.io | None found | – | 71 B | – | no | 2026-11-04 | | Standard Notes standardnotes.com | None found | – | 37 D | – | no | 2026-11-04 | | StarSling starsling.dev | None found | – | 50 C | – | no | 2026-11-04 | | Storia storia.ai | None found | – | 43 D | – | not read | 2026-11-04 | | StoriesIG storiesig.info | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Storyblok storyblok.com | No tools listed | – | 67 C | – | no | 2026-11-04 | | Storybook storybook.js.org | None found | – | 64 C | – | no | 2026-11-04 | | Strapi strapi.io | None found | – | 64 C | – | no | 2026-11-04 | | Struct struct.ai | None found | – | 67 C | – | no | 2026-11-04 | | Structura structura.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SugarSync sugarsync.com | None found | – | 55 C | – | no | 2026-11-04 | | Sunpia sunpia.io | None found | – | 40 D | – | no | 2026-11-04 | | Supabase supabase.com | Sign-in required OAuth DCR; tools not seen, not counted | supabase | 93 A | yes | no | 2026-11-04 | | superglue superglue.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Supernova.io supernova.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Surge surge.app | None found | – | 72 B | – | no | 2026-11-04 | | Svix svix.com | No answer | – | 69 C | – | no | 2026-11-04 | | Swarmia swarmia.com | None found | – | 60 C | – | no | 2026-11-04 | | Sweep sweep.dev | None found | – | 40 D | – | not read | 2026-11-04 | | T3 t3.chat | None found | – | 58 C | – | no | 2026-11-04 | | Tabnine tabnine.com | None found | – | 66 C | – | not read | 2026-11-04 | | Tailor tailor.tech | None found | – | 50 C | – | no | 2026-11-04 | | Taloflow taloflow.ai | None found | – | 39 D | – | no | 2026-11-04 | | Tana tana.inc | None found | – | 64 C | – | no | 2026-11-04 | | Teamwork.com teamwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Tempo tempo.new | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | TensorPool tensorpool.dev | None found | – | 35 D | – | no | 2026-11-04 | | Termii termii.com | None found | – | 45 D | – | no | 2026-11-04 | | Terracotta tryterracotta.com | None found | – | 52 C | – | no | 2026-11-04 | | Terrateam terrateam.io | None found | – | 52 C | – | no | 2026-11-04 | | testRigor testrigor.com | Credential wall API key | – | 56 C | – | no | 2026-11-04 | | The Context Company thecontext.company | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 58 C | – | no | 2026-11-04 | | Theneo theneo.io | No answer | – | 67 C | – | no | 2026-11-04 | | Thunder Compute thundercompute.com | None found | – | 76 B | – | no | 2026-11-04 | | Thunkable thunkable.com | None found | – | 48 C | – | no | 2026-11-04 | | TickTick ticktick.com | No answer | – | 61 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/developer-tools/page/4/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Developer Tools, page 5 | Agent MCP Directory" description: "Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 5 of 5. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/developer-tools/page/5 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Developer Tools, page 5 | Agent MCP Directory > Developer Tools: 450 companies, 41 with tools listed and 8 with a CLI on record, checked 4 November 2026. Page 5 of 5. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/developer-tools/page/5 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Developer Tools: MCP servers and CLIs, page 5 450 companies in Developer Tools: 41 listed tools to a client with no credentials, 96 answered with a sign-in challenge (not counted) and 8 have a CLI on record. This page lists rows 401 to 450, from Time Doctor to Zip-Codes.com. ## Rows 401 to 450 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Time Doctor timedoctor.com | None found | – | 37 D | – | no | 2026-11-04 | | Timely timely.com | None found | – | 58 C | – | no | 2026-11-04 | | Tiptap tiptap.dev | None found | – | 62 C | – | no | 2026-11-04 | | Toggl toggl.com | None found | – | 59 C | – | no | 2026-11-04 | | TracePass tracepass.eu | Verified no auth | – | | yes | not read | 2026-11-04 | | Trainloop AI trainloop.ai | None found | – | 51 C | – | no | 2026-11-04 | | Trainy trainy.ai | None found | – | 77 B | – | no | 2026-11-04 | | Travis CI travis-ci.com | None found | – | 53 C | – | no | 2026-11-04 | | Trivy trivy.dev | None found | – | 34 D | – | no | 2026-11-04 | | Truffle AI trytruffle.ai | None found | – | 47 D | – | no | 2026-11-04 | | Trynia trynia.ai | None found | – | 62 C | – | no | 2026-11-04 | | Trypillar trypillar.com | None found | – | 49 C | – | not read | 2026-11-04 | | Tumult tumult.com | None found | – | 35 D | – | no | 2026-11-04 | | Tusk usetusk.ai | None found | – | 56 C | – | no | 2026-11-04 | | Typewise typewise.app | None found | – | 75 B | – | no | 2026-11-04 | | Ulapcybo ulapcybo.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | unify unify.ai | None found | – | 42 D | – | no | 2026-11-04 | | Unlayer unlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Unsiloed AI unsiloed.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Unsloth unsloth.ai | None found | – | 43 D | – | no | 2026-11-04 | | Upsolve AI upsolve.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | v0 v0.dev | None found | – | 66 C | – | no | 2026-11-04 | | Vaaya vaaya.ai | Verified no auth | – | 90 A | yes | not read | 2026-11-04 | | VectorShift vectorshift.ai | None found | – | 69 C | – | no | 2026-11-04 | | Veryfi veryfi.com | None found | – | 69 C | – | no | 2026-11-04 | | vibe vibe.codes | None found | – | 39 D | – | no | 2026-11-04 | | VibeFlow vibeflow.ai | None found | – | 73 B | – | no | 2026-11-04 | | Vimmerse vimmerse.net | None found | – | 52 C | – | no | 2026-11-04 | | Visa visa.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | vocode vocode.dev | None found | – | 60 C | – | no | 2026-11-04 | | Voker voker.ai | None found | – | 62 C | – | no | 2026-11-04 | | Waldium waldium.com | No answer | – | 37 D | – | no | 2026-11-04 | | Warp warp.dev | None found | – | 80 B | – | no | 2026-11-04 | | WarpBuild warpbuild.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Wasmer wasmer.io | None found | – | 62 C | – | no | 2026-11-04 | | Waydev waydev.co | None found | – | 64 C | – | no | 2026-11-04 | | Webiny webiny.com | None found | – | 67 C | – | no | 2026-11-04 | | WeTransfer wetransfer.com | None found | – | 39 D | – | no | 2026-11-04 | | WeWeb weweb.io | None found | – | 62 C | – | no | 2026-11-04 | | Wild Moose AI wildmoose.ai | None found | – | 59 C | – | no | 2026-11-04 | | Windmill windmill.dev | None found | – | 56 C | – | no | 2026-11-04 | | Windsurf windsurf.com | None found | – | 57 C | – | no | 2026-11-04 | | Workamajig workamajig.com | No answer | – | 62 C | – | no | 2026-11-04 | | Workflowy workflowy.com | None found | – | 59 C | – | no | 2026-11-04 | | Wrike wrike.com | No answer | – | 66 C | – | no | 2026-11-04 | | Xquik xquik.com | Verified no auth | – | 92 A | yes | not read | 2026-11-04 | | Zed zed.dev | None found | – | 57 C | – | no | 2026-11-04 | | ZeroEval zeroeval.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 65 C | – | no | 2026-11-04 | | zeroheight zeroheight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Zip-Codes.com zip-codes.com | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/developer-tools/page/5/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "E-commerce: MCP servers and CLIs | Agent MCP Directory" description: "E-commerce: 14 companies, 7 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/e-commerce site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # E-commerce: MCP servers and CLIs | Agent MCP Directory > E-commerce: 14 companies, 7 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/e-commerce Site: Agent MCP Directory Last reviewed: 2026-11-05 # E-commerce: MCP servers and CLIs 14 companies in E-commerce: 7 listed tools to a client with no credentials, 7 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from App Store Tracker to Zinc. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | App Store Tracker appstoretracker.com | Verified no auth | – | 43 D | – | not read | 2026-11-04 | | AppmanAi appmanai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ASO Atlas asoatlas.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | BestPrice bestprice.gr | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | Channel3 trychannel3.com | Verified no auth | – | 92 A | – | no | 2026-11-04 | | FlickDirect flickdirect.com | Verified no auth | – | | – | not read | 2026-11-04 | | Getappniche getappniche.com | Verified no auth | – | | – | not read | 2026-11-04 | | Inttegro inttegro.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | kari kari.com | Verified no auth | – | | – | not read | 2026-11-04 | | MCPEmails mcpemails.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Say It Again sayitagain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SKU.io sku.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Social Growth Engineers socialgrowthengineers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Zinc zinc.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/e-commerce/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Education: MCP servers and CLIs | Agent MCP Directory" description: "Education: 2 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/education site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Education: MCP servers and CLIs | Agent MCP Directory > Education: 2 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/education Site: Agent MCP Directory Last reviewed: 2026-11-05 # Education: MCP servers and CLIs 2 companies in Education: 1 listed tools to a client with no credentials, 1 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Padlet to Studocu. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Padlet padlet.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Studocu studocu.com | Verified no auth | – | 40 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/education/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Gaming & Media: MCP servers and CLIs | Agent MCP Directory" description: "Gaming & Media: 12 companies, 4 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/gaming-and-media site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Gaming & Media: MCP servers and CLIs | Agent MCP Directory > Gaming & Media: 12 companies, 4 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/gaming-and-media Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gaming & Media: MCP servers and CLIs 12 companies in Gaming & Media: 4 listed tools to a client with no credentials, 6 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from aikstockdata to Upload-Post. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | aikstockdata aikstockdata.com | Verified no auth | – | | yes | not read | 2026-11-04 | | beehiiv beehiiv.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | Epidemic Sound epidemicsound.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Hookstep hookstep.in | Credential wall API key | – | | – | not read | 2026-11-04 | | Magic Hour magichour.ai | Verified no auth | – | 89 A | yes | no | 2026-11-04 | | MnogoReels mnogo-reels.ru | Verified no auth | – | | – | not read | 2026-11-04 | | Pexafy pexafy.com | Verified no auth | – | | – | not read | 2026-11-04 | | Picsart picsart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Screenshot Scout screenshotscout.com | Credential wall API key | – | | – | not read | 2026-11-04 | | ShapelessAI shapelessai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | SpriteCook spritecook.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Upload-Post upload-post.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/gaming-and-media/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Hardware & Robotics: MCP servers and CLIs | Agent MCP Directory" description: "Hardware & Robotics: 2 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/hardware-and-robotics site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Hardware & Robotics: MCP servers and CLIs | Agent MCP Directory > Hardware & Robotics: 2 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/hardware-and-robotics Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hardware & Robotics: MCP servers and CLIs 2 companies in Hardware & Robotics: 1 listed tools to a client with no credentials, 1 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Siemens to Tenet Industries. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Siemens siemens.com | Verified no auth | – | 56 C | – | no | 2026-11-04 | | Tenet Industries tenetindustries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/hardware-and-robotics/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Healthcare: MCP servers and CLIs | Agent MCP Directory" description: "Healthcare: 2 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/healthcare site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Healthcare: MCP servers and CLIs | Agent MCP Directory > Healthcare: 2 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/healthcare Site: Agent MCP Directory Last reviewed: 2026-11-05 # Healthcare: MCP servers and CLIs 2 companies in Healthcare: 1 listed tools to a client with no credentials, 1 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Findabis to Medplum. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Findabis findabis.com | Verified no auth | – | | – | not read | 2026-11-04 | | Medplum medplum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 43 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/healthcare/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "HR & Recruiting: MCP servers and CLIs | Agent MCP Directory" description: "HR & Recruiting: 1 company, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/hr-and-recruiting site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # HR & Recruiting: MCP servers and CLIs | Agent MCP Directory > HR & Recruiting: 1 company, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/hr-and-recruiting Site: Agent MCP Directory Last reviewed: 2026-11-05 # HR & Recruiting: MCP servers and CLIs 1 company in HR & Recruiting: 1 listed tools to a client with no credentials, 0 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Fiber AI to Fiber AI. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Fiber AI fiber.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/hr-and-recruiting/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Identity & Auth: MCP servers and CLIs | Agent MCP Directory" description: "Identity & Auth: 6 companies, 3 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/identity-and-auth site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Identity & Auth: MCP servers and CLIs | Agent MCP Directory > Identity & Auth: 6 companies, 3 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/identity-and-auth Site: Agent MCP Directory Last reviewed: 2026-11-05 # Identity & Auth: MCP servers and CLIs 6 companies in Identity & Auth: 3 listed tools to a client with no credentials, 2 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from FusionAuth to WorkOS. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | FusionAuth fusionauth.io | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Google google.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | JumpCloud jumpcloud.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Microsoft microsoft.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Stytch stytch.com | None found | – | 63 C | – | no | 2026-11-04 | | WorkOS workos.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/identity-and-auth/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Infrastructure: MCP servers and CLIs | Agent MCP Directory" description: "Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/infrastructure site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Infrastructure: MCP servers and CLIs | Agent MCP Directory > Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/infrastructure Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infrastructure: MCP servers and CLIs 303 companies in Infrastructure: 26 listed tools to a client with no credentials, 92 answered with a sign-in challenge (not counted) and 12 have a CLI on record. This page lists rows 1 to 100, from Acquia to Getmocha. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Acquia acquia.com | None found | – | 69 C | – | no | 2026-11-04 | | Activeloop activeloop.ai | None found | – | 47 D | – | no | 2026-11-04 | | Adalo adalo.com | None found | – | 69 C | – | no | 2026-11-04 | | AfterQuery afterquery.com | None found | – | 55 C | – | no | 2026-11-04 | | Agentalog agentalog.com | Verified no auth | – | | yes | not read | 2026-11-04 | | AgentHub agenthublabs.com | None found | – | 40 D | – | no | 2026-11-04 | | Agilitycms agilitycms.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Airbrake airbrake.io | None found | – | 49 C | – | not read | 2026-11-04 | | Airweave airweave.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 78 B | – | no | 2026-11-04 | | Alterlab alterlab.io | Verified no auth | – | | – | not read | 2026-11-04 | | Amazon Web Services aws.amazon.com | Verified no auth | awscli | 60 C | – | no | 2026-11-04 | | Amika amika.dev | None found | – | 55 C | – | no | 2026-11-04 | | APIVerve apiverve.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Apollo GraphQL apollographql.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 80 B | – | no | 2026-11-04 | | Apoxy apoxy.dev | None found | – | 37 D | – | no | 2026-11-04 | | Appcircle appcircle.io | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Appian appian.com | None found | – | 51 C | – | no | 2026-11-04 | | AppSignal appsignal.com | None found | – | 69 C | – | no | 2026-11-04 | | Aptible aptible.com | None found | – | 63 C | – | no | 2026-11-04 | | Ardent tryardent.com | None found | – | 71 B | – | no | 2026-11-04 | | Arthur arthur.ai | None found | – | 60 C | – | no | 2026-11-04 | | Automattic automattic.com | None found | – | 53 C | – | no | 2026-11-04 | | Auvik auvik.com | None found | – | 54 C | – | no | 2026-11-04 | | Backendless backendless.com | None found | – | 48 C | – | no | 2026-11-04 | | Benchspan benchspan.com | None found | – | 61 C | – | no | 2026-11-04 | | Bento bentoml.com | None found | – | 41 D | – | no | 2026-11-04 | | Better Stack betterstack.com | No answer | – | 59 C | – | no | 2026-11-04 | | Betteruptime betteruptime.com | None found | – | 48 C | – | no | 2026-11-04 | | BigPanda bigpanda.io | None found | – | 54 C | – | no | 2026-11-04 | | Blacksmith blacksmith.sh | None found | – | 42 D | – | no | 2026-11-04 | | Bland bland.com | None found | – | 60 C | yes | no | 2026-11-04 | | Blueprism blueprism.com | None found | – | 59 C | – | no | 2026-11-04 | | Bolna AI bolna.ai | No answer | – | 63 C | – | no | 2026-11-04 | | briq briq.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Bubble bubble.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 40 D | – | no | 2026-11-04 | | Bucket bucket.co | None found | – | 50 C | – | no | 2026-11-04 | | BugSnag bugsnag.com | None found | – | 52 C | – | no | 2026-11-04 | | Buildkite buildkite.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Carrd carrd.co | None found | – | 42 D | – | no | 2026-11-04 | | Castari castari.com | None found | – | 61 C | – | no | 2026-11-04 | | Cerebrium cerebrium.ai | Verified no auth | – | 86 A | – | no | 2026-11-04 | | CertScore.ai certscore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Chainstack chainstack.com | Verified no auth | – | 71 B | – | not read | 2026-11-04 | | Chamber usechamber.io | None found | – | 68 C | – | no | 2026-11-04 | | Chronosphere chronosphere.io | None found | – | 67 C | – | no | 2026-11-04 | | CircleCI circleci.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | yes | 2026-11-04 | | Cisco cisco.com | None found | – | 33 D | – | no | 2026-11-04 | | Cleanlab cleanlab.ai | None found | – | 34 D | – | no | 2026-11-04 | | CloudBees cloudbees.com | None found | – | 68 C | – | no | 2026-11-04 | | Cloudflare cloudflare.com | Verified no auth | wrangler | 82 B | yes | yes | 2026-11-04 | | CockroachDB cockroachlabs.com | None found | – | 69 C | – | no | 2026-11-04 | | Codefresh codefresh.io | None found | – | 50 C | – | no | 2026-11-04 | | Commsharbor commsharbor.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Compresr compresr.ai | None found | – | 49 C | yes | no | 2026-11-04 | | ConfigCat configcat.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 51 C | – | no | 2026-11-04 | | Confluent confluent.io | None found | – | 78 B | – | no | 2026-11-04 | | Convex convex.dev | Verified no auth; endpoint found by subdomain guess, verified by connecting | convex | 71 B | – | not read | 2026-11-04 | | Coralogix coralogix.com | None found | – | 79 B | yes | no | 2026-11-04 | | CoreMedia coremedia.com | None found | – | 57 C | – | no | 2026-11-04 | | CoreNexis API corenexis.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | CoreWeave coreweave.com | None found | – | 68 C | – | no | 2026-11-04 | | Costory costory.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Cpln cpln.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Craft CMS craftcms.com | None found | – | 44 D | – | no | 2026-11-04 | | Cronitor cronitor.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | CTGT ctgt.ai | None found | – | 46 D | – | no | 2026-11-04 | | CustomDomain™ customdomain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | cyon cyon.ch | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Daft daft.ai | None found | – | 45 D | – | no | 2026-11-04 | | Datadog datadoghq.com | Sign-in required OAuth DCR; tools not seen, not counted | @datadog/datadog-ci | 69 C | – | no | 2026-11-04 | | Deci deci.ai | None found | – | 44 D | – | no | 2026-11-04 | | Depot depot.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | DevCycle devcycle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Devo devo.com | None found | – | 43 D | – | no | 2026-11-04 | | Dialer getdialer.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Didit One didit.me | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | – | no | 2026-11-04 | | DigitalOcean digitalocean.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 74 B | – | no | 2026-11-04 | | Directus directus.io | None found | – | 47 D | – | no | 2026-11-04 | | Docker docker.com | No answer | – | 69 C | – | no | 2026-11-04 | | Dorik dorik.com | None found | – | 35 D | – | no | 2026-11-04 | | Dynatrace dynatrace.com | None found | – | 82 B | – | no | 2026-11-04 | | Egnyte egnyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Elastic elastic.co | None found | – | 59 C | – | no | 2026-11-04 | | EmpirioLabs AI empiriolabs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Encord encord.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 69 C | – | no | 2026-11-04 | | Epsilla epsilla.com | None found | – | 57 C | – | no | 2026-11-04 | | Fastero fastero.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | FastJVM fastjvm.com | None found | – | 43 D | – | no | 2026-11-04 | | Fastly fastly.com | None found | – | 70 B | – | no | 2026-11-04 | | Fiddler AI fiddler.ai | None found | – | 68 C | – | no | 2026-11-04 | | Firebase firebase.google.com | None found | firebase-tools | 56 C | – | not read | 2026-11-04 | | FireHydrant firehydrant.com | None found | – | 49 C | – | no | 2026-11-04 | | Flagsmith flagsmith.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 47 D | – | no | 2026-11-04 | | Flightcontrol flightcontrol.dev | None found | – | 46 D | – | no | 2026-11-04 | | FlowLeap flowleap.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flowtel flowtel.ai | None found | – | 55 C | – | no | 2026-11-04 | | FlutterFlow flutterflow.io | None found | – | 53 C | – | no | 2026-11-04 | | Fly fly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | no | 2026-11-04 | | Galileo AI galileo.ai | None found | – | 78 B | – | no | 2026-11-04 | | Getmocha getmocha.com | None found | – | 46 D | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/infrastructure/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Infrastructure, page 2 | Agent MCP Directory" description: "Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Page 2 of 4. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/infrastructure/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Infrastructure, page 2 | Agent MCP Directory > Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Page 2 of 4. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/infrastructure/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infrastructure: MCP servers and CLIs, page 2 303 companies in Infrastructure: 26 listed tools to a client with no credentials, 92 answered with a sign-in challenge (not counted) and 12 have a CLI on record. This page lists rows 101 to 200, from GitOps to Pulumi. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | GitOps gitops.tech | None found | – | 37 D | – | no | 2026-11-04 | | Glide glide.app | None found | – | 50 C | – | no | 2026-11-04 | | Google Cloud cloud.google.com | None found | – | 51 C | – | no | 2026-11-04 | | Grafana grafana.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Grafbase grafbase.com | No answer | – | 45 D | – | no | 2026-11-04 | | Graphcms graphcms.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Grav getgrav.org | None found | – | 68 C | – | no | 2026-11-04 | | Graylog graylog.org | None found | – | 45 D | – | no | 2026-11-04 | | GrowthBook growthbook.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | Guru getguru.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | HasData hasdata.com | Verified no auth | – | | – | not read | 2026-11-04 | | HashiCorp hashicorp.com | None found | – | 60 C | – | no | 2026-11-04 | | Heroku heroku.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | heroku | 73 B | – | no | 2026-11-04 | | HetrixTools hetrixtools.com | None found | – | 59 C | – | no | 2026-11-04 | | Hetzner hetzner.com | None found | – | 50 C | – | no | 2026-11-04 | | Hiro hiro.so | None found | – | 49 C | – | no | 2026-11-04 | | Honeycomb honeycomb.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | Hostinger hostinger.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | yes | 2026-11-04 | | Hygraph hygraph.com | None found | – | 69 C | – | no | 2026-11-04 | | Hyperspell hyperspell.com | None found | – | 75 B | – | no | 2026-11-04 | | ImageKit imagekit.io | Verified no auth | – | 63 C | – | not read | 2026-11-04 | | incident.io incident.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 64 C | – | no | 2026-11-04 | | Infobip infobip.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | IOMETE iomete.com | None found | – | 60 C | – | no | 2026-11-04 | | ix ix.dev | None found | – | 39 D | – | no | 2026-11-04 | | JustCall justcall.host | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kaiv kaiv.ai | Verified no auth | – | | – | not read | 2026-11-04 | | KeystoneJS keystonejs.com | None found | – | 55 C | – | no | 2026-11-04 | | Kili Technology kili-technology.com | None found | – | 59 C | – | no | 2026-11-04 | | Kinsta® kinsta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Kissflow kissflow.com | None found | – | 58 C | – | no | 2026-11-04 | | Kong konghq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Koyeb koyeb.com | None found | – | 61 C | – | no | 2026-11-04 | | Lambda lambdalabs.com | None found | – | 44 D | – | no | 2026-11-04 | | Last9 last9.io | None found | – | 73 B | – | no | 2026-11-04 | | LaunchDarkly launchdarkly.com | No answer | – | 69 C | – | no | 2026-11-04 | | Lightstep lightstep.com | None found | – | 42 D | – | no | 2026-11-04 | | Lilac getlilac.com | None found | – | 67 C | – | no | 2026-11-04 | | Limrun limrun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | Linode linode.com | None found | – | 53 C | – | no | 2026-11-04 | | Llmdata llmdata.com | None found | – | 35 D | – | no | 2026-11-04 | | Loggly loggly.com | None found | – | 52 C | – | no | 2026-11-04 | | LogicMonitor logicmonitor.com | None found | – | 46 D | – | no | 2026-11-04 | | Logz.io logz.io | None found | – | 58 C | – | no | 2026-11-04 | | Luel luel.ai | None found | – | 58 C | – | no | 2026-11-04 | | Lumman lumman.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mailkite mailkite.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Malware Patrol malwarepatrol.net | No answer | – | | – | not read | 2026-11-04 | | ManageEngine manageengine.com | No answer | – | 62 C | – | no | 2026-11-04 | | Maven trymaven.com | None found | – | 61 C | – | no | 2026-11-04 | | mcprush.com mcprush.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Memocore memocore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mendix mendix.com | None found | – | 72 B | – | no | 2026-11-04 | | Microsoft Azure azure.microsoft.com | None found | – | 51 C | – | no | 2026-11-04 | | Middleware middleware.io | None found | – | 52 C | – | no | 2026-11-04 | | Minicor minicor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | Moda moda.dev | None found | – | 85 B | – | no | 2026-11-04 | | MongoDB mongodb.com | None found | – | 78 B | – | no | 2026-11-04 | | Moogsoft moogsoft.com | None found | – | 41 D | – | no | 2026-11-04 | | Naive usenaive.ai | None found | – | 48 C | – | no | 2026-11-04 | | Nebius nebius.com | None found | – | 73 B | – | no | 2026-11-04 | | Neon neon.com | Sign-in required OAuth DCR; tools not seen, not counted | neonctl | 88 A | yes | no | 2026-11-04 | | Netlify netlify.com | Sign-in required OAuth DCR; tools not seen, not counted | netlify-cli | 92 A | yes | no | 2026-11-04 | | Nevercode nevercode.io | None found | – | 47 D | – | no | 2026-11-04 | | New Relic newrelic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Nginx nginx.com | None found | – | 47 D | – | no | 2026-11-04 | | ngrok ngrok.com | Sign-in required OAuth DCR; tools not seen, not counted | ngrok | 90 A | yes | no | 2026-11-04 | | Northflank northflank.com | Credential wall API key | – | 53 C | – | no | 2026-11-04 | | Octoml octoml.ai | None found | – | 38 D | – | no | 2026-11-04 | | Odigos odigos.io | None found | – | 69 C | – | no | 2026-11-04 | | Okibi okibi.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | | Opentext opentext.com | None found | – | 30 D | – | no | 2026-11-04 | | Opsgenie opsgenie.com | None found | – | 60 C | – | no | 2026-11-04 | | Opsramp opsramp.com | None found | – | 43 D | – | not read | 2026-11-04 | | Orthogonal orthogonal.com | None found | – | 66 C | – | no | 2026-11-04 | | Osmosis osmosis.ai | None found | – | 69 C | – | no | 2026-11-04 | | OutSystems outsystems.com | None found | – | 63 C | – | no | 2026-11-04 | | OVHcloud ovhcloud.com | None found | – | 58 C | – | no | 2026-11-04 | | Oximy oximy.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | PagerDuty pagerduty.com | None found | – | 71 B | – | no | 2026-11-04 | | PagerTree pagertree.com | None found | – | 48 C | – | no | 2026-11-04 | | Pangolin pangolin.net | None found | – | 66 C | – | no | 2026-11-04 | | Pantheon pantheon.io | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Pathrule pathrule.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Payload payloadcms.com | None found | – | 61 C | – | no | 2026-11-04 | | PgDog pgdog.dev | None found | – | 51 C | – | no | 2026-11-04 | | PicSee picsee.io | Verified no auth | – | | – | not read | 2026-11-04 | | Pipefy pipefy.com | None found | – | 70 B | – | no | 2026-11-04 | | PixelFlow pixelflow.so | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Platform.sh platform.sh | None found | – | 56 C | – | no | 2026-11-04 | | Plori plori.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | not read | 2026-11-04 | | Porkbun porkbun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | – | no | 2026-11-04 | | Port IO port.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | Porter porter.run | None found | – | 73 B | – | no | 2026-11-04 | | Praxim praxim.ai | None found | – | 39 D | – | no | 2026-11-04 | | Probativegrowth probativegrowth.com | Verified no auth | – | | – | not read | 2026-11-04 | | Processmaker processmaker.com | None found | – | 45 D | – | no | 2026-11-04 | | Projectx projectx.cloud | None found | – | 36 D | – | no | 2026-11-04 | | ProLevelMax prolevelmax.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Pulumi pulumi.com | None found | – | 80 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/infrastructure/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Infrastructure, page 3 | Agent MCP Directory" description: "Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Page 3 of 4. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/infrastructure/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Infrastructure, page 3 | Agent MCP Directory > Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Page 3 of 4. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/infrastructure/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infrastructure: MCP servers and CLIs, page 3 303 companies in Infrastructure: 26 listed tools to a client with no credentials, 92 answered with a sign-in challenge (not counted) and 12 have a CLI on record. This page lists rows 201 to 300, from Pylon to Xenition. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows 201 to 300 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Pylon pylonump.com | None found | – | 56 C | – | no | 2026-11-04 | | Qualityclouds qualityclouds.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Railway railway.com | Sign-in required OAuth DCR; tools not seen, not counted | @railway/cli | 89 A | yes | not read | 2026-11-04 | | Rapid7 rapid7.com | None found | – | 62 C | – | no | 2026-11-04 | | Raygun raygun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Redis redis.io | No answer | – | 62 C | – | no | 2026-11-04 | | Relvato relvato.com | Verified no auth | – | | – | not read | 2026-11-04 | | Remote MCP remote-mcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Render render.com | Sign-in required OAuth; tools not seen, not counted | – | 82 B | yes | yes | 2026-11-04 | | Rev rev.com | None found | – | 48 C | – | no | 2026-11-04 | | Rivet rivet.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Robocorp robocorp.com | None found | – | 41 D | – | no | 2026-11-04 | | Rokha rokha.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Rollbar rollbar.com | None found | – | 69 C | – | no | 2026-11-04 | | Rootly rootly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Run run.ai | None found | – | 37 D | – | not read | 2026-11-04 | | RunAnywhere runanywhere.ai | None found | – | 72 B | – | no | 2026-11-04 | | Runcascade runcascade.com | None found | – | 45 D | – | no | 2026-11-04 | | Runpulse runpulse.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Runtrellis runtrellis.com | None found | – | 40 D | – | no | 2026-11-04 | | SAP sap.com | None found | – | 52 C | – | not read | 2026-11-04 | | Scaleway scaleway.com | None found | – | 69 C | – | no | 2026-11-04 | | Scalix Cloud scalix.world | Verified no auth | – | | – | not read | 2026-11-04 | | Scalyr scalyr.com | None found | – | 40 D | – | no | 2026-11-04 | | Scento scento.com | Verified no auth | – | 82 B | – | not read | 2026-11-04 | | Scoutapm scoutapm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | ScreenVerb screenverb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Semaphore semaphoreci.com | None found | – | 49 C | – | no | 2026-11-04 | | Sentry sentry.io | Sign-in required OAuth DCR; tools not seen, not counted | @sentry/cli | 79 B | – | no | 2026-11-04 | | Server4Agent server4agent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SF Tensor sf-tensor.com | None found | – | 38 D | – | no | 2026-11-04 | | Shaped shaped.ai | None found | – | 47 D | – | no | 2026-11-04 | | Sherweb sherweb.com | Sign-in required OAuth; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | ShipStatic shipstatic.com | Verified no auth | – | | – | not read | 2026-11-04 | | Shogun shogun.com | None found | – | 52 C | – | no | 2026-11-04 | | SID AI sid.ai | None found | – | 35 D | – | no | 2026-11-04 | | SimpleBackups simplebackups.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Simvoly simvoly.com | None found | – | 54 C | – | no | 2026-11-04 | | Site24x7 site24x7.com | None found | – | 53 C | – | no | 2026-11-04 | | Sitecore sitecore.com | None found | – | 61 C | – | no | 2026-11-04 | | Sixtyfour sixtyfour.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | SmartBear smartbear.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | smol machines smolmachines.com | None found | – | 80 B | yes | no | 2026-11-04 | | Snorkel AI snorkel.ai | None found | – | 43 D | – | no | 2026-11-04 | | Snyk snyk.io | None found | – | 79 B | – | no | 2026-11-04 | | Softr softr.io | None found | – | 67 C | – | no | 2026-11-04 | | Spike spike.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Split.io split.io | None found | – | 60 C | – | no | 2026-11-04 | | SST sst.dev | None found | – | 63 C | – | no | 2026-11-04 | | Statamic statamic.com | None found | – | 38 D | – | no | 2026-11-04 | | Statsig statsig.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | StatusCake statuscake.com | None found | – | 53 C | – | no | 2026-11-04 | | StatusGator statusgator.com | None found | – | 38 D | – | no | 2026-11-04 | | Statuspage statuspage.io | None found | – | 35 D | – | no | 2026-11-04 | | Stillwind stillwind.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Streamkap streamkap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sumologic sumologic.com | None found | – | 71 B | – | no | 2026-11-04 | | SuperAnnotate superannotate.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 54 C | – | no | 2026-11-04 | | Superb AI superb-ai.com | None found | – | 65 C | – | no | 2026-11-04 | | Supervisely supervisely.com | None found | – | 65 C | – | no | 2026-11-04 | | SuprSend suprsend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Svelte svelte.dev | Verified no auth | – | 58 C | – | not read | 2026-11-04 | | Synth AI usesynth.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Tailscale tailscale.com | None found | – | 69 C | – | no | 2026-11-04 | | Tavus tavus.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Telnyx telnyx.com | Verified no auth | – | 99 A+ | yes | yes | 2026-11-04 | | Temporal temporal.io | None found | – | 61 C | – | no | 2026-11-04 | | Terminal Use terminaluse.com | None found | – | 48 C | – | no | 2026-11-04 | | Texel.ai texel.ai | None found | – | 52 C | – | no | 2026-11-04 | | The Token Company thetokencompany.com | None found | – | 72 B | yes | no | 2026-11-04 | | ThousandEyes thousandeyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | Tilda tilda.cc | None found | – | 49 C | – | no | 2026-11-04 | | Trackjs trackjs.com | None found | – | 55 C | – | no | 2026-11-04 | | Tray.ai tray.io | None found | – | 62 C | – | no | 2026-11-04 | | Truthsystems truthsystems.ai | None found | – | 37 D | – | no | 2026-11-04 | | Turso turso.tech | None found | – | 84 B | yes | no | 2026-11-04 | | Ubicloud ubicloud.com | None found | – | 49 C | – | no | 2026-11-04 | | UiPath uipath.com | None found | – | 62 C | – | no | 2026-11-04 | | updown.io updown.io | None found | – | 33 D | – | no | 2026-11-04 | | Upscrape upscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Upstash upstash.com | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Uptime.com :) uptime.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 59 C | – | no | 2026-11-04 | | UptimeRobot uptimerobot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Upwork upwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | V7labs v7labs.com | None found | – | 72 B | – | no | 2026-11-04 | | Vanta vanta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Vercel vercel.com | Sign-in required OAuth DCR; tools not seen, not counted | vercel | 91 A | yes | no | 2026-11-04 | | VeriTeknik veriteknik.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Virtualmin virtualmin.com | None found | – | 40 D | – | no | 2026-11-04 | | Vultr vultr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | WhyLabs whylabs.ai | None found | – | 47 D | – | no | 2026-11-04 | | Wiz wiz.io | None found | – | 58 C | – | no | 2026-11-04 | | Woodpecker CI woodpecker-ci.org | None found | – | 39 D | – | no | 2026-11-04 | | Workato workato.com | No answer | – | 64 C | – | no | 2026-11-04 | | Wp wp.com | None found | – | 46 D | – | no | 2026-11-04 | | WP Agent getwpagent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WP Engine wpengine.com | None found | – | 68 C | – | no | 2026-11-04 | | WPWriter wpwriter.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WunderGraph wundergraph.com | None found | – | 70 B | – | no | 2026-11-04 | | Xenition xenition.com | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/infrastructure/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Infrastructure, page 4 | Agent MCP Directory" description: "Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Page 4 of 4. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/infrastructure/page/4 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Infrastructure, page 4 | Agent MCP Directory > Infrastructure: 303 companies, 26 with tools listed and 12 with a CLI on record, checked 4 November 2026. Page 4 of 4. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/infrastructure/page/4 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infrastructure: MCP servers and CLIs, page 4 303 companies in Infrastructure: 26 listed tools to a client with no credentials, 92 answered with a sign-in challenge (not counted) and 12 have a CLI on record. This page lists rows 301 to 303, from ZeroDev to Zomato. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows 301 to 303 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | ZeroDev zerodev.app | None found | – | 46 D | – | no | 2026-11-04 | | ZeroEntropy zeroentropy.dev | No answer | – | 73 B | – | no | 2026-11-04 | | Zomato zomato.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 16 F | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/infrastructure/page/4/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Legal & Compliance: MCP servers and CLIs | Agent MCP Directory" description: "Legal & Compliance: 4 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/legal-and-compliance site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Legal & Compliance: MCP servers and CLIs | Agent MCP Directory > Legal & Compliance: 4 companies, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/legal-and-compliance Site: Agent MCP Directory Last reviewed: 2026-11-05 # Legal & Compliance: MCP servers and CLIs 4 companies in Legal & Compliance: 1 listed tools to a client with no credentials, 3 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Beglaubigt to PandaDoc. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Beglaubigt beglaubigt.de | Verified no auth | – | 49 C | – | no | 2026-11-04 | | Common Paper commonpaper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | CookieYes cookieyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | PandaDoc pandadoc.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/legal-and-compliance/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Logistics & Supply Chain: MCP servers and CLIs | Agent MCP Directory" description: "Logistics & Supply Chain: 2 companies, 0 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/logistics-and-supply-chain site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Logistics & Supply Chain: MCP servers and CLIs | Agent MCP Directory > Logistics & Supply Chain: 2 companies, 0 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/logistics-and-supply-chain Site: Agent MCP Directory Last reviewed: 2026-11-05 # Logistics & Supply Chain: MCP servers and CLIs 2 companies in Logistics & Supply Chain: 0 listed tools to a client with no credentials, 2 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Lanesurf to Skydropx. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Lanesurf lanesurf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | yes | no | 2026-11-04 | | Skydropx skydropx.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 41 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/logistics-and-supply-chain/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Marketing: MCP servers and CLIs | Agent MCP Directory" description: "Marketing: 31 companies, 7 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/marketing site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Marketing: MCP servers and CLIs | Agent MCP Directory > Marketing: 31 companies, 7 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/marketing Site: Agent MCP Directory Last reviewed: 2026-11-05 # Marketing: MCP servers and CLIs 31 companies in Marketing: 7 listed tools to a client with no credentials, 24 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Ads Uploader to Wall Marketing. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Ads Uploader adsuploader.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ahrefs ahrefs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | AltoRank altorank.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AppsFlyer appsflyer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | AthenaHQ athenahq.ai | Verified no auth | – | 67 C | – | no | 2026-11-04 | | BlogSEO blogseo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | brainattic brainattic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Chili Piper chilipiper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | Digestseo digestseo.com | Verified no auth | – | | – | not read | 2026-11-04 | | Easyship easyship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Frase frase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 89 A | yes | no | 2026-11-04 | | Kajabi kajabi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | no | 2026-11-04 | | Kragos kragos.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Leadpages leadpages.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | yes | no | 2026-11-04 | | Lodestarindex lodestarindex.com | Verified no auth | – | | – | not read | 2026-11-04 | | Lusha lusha.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Mellow Hub mellow.world | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Pageaudit pageaudit.online | Verified no auth | – | | yes | not read | 2026-11-04 | | Pipeboard pipeboard.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | Quillm quillm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RocketReach rocketreach.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | SendPulse sendpulse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | SEOmatic seomatic.ai | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | Serpstat serpstat.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Shippo shippo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Sitelemetry sitelemetry.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SurfacedBy AI surfacedby.com | Verified no auth | – | | – | not read | 2026-11-04 | | Tapcart tapcart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | Veles getveles.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | VISEON viseon.io | Verified no auth | – | | – | not read | 2026-11-04 | | Wall Marketing wall.marketing | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/marketing/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "News & Intelligence: MCP servers and CLIs | Agent MCP Directory" description: "News & Intelligence: 1 company, 0 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/news-and-intelligence site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # News & Intelligence: MCP servers and CLIs | Agent MCP Directory > News & Intelligence: 1 company, 0 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/news-and-intelligence Site: Agent MCP Directory Last reviewed: 2026-11-05 # News & Intelligence: MCP servers and CLIs 1 company in News & Intelligence: 0 listed tools to a client with no credentials, 1 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from MorningStar to MorningStar. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | MorningStar morningstar.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/news-and-intelligence/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Payments & Fintech: MCP servers and CLIs | Agent MCP Directory" description: "Payments & Fintech: 29 companies, 5 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/payments-and-fintech site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Payments & Fintech: MCP servers and CLIs | Agent MCP Directory > Payments & Fintech: 29 companies, 5 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/payments-and-fintech Site: Agent MCP Directory Last reviewed: 2026-11-05 # Payments & Fintech: MCP servers and CLIs 29 companies in Payments & Fintech: 5 listed tools to a client with no credentials, 23 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from AI Mail MCP to Vike. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | AI Mail MCP aimailmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Beancount.io beancount.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | BeliefState beliefstate.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Bitculator bitculator.com | Credential wall API key | – | | – | not read | 2026-11-04 | | BlindPay blindpay.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Checkout.com checkout.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | CoinMarketCap coinmarketcap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Dodo Payments dodopayments.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | not read | 2026-11-04 | | Easy itseasy.co | Verified no auth | – | 87 A | – | no | 2026-11-04 | | ElevenFlo elevenflo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Forter forter.com | Verified no auth | – | 92 A | yes | no | 2026-11-04 | | Frihet frihet.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | GoCardless gocardless.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | GuruHotel guruhotel.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Kema kema-studio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lezzoo lezzoo.com | Verified no auth | – | 69 C | – | no | 2026-11-04 | | Mercado Pago mercadopago.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Paddle paddle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | PayPal paypal.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Plaid plaid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Ramp ramp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Square square.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 26 F | – | not read | 2026-11-04 | | Square squareup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Stripe stripe.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | TapTax taptax.co.uk | Verified no auth | – | | – | not read | 2026-11-04 | | Tesorio tesorio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | The Bridge thebridge.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Twelve Data twelvedata.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vike vike.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/payments-and-fintech/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Productivity: MCP servers and CLIs | Agent MCP Directory" description: "Productivity: 49 companies, 3 with tools listed and 2 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/productivity site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Productivity: MCP servers and CLIs | Agent MCP Directory > Productivity: 49 companies, 3 with tools listed and 2 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/productivity Site: Agent MCP Directory Last reviewed: 2026-11-05 # Productivity: MCP servers and CLIs 49 companies in Productivity: 3 listed tools to a client with no credentials, 45 answered with a sign-in challenge (not counted) and 2 have a CLI on record. Rows run from Airtable to Zapier. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Airtable airtable.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Akiflow akiflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Alai getalai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Apricot apricot.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Asana asana.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Atlassian atlassian.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Basecamp basecamp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Box box.com | Sign-in required OAuth; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Calendly calendly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Canva canva.com | Sign-in required OAuth DCR; tools not seen, not counted | @canva/cli | 42 D | – | no | 2026-11-04 | | Carbon getcarbon.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Circleback circleback.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Clean Notes cleannotes.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ClickUp clickup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Cogram cogram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Craft craft.do | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Dart dartai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | yes | 2026-11-04 | | DocSpring docspring.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fathom fathom.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | Figma figma.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Find-A-Domain findadomain.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Fireflies.ai fireflies.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Gamma gamma.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | IFTTT ifttt.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Linear linear.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Listenetic listenetic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Luw.ai luw.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Make make.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Miro miro.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | monday monday.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | yes | 2026-11-04 | | Mural mural.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Notion notion.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | – | no | 2026-11-04 | | Notion notion.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | ONES ones.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | OpenWork openworklabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | Orangescrum orangescrum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | Otter.ai otter.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Pally pally.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | Parad1gm parad1gm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PatchDesign.AI patchdesign.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Sequencer sequencer.media | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SimplePDF simplepdf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | yes | no | 2026-11-04 | | Tallyfy tallyfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Todoist todoist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Typeform typeform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | WayStation waystation.ai | No answer | – | | – | not read | 2026-11-04 | | Whimsical whimsical.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | | Wolfram wolfram.com | Verified no auth | – | | – | no | 2026-11-04 | | Zapier zapier.com | Sign-in required OAuth DCR; tools not seen, not counted | zapier-platform-cli | 84 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/productivity/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Real Estate & Construction: MCP servers | Agent MCP Directory" description: "Real Estate & Construction: 1 company, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/real-estate-and-construction site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Real Estate & Construction: MCP servers | Agent MCP Directory > Real Estate & Construction: 1 company, 1 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/real-estate-and-construction Site: Agent MCP Directory Last reviewed: 2026-11-05 # Real Estate & Construction: MCP servers and CLIs 1 company in Real Estate & Construction: 1 listed tools to a client with no credentials, 0 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Autodesk to Autodesk. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Autodesk autodesk.com | Verified no auth | – | 36 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/real-estate-and-construction/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Security: MCP servers and CLIs | Agent MCP Directory" description: "Security: 10 companies, 4 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/security site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Security: MCP servers and CLIs | Agent MCP Directory > Security: 10 companies, 4 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/security Site: Agent MCP Directory Last reviewed: 2026-11-05 # Security: MCP servers and CLIs 10 companies in Security: 4 listed tools to a client with no credentials, 5 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from Ansvar to Zenable. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Ansvar ansvar.eu | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Casco casco.com | Verified no auth | – | 41 D | – | no | 2026-11-04 | | Checkmarx checkmarx.com | None found | – | 61 C | – | no | 2026-11-04 | | DMCA.com dmca.com | Verified no auth | – | | – | no | 2026-11-04 | | FlightQueue flightqueue.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Formasty formasty.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | JobsPipe jobspipe.dev | Verified no auth | – | 96 A+ | yes | not read | 2026-11-04 | | PensionHunter pensionhunter.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Prembly prembly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Zenable zenable.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/security/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Travel & Hospitality: MCP servers and CLIs | Agent MCP Directory" description: "Travel & Hospitality: 5 companies, 2 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/travel-and-hospitality site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Travel & Hospitality: MCP servers and CLIs | Agent MCP Directory > Travel & Hospitality: 5 companies, 2 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/travel-and-hospitality Site: Agent MCP Directory Last reviewed: 2026-11-05 # Travel & Hospitality: MCP servers and CLIs 5 companies in Travel & Hospitality: 2 listed tools to a client with no credentials, 3 answered with a sign-in challenge (not counted) and 0 have a CLI on record. Rows run from FlightSeatMap to trivago. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | FlightSeatMap flightseatmap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | FlyBest flybest.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PAVE pavecfi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Paytm paytm.com | Verified no auth | – | 52 C | – | no | 2026-11-04 | | trivago trivago.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/travel-and-hospitality/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Uncategorised: MCP servers and CLIs | Agent MCP Directory" description: "Uncategorised: 201 companies, 91 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry." canonical: https://agentmcpdirectory.com/directory/category/uncategorised site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Uncategorised: MCP servers and CLIs | Agent MCP Directory > Uncategorised: 201 companies, 91 with tools listed and 0 with a CLI on record, checked 4 November 2026. Endpoint, auth type and tools on each entry. Source: https://agentmcpdirectory.com/directory/category/uncategorised Site: Agent MCP Directory Last reviewed: 2026-11-05 # Uncategorised: MCP servers and CLIs 201 companies in Uncategorised: 91 listed tools to a client with no credentials, 97 answered with a sign-in challenge (not counted) and 0 have a CLI on record. This page lists rows 1 to 100, from 2extract to LLM Pulse. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 2extract 2extract.com | Verified no auth | – | | – | not read | 2026-11-04 | | Adkit adkit.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | Agent Ready agent-ready.dev | Verified no auth | – | 94 A | yes | yes | 2026-11-04 | | Alidns alidns.com | None found | – | | – | no | 2026-11-04 | | Almxpp almxpp.com | Verified no auth | – | | yes | not read | 2026-11-04 | | amCharts amcharts.com | Verified no auth | – | | – | not read | 2026-11-04 | | Anurag anuragd.me | Verified no auth | – | 54 C | – | not read | 2026-11-04 | | Appllama appllama.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 44 D | – | not read | 2026-11-04 | | Arcmira arcmira.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Arkm arkm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Arrumou arrumou.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Avalara avalara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | not read | 2026-11-04 | | aVenture aventure.vc | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | not read | 2026-11-04 | | Ball Ranks ballranks.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Barevalue barevalue.com | Verified no auth | – | | – | not read | 2026-11-04 | | Baserow baserow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | BGPT bgpt.pro | Verified no auth | – | | – | not read | 2026-11-04 | | BittleBits bittlebits.ai | No answer | – | | – | not read | 2026-11-04 | | Bugasura bugasura.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | not read | 2026-11-04 | | BulkPublish bulkpublish.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | BuyWhere buywhere.ai | Verified no auth | – | | yes | not read | 2026-11-04 | | call4me call4.me | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Carrick carrick.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Catalystproject catalystproject.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Celigo celigo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | not read | 2026-11-04 | | Charming charm.ing | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | yes | not read | 2026-11-04 | | Chatway chatway.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Clino clino.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Clutch.co clutch.co | Verified no auth | – | 21 F | – | no | 2026-11-04 | | Codex Reset codex-reset.com | Verified no auth | – | | yes | not read | 2026-11-04 | | CometChat cometchat.com | Verified no auth | – | 56 C | – | not read | 2026-11-04 | | Context Awesome context-awesome.com | Verified no auth | – | | – | not read | 2026-11-04 | | COROS coros.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | | CryptoAPIs IO cryptoapis.io | Verified no auth | – | | – | not read | 2026-11-04 | | CustomGPT.ai customgpt.ai | No answer | – | | – | not read | 2026-11-04 | | Dappier dappier.com | No answer | – | | – | not read | 2026-11-04 | | Deed deed.page | Verified no auth | – | | yes | not read | 2026-11-04 | | DeepWiki deepwiki.com | Verified no auth | – | | – | not read | 2026-11-04 | | Designesy designesy.org | Verified no auth | – | | – | not read | 2026-11-04 | | Devin devin.ai | Verified no auth | – | 67 C | yes | not read | 2026-11-04 | | Divblox divblox.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dreamwork dreamworkhq.com | Verified no auth | – | | – | not read | 2026-11-04 | | DropTheHassle dropthehassle.com | Verified no auth | – | | – | not read | 2026-11-04 | | DSers dsers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dueback dueback.co | Verified no auth | – | | – | not read | 2026-11-04 | | EAN-Search.org ean-search.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | EasyGerber easygerber.com | Verified no auth | – | | – | not read | 2026-11-04 | | emem emem.dev | Verified no auth | – | 85 B | – | not read | 2026-11-04 | | Eodly eodly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | not read | 2026-11-04 | | eResource Scheduler eresourcescheduler.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | EveryCalc everycalc.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | FairValid fairvalid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Faxforagents faxforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | Ferryhopper ferryhopper.com | Verified no auth | – | | – | not read | 2026-11-04 | | FinancialFilings financialfilings.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flowra flowra.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Follore follore.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | FullEnrich fullenrich.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | not read | 2026-11-04 | | Fund Momentum fundmomentum.vc | Verified no auth | – | | yes | not read | 2026-11-04 | | fynk fynk.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | | Gaipagents gaipagents.com | Verified no auth | – | | yes | not read | 2026-11-04 | | GenMagic genmagic.co | Verified no auth | – | | yes | not read | 2026-11-04 | | GetMattered getmattered.com | Verified no auth | – | | – | not read | 2026-11-04 | | Gomdori gomdori.app | Verified no auth | – | | – | not read | 2026-11-04 | | Google Cloud googleapis.com | Verified no auth | – | | – | no | 2026-11-04 | | GoSQLX gosqlx.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Granola granola.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Graphify graphify.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | Gryz gryz.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Hands for Agents handsforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | Hcti hcti.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Healthline healthline.com | None found | – | 75 B | – | no | 2026-11-04 | | Helena helena.bio | Verified no auth | – | | – | not read | 2026-11-04 | | HemmaBo hemmabo.com | Verified no auth | – | | – | not read | 2026-11-04 | | Hermoso hermoso.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Hive Intelligence hiveintelligence.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | Hookpulse hookpulse.net | Verified no auth | – | | yes | not read | 2026-11-04 | | HVTracker hvtracker.net | Verified no auth | – | | – | not read | 2026-11-04 | | HYPD AI hypd.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | Hyperresearch hyperresearch.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | not read | 2026-11-04 | | iDevice idevice.com | Verified no auth | – | | – | not read | 2026-11-04 | | Inamprotocol inamprotocol.org | Verified no auth | – | | – | not read | 2026-11-04 | | Indeed indeed.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 25 F | – | no | 2026-11-04 | | IndustryLens industry-lens.com | Verified no auth | – | | – | not read | 2026-11-04 | | Invideo invideo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 54 C | – | not read | 2026-11-04 | | ISMS Copilot ismscopilot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | yes | not read | 2026-11-04 | | Isonavigator isonavigator.io | Verified no auth | – | | – | not read | 2026-11-04 | | Isto Intents istointents.com | Verified no auth | – | | – | not read | 2026-11-04 | | JANCTION janction.jp | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Jotform jotform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Kiln kiln3d.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kraken kraken.com | Verified no auth | – | 82 B | yes | no | 2026-11-04 | | Kujolang.ai kujolang.ai | Verified no auth | – | 55 C | – | not read | 2026-11-04 | | Lambdatest lambdatest.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Lazaretto lazaretto.dev | Verified no auth | – | | yes | not read | 2026-11-04 | | Lazybird lazybird.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Leash lea.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Liquilens liquilens.in | Verified no auth | – | 72 B | – | not read | 2026-11-04 | | LiveScore MCP livescoremcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | LLM Pulse llmpulse.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/uncategorised/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Uncategorised, page 2 | Agent MCP Directory" description: "Uncategorised: 201 companies, 91 with tools listed and 0 with a CLI on record, checked 4 November 2026. Page 2 of 3. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/uncategorised/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Uncategorised, page 2 | Agent MCP Directory > Uncategorised: 201 companies, 91 with tools listed and 0 with a CLI on record, checked 4 November 2026. Page 2 of 3. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/uncategorised/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Uncategorised: MCP servers and CLIs, page 2 201 companies in Uncategorised: 91 listed tools to a client with no credentials, 97 answered with a sign-in challenge (not counted) and 0 have a CLI on record. This page lists rows 101 to 200, from Llmtxt to XMemo. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Llmtxt llmtxt.dev | No answer | – | | – | not read | 2026-11-04 | | Longbridge longbridge.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | not read | 2026-11-04 | | Macfax macfax.com | Verified no auth | – | | – | not read | 2026-11-04 | | Mailrith mailrith.com | Verified no auth | – | 97 A+ | yes | not read | 2026-11-04 | | Manifold manifold.markets | Verified no auth | – | | – | not read | 2026-11-04 | | Mapbox mapbox.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | MAQAMI maqami.co | Verified no auth | – | | – | not read | 2026-11-04 | | Market Eyes Live marketeyeslive.com | Verified no auth | – | | – | not read | 2026-11-04 | | MCP Telegram mcp-telegram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | MedicalNewsToday medicalnewstoday.com | None found | – | 75 B | – | no | 2026-11-04 | | Mercado Libre mercadolibre.com | No answer | – | 40 D | – | no | 2026-11-04 | | Microsoft 365 cloud.microsoft | Sign-in required OAuth; tools not seen, not counted | – | | – | no | 2026-11-04 | | Mnemoverse mnemoverse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | MotionSpec motionspec.dev | Verified no auth | – | | – | not read | 2026-11-04 | | mypromind mypromind.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Needle needle-ai.com | No answer | – | | – | not read | 2026-11-04 | | NegativeEV negativeev.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Netdata netdata.cloud | Credential wall API key | – | | – | not read | 2026-11-04 | | Nomas nomas.fyi | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Nslookup nslookup.io | Verified no auth | – | | – | not read | 2026-11-04 | | Nuxt nuxt.com | No answer | – | 79 B | yes | no | 2026-11-04 | | Oakallow oakallow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Obolusfinanz obolusfinanz.de | Verified no auth | – | | – | not read | 2026-11-04 | | Octagon octagonai.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | OctoPerf octoperf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | Omnidim omnidim.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | yes | not read | 2026-11-04 | | OneContext onecontext.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | OpenAccountants openaccountants.com | Verified no auth | – | 64 C | – | not read | 2026-11-04 | | OpenMesh openmesh.dev | No answer | – | | – | not read | 2026-11-04 | | Optionsahoy optionsahoy.com | Verified no auth | – | | yes | not read | 2026-11-04 | | OpusClip opus.pro | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | PaidSync.ai paidsync.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | PakBus pakbus.app | Verified no auth | – | | – | not read | 2026-11-04 | | Pith pith.day | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | POEditor poeditor.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Posy posy.page | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Process Street process.st | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | Prompeteer prompeteer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Publora publora.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Pulse thepulse.markets | Verified no auth | – | | – | not read | 2026-11-04 | | Pushary pushary.com | Verified no auth | – | 79 B | – | not read | 2026-11-04 | | Quorum AI quorum.dog | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Rankability rankability.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | Rapier rapier.website | Verified no auth | – | | – | not read | 2026-11-04 | | Read AI read.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | RegEvidenceHub regevidencehub.com | Verified no auth | – | | – | not read | 2026-11-04 | | ReplyOnTheFly replyonthefly.com | Verified no auth | – | | – | not read | 2026-11-04 | | RoboSystems robosystems.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rocketship deployrocketship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rta rta.lat | Verified no auth | – | | – | not read | 2026-11-04 | | Runcomfy runcomfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Saifs saifs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SanctionsKit sanctionskit.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Scavio scavio.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scholar Sidekick scholar-sidekick.com | Verified no auth | – | 98 A+ | yes | not read | 2026-11-04 | | Scorecard scorecard.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Screenforge screenforge.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Search Fragments searchfragments.com | Verified no auth | – | | – | not read | 2026-11-04 | | Sendmux sendmux.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | – | not read | 2026-11-04 | | Sentry sentry.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | SerpApi serpapi.com | Verified no auth | – | 59 C | – | not read | 2026-11-04 | | Servicebricks servicebricks.com | No answer | – | | – | not read | 2026-11-04 | | Short.io short.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Since.dev since.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SkillDB skilldb.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SlideForge slideforge.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Socialync socialync.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Spacefast spacefast.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | not read | 2026-11-04 | | Spicrawl spicrawl.com | Verified no auth | – | | – | not read | 2026-11-04 | | Steellantern steellantern.com | Verified no auth | – | | – | not read | 2026-11-04 | | SubwayInfo NYC subwayinfo.nyc | Verified no auth | – | | yes | not read | 2026-11-04 | | Symbioza symbioza.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | TakeMeUp.cv takemeup.cv | Verified no auth | – | | – | not read | 2026-11-04 | | Taplio taplio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Taxapp taxapp.nz | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | TempGuru tempguru.co | Verified no auth | – | | – | not read | 2026-11-04 | | The Brains brains.ceo | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | The White Report thewhitereport.com | Verified no auth | – | | – | not read | 2026-11-04 | | tl;dv tldv.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | not read | 2026-11-04 | | Todoist todoist.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Tomiseregi tomiseregi.si | Verified no auth | – | | – | not read | 2026-11-04 | | Treza trezalabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Turkishtechlab turkishtechlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | TweetSave tweetsave.org | Verified no auth | – | | – | not read | 2026-11-04 | | txscribe txscribe.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Uizze uizze.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ultralayer ultralayer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Usercentrics usercentrics.eu | Verified no auth | – | | – | yes | 2026-11-04 | | UXKIN uxkin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Valkyrlabs valkyrlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Veridu veridu.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | VibeMarketing vibemarketing.ninja | Verified no auth | – | | – | not read | 2026-11-04 | | Viridisconservation viridisconservation.com | Verified no auth | – | | – | not read | 2026-11-04 | | Vybenetwork vybenetwork.com | Verified no auth | – | | – | not read | 2026-11-04 | | Watchgoose watchgoose.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | yes | not read | 2026-11-04 | | WebZum webzum.com | Verified no auth | – | | – | not read | 2026-11-04 | | WhitePact whitepact.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WITAN Markets witan.markets | Verified no auth | – | | yes | not read | 2026-11-04 | | WRDO wrdo.co.za | Verified no auth | – | 48 C | – | not read | 2026-11-04 | | XMemo xmemo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/uncategorised/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Uncategorised, page 3 | Agent MCP Directory" description: "Uncategorised: 201 companies, 91 with tools listed and 0 with a CLI on record, checked 4 November 2026. Page 3 of 3. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/category/uncategorised/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Uncategorised, page 3 | Agent MCP Directory > Uncategorised: 201 companies, 91 with tools listed and 0 with a CLI on record, checked 4 November 2026. Page 3 of 3. Dated and sourced. Source: https://agentmcpdirectory.com/directory/category/uncategorised/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Uncategorised: MCP servers and CLIs, page 3 201 companies in Uncategorised: 91 listed tools to a client with no credentials, 97 answered with a sign-in challenge (not counted) and 0 have a CLI on record. This page lists rows 201 to 201, from Zip1 to Zip1. Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. ## Rows 201 to 201 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Zip1 zip1.io | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/category/uncategorised/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Causely MCP server | Agent MCP Directory" description: "Causely: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/causely-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Causely MCP server | Agent MCP Directory > Causely: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/causely-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Causely: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Causely at api.causely.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Causely | | --- | --- | | Domain | causely.app | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for causely.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.causely.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 530 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:49Z https://api.causely.app/mcp sent initialize result auth-required (HTTP 401) 748 ms - 20:02:21Z https://api.causely.app/mcp sent initialize result auth-required (HTTP 401) 530 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.causely.app/.well-known/oauth-protected-resource/mcp" scope="openid profile email" | | Protected resource metadata | api.causely.app | | Authorization server metadata | api.causely.app | | Registration endpoint | https://api.causely.app/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://api.causely.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.causely.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.causely.app/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Causely. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.causely/causely | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/causely-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=causely), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cavyro MCP server | Agent MCP Directory" description: "Cavyro: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/cavyro-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cavyro MCP server | Agent MCP Directory > Cavyro: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/cavyro-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cavyro: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Cavyro at ai.cavyro.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Cavyro | | --- | --- | | Domain | cavyro.com | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | 73, grade B; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cavyro.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.cavyro.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 617 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:50Z https://ai.cavyro.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 675 ms - 20:02:21Z https://ai.cavyro.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 617 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | Bearer realm="cavyro" | ### The sign-in route, step by step 1. Request `https://ai.cavyro.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cavyro. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: cavyro.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.cavyro/cavyro | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cavyro-com/index.md) ## Sources - [Ora score page for cavyro.com](https://ora.ai/score/cavyro.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cavyro), read 4 November 2026 - [Cavyro website](https://cavyro.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cedana MCP server | Agent MCP Directory" description: "Does Cedana have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cedana-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cedana MCP server | Agent MCP Directory > Does Cedana have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cedana-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cedana: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cedana (cedana.ai), so the connector had nothing to connect to. Ora's cached score for cedana.ai is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cedana (registry title: cedana.ai) | | --- | --- | | Domain | cedana.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cedana.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cedana. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cedana.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cedana. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cedana-ai/index.md) ## Sources - [Ora score page for cedana.ai](https://ora.ai/score/cedana.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Cedana was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cedana website](https://cedana.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cekura MCP server | Agent MCP Directory" description: "Does Cekura have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cekura-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cekura MCP server | Agent MCP Directory > Does Cekura have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cekura-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cekura: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cekura (cekura.ai), so the connector had nothing to connect to. Ora's cached score for cekura.ai is 82, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cekura (registry title: cekura.ai) | | --- | --- | | Domain | cekura.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 82, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cekura.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cekura. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cekura.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cekura. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cekura-ai/index.md) ## Sources - [Ora score page for cekura.ai](https://ora.ai/score/cekura.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Cekura was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cekura website](https://cekura.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Celigo MCP server | Agent MCP Directory" description: "Celigo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/celigo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Celigo MCP server | Agent MCP Directory > Celigo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/celigo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Celigo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Celigo at api.integrator.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Celigo | | --- | --- | | Domain | celigo.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 79, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for celigo.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.integrator.io/celigo-mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,379 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://api.integrator.io/celigo-mcp sent initialize result auth-required (HTTP 401) 1625 ms - 20:02:22Z https://api.integrator.io/celigo-mcp sent initialize result auth-required (HTTP 401) 1379 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.integrator.io/.well-known/oauth-protected-resource/celigo-mcp", scope="mcp:read mcp:write offline_access" | | Protected resource metadata | api.integrator.io | | Authorization server metadata | integrator.io | | Registration endpoint | https://integrator.io/oidc/reg | ### The sign-in route, step by step 1. Request `https://api.integrator.io/celigo-mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.integrator.io/.well-known/oauth-protected-resource/celigo-mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://integrator.io/oidc/reg` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Celigo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.celigo/celigo | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/celigo-com/index.md) ## Sources - [Ora score page for celigo.com](https://ora.ai/score/celigo.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=celigo), read 4 November 2026 - [Celigo website](https://celigo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cerebrium MCP server | Agent MCP Directory" description: "Cerebrium has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cerebrium-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cerebrium MCP server | Agent MCP Directory > Cerebrium has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cerebrium-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cerebrium: MCP server, CLI and agent surfaces Yes: Cerebrium runs a public MCP server at cerebrium.ai that listed 3 tools to a client with no credentials on 4 November 2026. Examples: search\_cerebrium, query\_docs\_filesystem\_cerebrium, submit\_feedback. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for cerebrium.ai is 86, grade A, read on 5 November 2026. ## Fact sheet | Company | Cerebrium (registry title: Cerebrium Docs) | | --- | --- | | Domain | cerebrium.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 86, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cerebrium.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://cerebrium.ai/docs/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Cerebrium 1.0.0 | | Capabilities | tools, resources | | Tools | 3 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,831 ms over 1 attempt | ### Tools listed 3 tools - search\_cerebrium - query\_docs\_filesystem\_cerebrium - submit\_feedback ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://cerebrium.ai/docs/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1860 ms - 20:02:23Z https://cerebrium.ai/docs/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1831 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://cerebrium.ai/docs/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cerebrium. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: cerebrium.ai/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: cerebrium.ai/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.cerebrium/docs | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cerebrium-ai/index.md) ## Sources - [Ora score page for cerebrium.ai](https://ora.ai/score/cerebrium.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Cerebrium was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.cerebrium%2Fdocs), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cerebrium), read 4 November 2026 - [Cerebrium website](https://cerebrium.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CertScore.ai MCP server | Agent MCP Directory" description: "CertScore.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/certscore-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CertScore.ai MCP server | Agent MCP Directory > CertScore.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/certscore-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # CertScore.ai: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for CertScore.ai at mcp.certscore.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | CertScore.ai (registry title: CertScore.ai MCP Light) | | --- | --- | | Domain | certscore.ai | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for certscore.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.certscore.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 760 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://mcp.certscore.ai/mcp sent initialize result auth-required (HTTP 401) 1674 ms - 20:02:22Z https://mcp.certscore.ai/mcp sent initialize result auth-required (HTTP 401) 760 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.certscore.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.certscore.ai | | Authorization server metadata | certscore.ai | | Registration endpoint | https://certscore.ai/api/v2/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.certscore.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.certscore.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://certscore.ai/api/v2/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CertScore.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.certscore/mcp, ai.certscore/mcp-light | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/certscore-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=certscore), read 4 November 2026 - [CertScore.ai website](https://certscore.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Chainstack MCP server | Agent MCP Directory" description: "Chainstack has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/chainstack-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chainstack MCP server | Agent MCP Directory > Chainstack has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/chainstack-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chainstack: MCP server, CLI and agent surfaces Yes: Chainstack runs a public MCP server at mcp.chainstack.com that listed 23 tools to a client with no credentials on 4 November 2026. Examples: get\_organization, get\_deployment\_options, list\_projects. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for chainstack.com is 71, grade B, read on 5 November 2026. ## Fact sheet | Company | Chainstack | | --- | --- | | Domain | chainstack.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 71, grade B; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for chainstack.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.chainstack.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Chainstack 1.12.0 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 23 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,539 ms over 1 attempt | ### Tools listed 23 tools - get\_organization - get\_deployment\_options - list\_projects - create\_project - list\_nodes - get\_node - create\_node - get\_project - update\_project - delete\_project - update\_node - delete\_node - list\_node\_access\_rules - create\_node\_access\_rule - update\_node\_access\_rule - delete\_node\_access\_rule - set\_node\_access\_rules\_status - search\_docs - get\_doc\_page - get\_platform\_status - contact\_chainstack - request\_testnet\_funds - get\_chainstack\_pricing ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://mcp.chainstack.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1715 ms - 20:02:23Z https://mcp.chainstack.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1539 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.chainstack.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Chainstack. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.chainstack/chainstack | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/chainstack-com/index.md) ## Sources - [Ora score page for chainstack.com](https://ora.ai/score/chainstack.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=chainstack), read 4 November 2026 - [Chainstack website](https://chainstack.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Charming MCP server | Agent MCP Directory" description: "Charming: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/charm-ing site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Charming MCP server | Agent MCP Directory > Charming: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/charm-ing Site: Agent MCP Directory Last reviewed: 2026-11-05 # Charming: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Charming at charm.ing answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Charming | | --- | --- | | Domain | charm.ing | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 82, grade B; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for charm.ing, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://charm.ing/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,128 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://charm.ing/mcp sent initialize result auth-required (HTTP 401) 1524 ms - 20:02:23Z https://charm.ing/mcp sent initialize result auth-required (HTTP 401) 1128 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://charm.ing/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | charm.ing | | Authorization server metadata | charm.ing | | Registration endpoint | https://charm.ing/api/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://charm.ing/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://charm.ing/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://charm.ing/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Charming. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: charm.ing (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/charm-ing/index.md) ## Sources - [Ora score page for charm.ing](https://ora.ai/score/charm.ing?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/score) - [Charming website](https://charm.ing), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Chatfuel MCP server | Agent MCP Directory" description: "Chatfuel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/chatfuel-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chatfuel MCP server | Agent MCP Directory > Chatfuel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/chatfuel-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chatfuel: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Chatfuel at mcp.chatfuel.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Chatfuel | | --- | --- | | Domain | chatfuel.com | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for chatfuel.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.chatfuel.com/panel | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,379 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://mcp.chatfuel.com/panel sent initialize result auth-required (HTTP 401) 1391 ms - 20:02:24Z https://mcp.chatfuel.com/panel sent initialize result auth-required (HTTP 401) 1379 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.chatfuel.com/.well-known/oauth-protected-resource/panel", scope="chatfuel" | | Protected resource metadata | mcp.chatfuel.com | | Authorization server metadata | panel.chatfuel.com | | Registration endpoint | https://panel.chatfuel.com/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.chatfuel.com/panel` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.chatfuel.com/.well-known/oauth-protected-resource/panel` to find the authorization server. 3. Register a client at the registration endpoint `https://panel.chatfuel.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Chatfuel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.chatfuel/chatfuel, com.chatfuel/chatfuel-api | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/chatfuel-com/index.md) ## Sources - [Ora score page for chatfuel.com](https://ora.ai/score/chatfuel.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Chatfuel was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.chatfuel%2Fchatfuel), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=chatfuel), read 4 November 2026 - [Chatfuel website](https://chatfuel.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Chatway MCP server | Agent MCP Directory" description: "Chatway: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/chatway-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chatway MCP server | Agent MCP Directory > Chatway: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/chatway-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chatway: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Chatway at mcp.chatway.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Chatway (registry title: Chatway Live Chat) | | --- | --- | | Domain | chatway.app | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for chatway.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.chatway.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,081 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:52Z https://mcp.chatway.app/mcp sent initialize result auth-required (HTTP 401) 1566 ms - 20:02:24Z https://mcp.chatway.app/mcp sent initialize result auth-required (HTTP 401) 1081 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.chatway.app/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.chatway.app | | Authorization server metadata | mcp.chatway.app | | Registration endpoint | https://mcp.chatway.app/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.chatway.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.chatway.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.chatway.app/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Chatway. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/chatway-app/index.md) ## Sources - [Chatway website](https://chatway.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Checkmarx MCP server | Agent MCP Directory" description: "Does Checkmarx have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/checkmarx-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Checkmarx MCP server | Agent MCP Directory > Does Checkmarx have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/checkmarx-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Checkmarx: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Checkmarx (checkmarx.com), so the connector had nothing to connect to. Ora's cached score for checkmarx.com is 61, grade C, read on 5 November 2026. The company was added from the GitHub MCP Registry. ## Fact sheet | Company | Checkmarx | | --- | --- | | Domain | checkmarx.com | | Category | Security (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for checkmarx.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Checkmarx. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for checkmarx.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (com.checkmarx/checkmarx) | | GitHub MCP Registry | Listed | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Checkmarx. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: checkmarx.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.checkmarx/checkmarx | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/checkmarx-com/index.md) ## Sources - [Ora score page for checkmarx.com](https://ora.ai/score/checkmarx.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=checkmarx), read 4 November 2026 - [Checkmarx website](https://checkmarx.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Checkout.com MCP server | Agent MCP Directory" description: "Checkout.com: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/checkout-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Checkout.com MCP server | Agent MCP Directory > Checkout.com: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/checkout-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Checkout.com: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Checkout.com at mcp.checkout.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Checkout.com | | --- | --- | | Domain | checkout.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 9,661 on the list of 4 November 2026 | | Ora score | 73, grade B; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for checkout.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.checkout.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,089 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:15Z https://mcp.checkout.com sent initialize result auth-required (HTTP 401) 809 ms - 20:01:54Z https://mcp.checkout.com sent initialize result auth-required (HTTP 401) 1089 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.checkout.com | | Authorization server metadata | access.mcp.checkout.com | | Registration endpoint | https://access.mcp.checkout.com/payment-operations/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.checkout.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.checkout.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://access.mcp.checkout.com/payment-operations/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Checkout.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/checkout-com/index.md) ## Sources - [Ora score page for checkout.com](https://ora.ai/score/checkout.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/score) - [Checkout.com website](https://checkout.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Chili Piper MCP server | Agent MCP Directory" description: "Chili Piper: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/chilipiper-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chili Piper MCP server | Agent MCP Directory > Chili Piper: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/chilipiper-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chili Piper: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Chili Piper at fire.chilipiper.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Chili Piper | | --- | --- | | Domain | chilipiper.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 48, grade C; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for chilipiper.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://fire.chilipiper.com/api/fire-edge/v1/org/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 698 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://fire.chilipiper.com/api/fire-edge/v1/org/mcp sent initialize result auth-required (HTTP 401) 774 ms - 20:02:23Z https://fire.chilipiper.com/api/fire-edge/v1/org/mcp sent initialize result auth-required (HTTP 401) 698 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://fire.chilipiper.com/api/fire-edge/v1/org/mcp/.well-known/oauth-protected-resource" | | Protected resource metadata | fire.chilipiper.com | | Authorization server metadata | fire.chilipiper.com | | Registration endpoint | https://fire.chilipiper.com/api/fire-edge/v1/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://fire.chilipiper.com/api/fire-edge/v1/org/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://fire.chilipiper.com/api/fire-edge/v1/org/mcp/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://fire.chilipiper.com/api/fire-edge/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Chili Piper. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.chilipiper/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/chilipiper-com/index.md) ## Sources - [Ora score page for chilipiper.com](https://ora.ai/score/chilipiper.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/leaderboard) - [Where Chili Piper was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.chilipiper%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=chilipiper), read 4 November 2026 - [Chili Piper website](https://chilipiper.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Chonkie MCP server | Agent MCP Directory" description: "Chonkie has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/chonkie-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chonkie MCP server | Agent MCP Directory > Chonkie has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/chonkie-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chonkie: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Chonkie; the connector tried mcp.chonkie.ai as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: CERT\_HAS\_EXPIRED. Ora's cached score for chonkie.ai is 43, grade D, read on 5 November 2026. ## Fact sheet | Company | Chonkie (registry title: chonkie.ai) | | --- | --- | | Domain | chonkie.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 43, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for chonkie.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.chonkie.ai/mcp | | --- | --- | | How it was found | mcp.chonkie.ai was tried as a guess and did not answer | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 158 ms over 1 attempt | | Result | CERT_HAS_EXPIRED | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:52Z https://mcp.chonkie.ai/mcp sent initialize result no-answer 433 ms - 20:02:24Z https://mcp.chonkie.ai/mcp sent initialize result no-answer 158 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.chonkie.ai/mcp`. The connector could not tell what it wants: CERT\_HAS\_EXPIRED. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Chonkie. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/chonkie-ai/index.md) ## Sources - [Ora score page for chonkie.ai](https://ora.ai/score/chonkie.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Chonkie was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Chonkie website](https://chonkie.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Chronosphere MCP server | Agent MCP Directory" description: "Does Chronosphere have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/chronosphere-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chronosphere MCP server | Agent MCP Directory > Does Chronosphere have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/chronosphere-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chronosphere: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Chronosphere (chronosphere.io), so the connector had nothing to connect to. Ora's cached score for chronosphere.io is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Chronosphere (registry title: chronosphere.io) | | --- | --- | | Domain | chronosphere.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 13 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for chronosphere.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Chronosphere. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for chronosphere.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Chronosphere. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: chronosphere.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/chronosphere-io/index.md) ## Sources - [Ora score page for chronosphere.io](https://ora.ai/score/chronosphere.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 13 October 2026, read from GET /api/leaderboard) - [Where Chronosphere was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Chronosphere website](https://chronosphere.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ciphyr MCP server | Agent MCP Directory" description: "Ciphyr has an open MCP server with 112 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ciphyr-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ciphyr MCP server | Agent MCP Directory > Ciphyr has an open MCP server with 112 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ciphyr-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ciphyr: MCP server, CLI and agent surfaces Yes: Ciphyr runs a public MCP server at agentmart.ciphyr.ai that listed 112 tools to a client with no credentials on 4 November 2026. Examples: create\_passport, whoami, invite\_agent. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Ciphyr (registry title: AgentMart) | | --- | --- | | Domain | ciphyr.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for ciphyr.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agentmart.ciphyr.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | agentmart 1.4.0 | | Capabilities | tools, resources | | Tools | 112 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,352 ms over 1 attempt | ### Tools listed 112 tools; the first 40 names are recorded - create\_passport - whoami - invite\_agent - join\_owner - list\_passports - remove\_passport - confirm\_owner\_email - leave\_owner - rotate\_token - revoke\_passport - search\_catalog - get\_item - top\_up - top\_up\_status - buy - get\_order - list\_orders - list\_jobs - get\_job - answer\_job\_question - verify\_job\_sites - quote\_human\_service - cancel\_job - accept\_job - dispute\_job - check\_emails - get\_email\_check - list\_email\_checks - new\_download\_link - list\_utilities - get\_utility - inbox\_messages - inbox\_ack - inbox\_delete - locker\_put - locker\_get - locker\_list - locker\_delete - wakeup\_schedule - wakeup\_list ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:54Z https://agentmart.ciphyr.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1478 ms - 20:02:25Z https://agentmart.ciphyr.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1352 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://agentmart.ciphyr.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ciphyr. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.ciphyr.agentmart/agentmart, ai.ciphyr.agentmart/core | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ciphyr-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ciphyr), read 4 November 2026 - [Ciphyr website](https://ciphyr.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Circleback MCP server | Agent MCP Directory" description: "Circleback: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/circleback-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Circleback MCP server | Agent MCP Directory > Circleback: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/circleback-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Circleback: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Circleback at circleback.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Circleback | | --- | --- | | Domain | circleback.ai | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 76, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for circleback.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://circleback.ai/api/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,023 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:53Z https://circleback.ai/api/mcp sent initialize result auth-required (HTTP 401) 1106 ms - 20:02:25Z https://circleback.ai/api/mcp sent initialize result auth-required (HTTP 401) 1023 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://circleback.ai/.well-known/oauth-protected-resource/api/mcp", scope="user user:write" | | Protected resource metadata | circleback.ai | | Authorization server metadata | circleback.ai | | Registration endpoint | https://circleback.ai/api/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://circleback.ai/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://circleback.ai/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://circleback.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Circleback. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: circleback.ai/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.circleback/circleback | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/circleback-ai/index.md) ## Sources - [Ora score page for circleback.ai](https://ora.ai/score/circleback.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Circleback was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=circleback), read 4 November 2026 - [Circleback website](https://circleback.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CircleCI MCP server | Agent MCP Directory" description: "CircleCI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/circleci-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CircleCI MCP server | Agent MCP Directory > CircleCI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/circleci-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CircleCI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for CircleCI at mcp.circleci.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | CircleCI | | --- | --- | | Domain | circleci.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 81, grade B; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for circleci.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.circleci.com/v1/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,217 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:53Z https://mcp.circleci.com/v1/mcp sent initialize result auth-required (HTTP 401) 1126 ms - 20:02:25Z https://mcp.circleci.com/v1/mcp sent initialize result auth-required (HTTP 401) 1217 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.circleci.com/.well-known/oauth-protected-resource/v1/mcp" | | Protected resource metadata | mcp.circleci.com | | Authorization server metadata | app.circleci.com | | Registration endpoint | https://app.circleci.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.circleci.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.circleci.com/.well-known/oauth-protected-resource/v1/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.circleci.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CircleCI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: circleci.com (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.circleci/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/circleci-com/index.md) ## Sources - [Ora score page for circleci.com](https://ora.ai/score/circleci.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 October 2026, read from GET /api/leaderboard) - [Where CircleCI was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.circleci%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=circleci), read 4 November 2026 - [CircleCI website](https://circleci.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cisco MCP server | Agent MCP Directory" description: "Does Cisco have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cisco-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cisco MCP server | Agent MCP Directory > Does Cisco have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cisco-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cisco: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cisco (cisco.com), so the connector had nothing to connect to. Ora's cached score for cisco.com is 33, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cisco | | --- | --- | | Domain | cisco.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 248 on the list of 4 November 2026 | | Ora score | 33, grade D; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cisco.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cisco. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cisco.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cisco. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cisco-com/index.md) ## Sources - [Ora score page for cisco.com](https://ora.ai/score/cisco.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Where Cisco was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cisco website](https://cisco.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clarm MCP server | Agent MCP Directory" description: "Does Clarm have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/clarm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clarm MCP server | Agent MCP Directory > Does Clarm have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/clarm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clarm: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Clarm (clarm.com), so the connector had nothing to connect to. Ora's cached score for clarm.com is 69, grade C, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Clarm (registry title: clarm.com) | | --- | --- | | Domain | clarm.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for clarm.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Clarm. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for clarm.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Clarm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: clarm.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clarm-com/index.md) ## Sources - [Ora score page for clarm.com](https://ora.ai/score/clarm.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/leaderboard) - [Where Clarm was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Clarm website](https://clarm.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Claude MCP server | Agent MCP Directory" description: "Claude has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/claude-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Claude MCP server | Agent MCP Directory > Claude has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/claude-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Claude: MCP server, CLI and agent surfaces Yes: Claude runs a public MCP server at platform.claude.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: search\_docs, get\_navigation, get\_doc. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for claude.com is 62, grade C, read on 5 November 2026. ## Fact sheet | Company | Claude (registry title: Claude Platform Docs) | | --- | --- | | Domain | claude.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 2,189 on the list of 4 November 2026 | | Ora score | 62, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for claude.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://platform.claude.com/docs/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | claude-platform-docs 1.0.1 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 641 ms over 1 attempt | ### Tools listed 4 tools - search\_docs - get\_navigation - get\_doc - get\_api\_endpoint ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:58Z https://platform.claude.com/docs/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 658 ms - 20:01:34Z https://platform.claude.com/docs/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 641 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://platform.claude.com/docs/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Claude. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.claude.platform/docs | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/claude-com/index.md) ## Sources - [Ora score page for claude.com](https://ora.ai/score/claude.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Where Claude was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.claude.platform%2Fdocs), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=claude), read 4 November 2026 - [Claude website](https://claude.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cleanlab MCP server | Agent MCP Directory" description: "Does Cleanlab have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cleanlab-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cleanlab MCP server | Agent MCP Directory > Does Cleanlab have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cleanlab-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cleanlab: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cleanlab (cleanlab.ai), so the connector had nothing to connect to. Ora's cached score for cleanlab.ai is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cleanlab (registry title: cleanlab.ai) | | --- | --- | | Domain | cleanlab.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cleanlab.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cleanlab. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cleanlab.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cleanlab. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cleanlab-ai/index.md) ## Sources - [Ora score page for cleanlab.ai](https://ora.ai/score/cleanlab.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Cleanlab was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cleanlab website](https://cleanlab.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clean Notes MCP server | Agent MCP Directory" description: "Clean Notes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/cleannotes-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clean Notes MCP server | Agent MCP Directory > Clean Notes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/cleannotes-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clean Notes: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Clean Notes at cleannotes.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Clean Notes | | --- | --- | | Domain | cleannotes.app | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for cleannotes.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://cleannotes.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,685 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:54Z https://cleannotes.app/mcp sent initialize result auth-required (HTTP 401) 1821 ms - 20:02:26Z https://cleannotes.app/mcp sent initialize result auth-required (HTTP 401) 1685 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://cleannotes.app/.well-known/oauth-protected-resource/mcp", scope="openid email" | | Protected resource metadata | cleannotes.app | | Authorization server metadata | nptfmuykgcmqqerpjlwe.supabase.co | | Registration endpoint | https://nptfmuykgcmqqerpjlwe.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://cleannotes.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://cleannotes.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://nptfmuykgcmqqerpjlwe.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Clean Notes. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.cleannotes/clean-notes | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cleannotes-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cleannotes), read 4 November 2026 - [Clean Notes website](https://cleannotes.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ClickUp MCP server | Agent MCP Directory" description: "ClickUp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/clickup-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ClickUp MCP server | Agent MCP Directory > ClickUp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/clickup-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ClickUp: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ClickUp at mcp.clickup.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ClickUp | | --- | --- | | Domain | clickup.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,948 on the list of 4 November 2026 | | Ora score | 64, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for clickup.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.clickup.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,826 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:01Z https://mcp.clickup.com/mcp sent initialize result auth-required (HTTP 401) 1599 ms - 20:01:37Z https://mcp.clickup.com/mcp sent initialize result auth-required (HTTP 401) 1826 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="MCP Server", error="invalid_token", error_description="Bearer token required", resource_metadata="https://mcp.clickup.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.clickup.com | | Authorization server metadata | mcp.clickup.com | | Registration endpoint | https://mcp.clickup.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.clickup.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.clickup.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.clickup.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ClickUp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clickup-com/index.md) ## Sources - [Ora score page for clickup.com](https://ora.ai/score/clickup.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Where ClickUp was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [ClickUp website](https://clickup.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clicon MCP server | Agent MCP Directory" description: "Clicon has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/clicon-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clicon MCP server | Agent MCP Directory > Clicon has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/clicon-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clicon: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Clicon (lotus.clicon.app), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). ## Fact sheet | Company | Clicon (registry title: Lotus: AI Citation Intelligence) | | --- | --- | | Domain | clicon.app | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for clicon.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://lotus.clicon.app/mcp/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | HTTP status | 404 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 707 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:54Z https://lotus.clicon.app/mcp/ sent initialize result no-answer (HTTP 404) 769 ms - 20:02:25Z https://lotus.clicon.app/mcp/ sent initialize result no-answer (HTTP 404) 707 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://lotus.clicon.app/mcp/`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Clicon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.clicon/lotus | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clicon-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=clicon), read 4 November 2026 - [Clicon website](https://clicon.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clidey MCP server | Agent MCP Directory" description: "Does Clidey have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/clidey-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clidey MCP server | Agent MCP Directory > Does Clidey have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/clidey-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clidey: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Clidey (clidey.com), so the connector had nothing to connect to. Ora's cached score for clidey.com is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Clidey (registry title: clidey.com) | | --- | --- | | Domain | clidey.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for clidey.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Clidey. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for clidey.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Clidey. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clidey-com/index.md) ## Sources - [Ora score page for clidey.com](https://ora.ai/score/clidey.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Clidey was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Clidey website](https://clidey.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cline MCP server | Agent MCP Directory" description: "Does Cline have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cline-bot site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cline MCP server | Agent MCP Directory > Does Cline have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cline-bot Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cline: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cline (cline.bot), so the connector had nothing to connect to. Ora's cached score for cline.bot is 77, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cline | | --- | --- | | Domain | cline.bot | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cline.bot, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cline. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cline.bot, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cline. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cline-bot/index.md) ## Sources - [Ora score page for cline.bot](https://ora.ai/score/cline.bot?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Cline was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cline website](https://cline.bot), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clino MCP server | Agent MCP Directory" description: "Clino has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/clino-ch site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clino MCP server | Agent MCP Directory > Clino has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/clino-ch Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clino: MCP server, CLI and agent surfaces Yes: Clino runs a public MCP server at clino.ch that listed 11 tools to a client with no credentials on 4 November 2026. Examples: estimate\_employer\_cost, compare\_cantons, get\_minimum\_wage. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Clino (registry title: Clino: Swiss household employment) | | --- | --- | | Domain | clino.ch | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for clino.ch when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://clino.ch/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | clino 1.5.0 | | Capabilities | tools, prompts | | Tools | 11 | | Resources | 0 | | Prompts | 2 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,073 ms over 1 attempt | ### Tools listed 11 tools - estimate\_employer\_cost - compare\_cantons - get\_minimum\_wage - get\_canton\_rules - get\_employer\_guide - get\_official\_sources - get\_hiring\_checklist - get\_contract\_terms - get\_employment\_package - search - fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:54Z https://clino.ch/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1094 ms - 20:02:26Z https://clino.ch/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1073 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://clino.ch/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Clino. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ch.clino/household-employment | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clino-ch/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=clino), read 4 November 2026 - [Clino website](https://clino.ch), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clockify™ MCP server | Agent MCP Directory" description: "Does Clockify™ have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/clockify-me site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clockify™ MCP server | Agent MCP Directory > Does Clockify™ have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/clockify-me Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clockify™: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Clockify™ (clockify.me), so the connector had nothing to connect to. Ora's cached score for clockify.me is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Clockify™ (registry title: clockify.me) | | --- | --- | | Domain | clockify.me | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for clockify.me, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Clockify™. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for clockify.me, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Clockify™. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clockify-me/index.md) ## Sources - [Ora score page for clockify.me](https://ora.ai/score/clockify.me?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Clockify™ was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Clockify™ website](https://clockify.me), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Close MCP server | Agent MCP Directory" description: "Close: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/close-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Close MCP server | Agent MCP Directory > Close: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/close-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Close: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Close at mcp.close.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Close | | --- | --- | | Domain | close.com | | Category | CRM (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 79, grade B; Ora scanned the domain on 14 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for close.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.close.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,733 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:55Z https://mcp.close.com/mcp sent initialize result auth-required (HTTP 401) 1689 ms - 20:02:27Z https://mcp.close.com/mcp sent initialize result auth-required (HTTP 401) 1733 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.close.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.close.com | | Authorization server metadata | api.close.com | | Registration endpoint | https://api.close.com/oauth2/register/ | | Auth as listed by a registry | OAuth2.1 API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.close.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.close.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.close.com/oauth2/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Close. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: close.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.close/close-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/close-com/index.md) ## Sources - [Ora score page for close.com](https://ora.ai/score/close.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 October 2026, read from GET /api/leaderboard) - [Where Close was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=close), read 4 November 2026 - [Close website](https://close.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Google Cloud (cloud.google.com) MCP server | Agent MCP Directory" description: "Does Google Cloud (cloud.google.com) have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cloud-google-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Google Cloud (cloud.google.com) MCP server | Agent MCP Directory > Does Google Cloud (cloud.google.com) have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cloud-google-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Google Cloud: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Google Cloud (cloud.google.com), so the connector had nothing to connect to. Ora's cached score for cloud.google.com is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Google Cloud | | --- | --- | | Domain | cloud.google.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cloud.google.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Google Cloud. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cloud.google.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Google Cloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloud-google-com/index.md) ## Sources - [Ora score page for cloud.google.com](https://ora.ai/score/cloud.google.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Google Cloud was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Google Cloud website](https://cloud.google.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Microsoft 365 MCP server | Agent MCP Directory" description: "Microsoft 365: sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/cloud-microsoft site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Microsoft 365 MCP server | Agent MCP Directory > Microsoft 365: sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/cloud-microsoft Site: Agent MCP Directory Last reviewed: 2026-11-05 # Microsoft 365: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Microsoft 365 at mcp.svc.cloud.microsoft answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Microsoft 365 (registry title: Microsoft 365 (Enterprise MCP)) | | --- | --- | | Domain | cloud.microsoft | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth without client registration) | | Tranco rank | 42 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for cloud.microsoft when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.svc.cloud.microsoft/enterprise | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,390 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:52Z https://mcp.svc.cloud.microsoft/enterprise sent initialize result auth-required (HTTP 401) 1180 ms - 20:01:27Z https://mcp.svc.cloud.microsoft/enterprise sent initialize result auth-required (HTTP 401) 1390 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer realm="", authorization_uri="https://login.microsoftonline.com/common/oauth2/authorize", client_id="e8c77dc2-69b3-43f4-bc51-3213c9d915b4", resource_metadata="https://mcp.svc.cloud.microsoft/.well-known/oauth-protected-resource/enterprise" | | Protected resource metadata | mcp.svc.cloud.microsoft | | Authorization server metadata | login.microsoftonline.com | ### The sign-in route, step by step 1. Request `https://mcp.svc.cloud.microsoft/enterprise` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://login.microsoftonline.com/organizations/v2.0/.well-known/openid-configuration`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Microsoft 365. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloud-microsoft/index.md) ## Sources - [Where Microsoft 365 was found](https://github.com/mcp/microsoft/EnterpriseMCP), read 4 November 2026 - [Microsoft 365 website](https://cloud.microsoft), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CloudBees MCP server | Agent MCP Directory" description: "Does CloudBees have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cloudbees-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CloudBees MCP server | Agent MCP Directory > Does CloudBees have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cloudbees-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CloudBees: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for CloudBees (cloudbees.com), so the connector had nothing to connect to. Ora's cached score for cloudbees.com is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | CloudBees (registry title: cloudbees.com) | | --- | --- | | Domain | cloudbees.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cloudbees.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for CloudBees. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cloudbees.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for CloudBees. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloudbees-com/index.md) ## Sources - [Ora score page for cloudbees.com](https://ora.ai/score/cloudbees.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where CloudBees was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [CloudBees website](https://cloudbees.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudchipr MCP server | Agent MCP Directory" description: "Cloudchipr: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/cloudchipr-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cloudchipr MCP server | Agent MCP Directory > Cloudchipr: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/cloudchipr-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudchipr: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Cloudchipr; the connector's guess at mcp.cloudchipr.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cloudchipr (registry title: cloudchipr.com) | | --- | --- | | Domain | cloudchipr.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 55, grade C; Ora scanned the domain on 19 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cloudchipr.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cloudchipr.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,737 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:55Z https://mcp.cloudchipr.com/mcp sent initialize result auth-required (HTTP 401) 1699 ms - 20:02:27Z https://mcp.cloudchipr.com/mcp sent initialize result auth-required (HTTP 401) 1737 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="cloudchipr", error="invalid_token", error_description="No bearer token provided" | | Protected resource metadata | mcp.cloudchipr.com | | Authorization server metadata | auth0.cloudchipr.com | | Registration endpoint | https://auth0.cloudchipr.com/oidc/register | ### The sign-in route, step by step 1. Request `https://mcp.cloudchipr.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.cloudchipr.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth0.cloudchipr.com/oidc/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cloudchipr. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloudchipr-com/index.md) ## Sources - [Ora score page for cloudchipr.com](https://ora.ai/score/cloudchipr.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 August 2026, read from GET /api/leaderboard) - [Where Cloudchipr was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cloudchipr website](https://cloudchipr.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudflare MCP server | Agent MCP Directory" description: "Cloudflare has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cloudflare-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cloudflare MCP server | Agent MCP Directory > Cloudflare has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cloudflare-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudflare: MCP server, CLI and agent surfaces Yes: Cloudflare runs a public MCP server at docs.mcp.cloudflare.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: search\_cloudflare\_documentation, migrate\_pages\_to\_workers\_guide. It speaks streamable-http, protocol 2025-11-25. A CLI is on record: wrangler on npm. Ora's cached score for cloudflare.com is 82, grade B, read on 5 November 2026. ## Fact sheet | Company | Cloudflare | | --- | --- | | Domain | cloudflare.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 2 on the list of 4 November 2026 | | Ora score | 82, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cloudflare.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://docs.mcp.cloudflare.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | docs-ai-search 0.5.0 | | Capabilities | tools, prompts | | Tools | 2 | | Resources | 0 | | Prompts | 1 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 238 ms over 1 attempt | | Documentation | developers.cloudflare.com | ### Tools listed 2 tools - search\_cloudflare\_documentation - migrate\_pages\_to\_workers\_guide ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:51Z https://docs.mcp.cloudflare.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 138 ms - 20:01:26Z https://docs.mcp.cloudflare.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 238 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://docs.mcp.cloudflare.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | wrangler on npm (page) | | --- | --- | | Exists | yes | | Latest version | 4.157.0 | | Last publish | 3 November 2026 | | Command names | wrangler, wrangler2, cf-wrangler | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.cloudflare.com (JSON, via the shared crawl). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: cloudflare.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Found: cloudflare.com/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.cloudflare.mcp/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloudflare-com/index.md) ## Sources - [Cloudflare MCP documentation](https://developers.cloudflare.com/agents/model-context-protocol/mcp-servers-for-cloudflare/), read 4 November 2026 - [Ora score page for cloudflare.com](https://ora.ai/score/cloudflare.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cloudflare), read 4 November 2026 - [Cloudflare website](https://cloudflare.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudglue MCP server | Agent MCP Directory" description: "Cloudglue: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cloudglue-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cloudglue MCP server | Agent MCP Directory > Cloudglue: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cloudglue-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudglue: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Cloudglue; the connector's guess at mcp.cloudglue.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cloudglue (registry title: cloudglue.dev) | | --- | --- | | Domain | cloudglue.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cloudglue.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cloudglue.dev/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,242 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:57Z https://mcp.cloudglue.dev/mcp sent initialize result auth-required (HTTP 401) 2603 ms - 20:02:27Z https://mcp.cloudglue.dev/mcp sent initialize result auth-required (HTTP 401) 1242 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Invalid token", resource_metadata="https://mcp.cloudglue.dev/.well-known/oauth-protected-resource" | ### The sign-in route, step by step 1. Request `https://mcp.cloudglue.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cloudglue. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloudglue-dev/index.md) ## Sources - [Ora score page for cloudglue.dev](https://ora.ai/score/cloudglue.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Cloudglue was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cloudglue website](https://cloudglue.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudinary MCP server | Agent MCP Directory" description: "Cloudinary: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/cloudinary-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cloudinary MCP server | Agent MCP Directory > Cloudinary: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/cloudinary-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudinary: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Cloudinary at asset-management.mcp.cloudinary.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cloudinary | | --- | --- | | Domain | cloudinary.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 882 on the list of 4 November 2026 | | Ora score | 83, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cloudinary.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://asset-management.mcp.cloudinary.com/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 605 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://asset-management.mcp.cloudinary.com/sse sent initialize result auth-required (HTTP 401) 516 ms - 20:01:31Z https://asset-management.mcp.cloudinary.com/sse sent initialize result auth-required (HTTP 401) 605 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://asset-management.mcp.cloudinary.com/.well-known/oauth-protected-resource", scope="openid profile email offline_access asset_management upload media_generation" | | Protected resource metadata | asset-management.mcp.cloudinary.com | | Authorization server metadata | asset-management.mcp.cloudinary.com | | Registration endpoint | https://asset-management.mcp.cloudinary.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://asset-management.mcp.cloudinary.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://asset-management.mcp.cloudinary.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://asset-management.mcp.cloudinary.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cloudinary. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloudinary-com/index.md) ## Sources - [Ora score page for cloudinary.com](https://ora.ai/score/cloudinary.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Cloudinary was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Cloudinary website](https://cloudinary.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudthread MCP server | Agent MCP Directory" description: "Does Cloudthread have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cloudthread-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cloudthread MCP server | Agent MCP Directory > Does Cloudthread have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cloudthread-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudthread: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cloudthread (cloudthread.io), so the connector had nothing to connect to. Ora's cached score for cloudthread.io is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cloudthread (registry title: cloudthread.io) | | --- | --- | | Domain | cloudthread.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cloudthread.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cloudthread. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cloudthread.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cloudthread. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cloudthread-io/index.md) ## Sources - [Ora score page for cloudthread.io](https://ora.ai/score/cloudthread.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Cloudthread was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clubhouse MCP server | Agent MCP Directory" description: "Does Clubhouse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/clubhouse-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clubhouse MCP server | Agent MCP Directory > Does Clubhouse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/clubhouse-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clubhouse: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Clubhouse (clubhouse.io), so the connector had nothing to connect to. Ora's cached score for clubhouse.io is 62, grade C, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Clubhouse (registry title: clubhouse.io) | | --- | --- | | Domain | clubhouse.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for clubhouse.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Clubhouse. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for clubhouse.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Clubhouse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.shortcut.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clubhouse-io/index.md) ## Sources - [Ora score page for clubhouse.io](https://ora.ai/score/clubhouse.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where Clubhouse was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Clubhouse website](https://clubhouse.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clueso MCP server | Agent MCP Directory" description: "Clueso has an open MCP server with 54 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/clueso-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clueso MCP server | Agent MCP Directory > Clueso has an open MCP server with 54 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/clueso-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clueso: MCP server, CLI and agent surfaces Yes: Clueso runs a public MCP server at connect.clueso.io that listed 54 tools to a client with no credentials on 4 November 2026. Examples: get\_design\_guide, read\_animation, edit\_animation. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for clueso.io is 78, grade B, read on 5 November 2026. ## Fact sheet | Company | Clueso | | --- | --- | | Domain | clueso.io | | Category | AI & ML (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 78, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for clueso.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://connect.clueso.io/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | clueso-connect 1.0.0 | | Capabilities | experimental, resources, tools | | Tools | 54 | | Resources | 19 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 901 ms over 1 attempt | ### Tools listed 54 tools; the first 40 names are recorded - get\_design\_guide - read\_animation - edit\_animation - create\_project - update\_project - duplicate\_project - export\_project - get\_export - get\_media\_job - get\_recording\_activity - get\_embed - create\_folder - find - switch\_workspace - get\_project - get\_clip - update\_clips - remove\_clip - split\_clip - captions - duplicate\_clip - add\_clips - get\_element\_schema - add\_elements - update\_elements - remove\_elements - reorder\_elements - update\_groups - remove\_from\_project - add\_audio - update\_audio - extract\_audio - voiceover\_batch - auto\_sync - add\_sync\_point - upload\_file - check\_uploads - generate\_media - analyze\_audio - get\_article ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:55Z https://connect.clueso.io/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 914 ms - 20:02:27Z https://connect.clueso.io/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 901 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://connect.clueso.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Clueso. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | Found: clueso.io/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.clueso/video | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clueso-io/index.md) ## Sources - [Ora score page for clueso.io](https://ora.ai/score/clueso.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Where Clueso was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.clueso%2Fvideo), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=clueso), read 4 November 2026 - [Clueso website](https://clueso.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clutch.co MCP server | Agent MCP Directory" description: "Clutch.co has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/clutch-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clutch.co MCP server | Agent MCP Directory > Clutch.co has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/clutch-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clutch.co: MCP server, CLI and agent surfaces Yes: Clutch.co runs a public MCP server at bot.clutch.co that listed 5 tools to a client with no credentials on 4 November 2026. Examples: get\_provider\_info, get\_service\_provider\_reviews, recommend\_service\_providers. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for clutch.co is 21, grade F, read on 5 November 2026. ## Fact sheet | Company | Clutch.co | | --- | --- | | Domain | clutch.co | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 7,300 on the list of 4 November 2026 | | Ora score | 21, grade F; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for clutch.co, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://bot.clutch.co/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Clutch 3.4.2 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 5 | | Resources | 4 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,281 ms over 1 attempt | ### Tools listed 5 tools - get\_provider\_info - get\_service\_provider\_reviews - recommend\_service\_providers - send\_message\_to\_provider - get\_service\_packages ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:13Z https://bot.clutch.co/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 908 ms - 20:01:51Z https://bot.clutch.co/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1281 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://bot.clutch.co/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Clutch.co. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.clutch/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/clutch-co/index.md) ## Sources - [Ora score page for clutch.co](https://ora.ai/score/clutch.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/score) - [Where Clutch.co was found](https://registry.modelcontextprotocol.io/v0/servers?search=co.clutch%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=clutch), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "cmux MCP server | Agent MCP Directory" description: "Does cmux have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/cmux-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # cmux MCP server | Agent MCP Directory > Does cmux have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/cmux-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # cmux: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for cmux (cmux.com), so the connector had nothing to connect to. Ora's cached score for cmux.com is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | cmux (registry title: cmux.com) | | --- | --- | | Domain | cmux.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cmux.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for cmux. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cmux.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for cmux. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cmux-com/index.md) ## Sources - [Ora score page for cmux.com](https://ora.ai/score/cmux.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where cmux was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [cmux website](https://cmux.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codev MCP server | Agent MCP Directory" description: "Does Codev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/co-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codev MCP server | Agent MCP Directory > Does Codev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/co-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codev: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Codev (co.dev), so the connector had nothing to connect to. Ora's cached score for co.dev is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Codev | | --- | --- | | Domain | co.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 16 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for co.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Codev. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for co.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Codev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/co-dev/index.md) ## Sources - [Ora score page for co.dev](https://ora.ai/score/co.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 September 2026, read from GET /api/leaderboard) - [Where Codev was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Codev website](https://co.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Coasts MCP server | Agent MCP Directory" description: "Does Coasts have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/coasts-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Coasts MCP server | Agent MCP Directory > Does Coasts have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/coasts-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Coasts: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Coasts (coasts.dev), so the connector had nothing to connect to. Ora's cached score for coasts.dev is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Coasts (registry title: coasts.dev) | | --- | --- | | Domain | coasts.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for coasts.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Coasts. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for coasts.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Coasts. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coasts-dev/index.md) ## Sources - [Ora score page for coasts.dev](https://ora.ai/score/coasts.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Coasts was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Coasts website](https://coasts.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CockroachDB MCP server | Agent MCP Directory" description: "Does CockroachDB have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cockroachlabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CockroachDB MCP server | Agent MCP Directory > Does CockroachDB have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cockroachlabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CockroachDB: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for CockroachDB (cockroachlabs.com), so the connector had nothing to connect to. Ora's cached score for cockroachlabs.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | CockroachDB | | --- | --- | | Domain | cockroachlabs.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cockroachlabs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for CockroachDB. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cockroachlabs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for CockroachDB. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cockroachlabs-com/index.md) ## Sources - [Ora score page for cockroachlabs.com](https://ora.ai/score/cockroachlabs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where CockroachDB was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [CockroachDB website](https://cockroachlabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codeanywhere MCP server | Agent MCP Directory" description: "Does Codeanywhere have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codeanywhere-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codeanywhere MCP server | Agent MCP Directory > Does Codeanywhere have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codeanywhere-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codeanywhere: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Codeanywhere (codeanywhere.com), so the connector had nothing to connect to. Ora's cached score for codeanywhere.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Codeanywhere (registry title: codeanywhere.com) | | --- | --- | | Domain | codeanywhere.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for codeanywhere.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Codeanywhere. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codeanywhere.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Codeanywhere. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codeanywhere-com/index.md) ## Sources - [Ora score page for codeanywhere.com](https://ora.ai/score/codeanywhere.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/leaderboard) - [Where Codeanywhere was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Codeanywhere website](https://codeanywhere.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codeberg.org MCP server | Agent MCP Directory" description: "Does Codeberg.org have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codeberg-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codeberg.org MCP server | Agent MCP Directory > Does Codeberg.org have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codeberg-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codeberg.org: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Codeberg.org (codeberg.org), so the connector had nothing to connect to. Ora's cached score for codeberg.org is 54, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Codeberg.org | | --- | --- | | Domain | codeberg.org | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 3,498 on the list of 4 November 2026 | | Ora score | 54, grade C; Ora scanned the domain on 4 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for codeberg.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Codeberg.org. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codeberg.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Codeberg.org. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codeberg-org/index.md) ## Sources - [Ora score page for codeberg.org](https://ora.ai/score/codeberg.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 October 2026, read from GET /api/score) - [Where Codeberg.org was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Codeberg.org website](https://codeberg.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Code Climate MCP server | Agent MCP Directory" description: "Does Code Climate have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codeclimate-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Code Climate MCP server | Agent MCP Directory > Does Code Climate have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codeclimate-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Code Climate: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Code Climate (codeclimate.com), so the connector had nothing to connect to. Ora's cached score for codeclimate.com is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Code Climate | | --- | --- | | Domain | codeclimate.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for codeclimate.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Code Climate. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codeclimate.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Code Climate. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codeclimate-com/index.md) ## Sources - [Ora score page for codeclimate.com](https://ora.ai/score/codeclimate.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Code Climate was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Code Climate website](https://codeclimate.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codecov MCP server | Agent MCP Directory" description: "Does Codecov have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codecov-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codecov MCP server | Agent MCP Directory > Does Codecov have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codecov-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codecov: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Codecov (codecov.io), so the connector had nothing to connect to. Ora's cached score for codecov.io is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Codecov | | --- | --- | | Domain | codecov.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 18 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for codecov.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Codecov. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codecov.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Codecov. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codecov-io/index.md) ## Sources - [Ora score page for codecov.io](https://ora.ai/score/codecov.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 October 2026, read from GET /api/leaderboard) - [Where Codecov was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Codecov website](https://codecov.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codefresh MCP server | Agent MCP Directory" description: "Does Codefresh have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codefresh-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codefresh MCP server | Agent MCP Directory > Does Codefresh have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codefresh-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codefresh: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Codefresh (codefresh.io), so the connector had nothing to connect to. Ora's cached score for codefresh.io is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Codefresh (registry title: codefresh.io) | | --- | --- | | Domain | codefresh.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for codefresh.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Codefresh. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codefresh.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Codefresh. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codefresh-io/index.md) ## Sources - [Ora score page for codefresh.io](https://ora.ai/score/codefresh.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Codefresh was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Codefresh website](https://codefresh.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codeium MCP server | Agent MCP Directory" description: "Does Codeium have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codeium-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codeium MCP server | Agent MCP Directory > Does Codeium have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codeium-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codeium: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Codeium (codeium.com), so the connector had nothing to connect to. Ora's cached score for codeium.com is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Codeium | | --- | --- | | Domain | codeium.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 18 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for codeium.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Codeium. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codeium.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Codeium. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codeium-com/index.md) ## Sources - [Ora score page for codeium.com](https://ora.ai/score/codeium.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 September 2026, read from GET /api/leaderboard) - [Where Codeium was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Codeium website](https://codeium.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codemagic MCP server | Agent MCP Directory" description: "Does Codemagic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codemagic-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codemagic MCP server | Agent MCP Directory > Does Codemagic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codemagic-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codemagic: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Codemagic (codemagic.io), so the connector had nothing to connect to. Ora's cached score for codemagic.io is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Codemagic | | --- | --- | | Domain | codemagic.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for codemagic.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Codemagic. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codemagic.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Codemagic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codemagic-io/index.md) ## Sources - [Ora score page for codemagic.io](https://ora.ai/score/codemagic.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Codemagic was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Codemagic website](https://codemagic.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Coder MCP server | Agent MCP Directory" description: "Does Coder have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/coder-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Coder MCP server | Agent MCP Directory > Does Coder have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/coder-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Coder: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Coder (coder.com), so the connector had nothing to connect to. Ora's cached score for coder.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Coder (registry title: coder.com) | | --- | --- | | Domain | coder.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for coder.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Coder. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for coder.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Coder. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coder-com/index.md) ## Sources - [Ora score page for coder.com](https://ora.ai/score/coder.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Coder was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Coder website](https://coder.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CodeSandbox MCP server | Agent MCP Directory" description: "Does CodeSandbox have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codesandbox-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CodeSandbox MCP server | Agent MCP Directory > Does CodeSandbox have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/codesandbox-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # CodeSandbox: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for CodeSandbox (codesandbox.io), so the connector had nothing to connect to. Ora's cached score for codesandbox.io is 44, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | CodeSandbox | | --- | --- | | Domain | codesandbox.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 44, grade D; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for codesandbox.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for CodeSandbox. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for codesandbox.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for CodeSandbox. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codesandbox-io/index.md) ## Sources - [Ora score page for codesandbox.io](https://ora.ai/score/codesandbox.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where CodeSandbox was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [CodeSandbox website](https://codesandbox.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Codex Reset MCP server | Agent MCP Directory" description: "Codex Reset has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/codex-reset-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Codex Reset MCP server | Agent MCP Directory > Codex Reset has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/codex-reset-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Codex Reset: MCP server, CLI and agent surfaces Yes: Codex Reset runs a public MCP server at codex-reset.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: get\_reset\_forecast, get\_reset\_timeline, get\_codex\_status. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Codex Reset | | --- | --- | | Domain | codex-reset.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for codex-reset.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://codex-reset.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | codex-reset 1.0.0 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 188 ms over 1 attempt | ### Tools listed 3 tools - get\_reset\_forecast - get\_reset\_timeline - get\_codex\_status ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:57Z https://codex-reset.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 268 ms - 20:02:28Z https://codex-reset.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 188 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://codex-reset.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Codex Reset. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: codex-reset.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/codex-reset-com/index.md) ## Sources - [Codex Reset website](https://codex-reset.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cogram MCP server | Agent MCP Directory" description: "Cogram: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cogram-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cogram MCP server | Agent MCP Directory > Cogram: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cogram-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cogram: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Cogram at mcp.cogram.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cogram (registry title: Cogram Project) | | --- | --- | | Domain | cogram.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 71, grade B; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cogram.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cogram.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,370 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:58Z https://mcp.cogram.com/mcp sent initialize result auth-required (HTTP 401) 1585 ms - 20:02:29Z https://mcp.cogram.com/mcp sent initialize result auth-required (HTTP 401) 1370 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.cogram.com/.well-known/oauth-protected-resource/mcp", scope="email offline_access" | | Protected resource metadata | mcp.cogram.com | | Authorization server metadata | mcp.cogram.com | | Registration endpoint | https://oudzkevdvvkndzkgndiw.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://mcp.cogram.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.cogram.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://oudzkevdvvkndzkgndiw.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cogram. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.cogram/project | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cogram-com/index.md) ## Sources - [Ora score page for cogram.com](https://ora.ai/score/cogram.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Cogram was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.cogram%2Fproject), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cogram), read 4 November 2026 - [Cogram website](https://cogram.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CoinMarketCap MCP server | Agent MCP Directory" description: "CoinMarketCap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/coinmarketcap-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CoinMarketCap MCP server | Agent MCP Directory > CoinMarketCap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/coinmarketcap-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CoinMarketCap: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for CoinMarketCap at mcp.coinmarketcap.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | CoinMarketCap | | --- | --- | | Domain | coinmarketcap.com | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,179 on the list of 4 November 2026 | | Ora score | 60, grade C; Ora scanned the domain on 7 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for coinmarketcap.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.coinmarketcap.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,720 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:58Z https://mcp.coinmarketcap.com/mcp sent initialize result auth-required (HTTP 401) 1157 ms - 20:01:35Z https://mcp.coinmarketcap.com/mcp sent initialize result auth-required (HTTP 401) 1720 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Token not found" | | Protected resource metadata | mcp.coinmarketcap.com | | Authorization server metadata | mcp.coinmarketcap.com | | Registration endpoint | https://mcp.coinmarketcap.com/register | ### The sign-in route, step by step 1. Request `https://mcp.coinmarketcap.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.coinmarketcap.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.coinmarketcap.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CoinMarketCap. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.coinmarketcap/coinmarketcap | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coinmarketcap-com/index.md) ## Sources - [Ora score page for coinmarketcap.com](https://ora.ai/score/coinmarketcap.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 September 2026, read from GET /api/score) - [Where CoinMarketCap was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.coinmarketcap%2Fcoinmarketcap), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=coinmarketcap), read 4 November 2026 - [CoinMarketCap website](https://coinmarketcap.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "COLA Cloud MCP server | Agent MCP Directory" description: "COLA Cloud: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/colacloud-us site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # COLA Cloud MCP server | Agent MCP Directory > COLA Cloud: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/colacloud-us Site: Agent MCP Directory Last reviewed: 2026-11-05 # COLA Cloud: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for COLA Cloud at mcp.colacloud.us answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | COLA Cloud | | --- | --- | | Domain | colacloud.us | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for colacloud.us when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.colacloud.us/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 720 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:57Z https://mcp.colacloud.us/mcp sent initialize result auth-required (HTTP 401) 948 ms - 20:02:29Z https://mcp.colacloud.us/mcp sent initialize result auth-required (HTTP 401) 720 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="colacloud", resource_metadata="https://mcp.colacloud.us/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.colacloud.us | | Authorization server metadata | nimble-star-17.authkit.app | | Registration endpoint | https://nimble-star-17.authkit.app/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.colacloud.us/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.colacloud.us/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://nimble-star-17.authkit.app/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for COLA Cloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/colacloud-us/index.md) ## Sources - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CometChat MCP server | Agent MCP Directory" description: "CometChat has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cometchat-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CometChat MCP server | Agent MCP Directory > CometChat has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cometchat-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CometChat: MCP server, CLI and agent surfaces Yes: CometChat runs a public MCP server at mcp.cometchat.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: search\_cometchat\_docs, fetch\_cometchat\_doc\_page, get\_cometchat\_implementation\_bundle. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for cometchat.com is 56, grade C, read on 5 November 2026. ## Fact sheet | Company | CometChat (registry title: CometChat Docs) | | --- | --- | | Domain | cometchat.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 56, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cometchat.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cometchat.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | CometChat Docs 0.1.7 | | Capabilities | tools, resources | | Tools | 4 | | Resources | 12 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 683 ms over 1 attempt | ### Tools listed 4 tools - search\_cometchat\_docs - fetch\_cometchat\_doc\_page - get\_cometchat\_implementation\_bundle - list\_cometchat\_bundles ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:57Z https://mcp.cometchat.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 737 ms - 20:02:29Z https://mcp.cometchat.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 683 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.cometchat.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CometChat. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cometchat-com/index.md) ## Sources - [Ora score page for cometchat.com](https://ora.ai/score/cometchat.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Where CometChat was found](https://github.com/mcp/cometchat/docs-mcp), read 4 November 2026 - [CometChat website](https://cometchat.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Common Paper MCP server | Agent MCP Directory" description: "Common Paper: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Legal & Compliance." canonical: https://agentmcpdirectory.com/directory/commonpaper-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Common Paper MCP server | Agent MCP Directory > Common Paper: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Legal & Compliance. Source: https://agentmcpdirectory.com/directory/commonpaper-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Common Paper: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Common Paper at api.commonpaper.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Common Paper | | --- | --- | | Domain | commonpaper.com | | Category | Legal & Compliance (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 51, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for commonpaper.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.commonpaper.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 412 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:58Z https://api.commonpaper.com/mcp sent initialize result auth-required (HTTP 401) 966 ms - 20:02:29Z https://api.commonpaper.com/mcp sent initialize result auth-required (HTTP 401) 412 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.commonpaper.com/.well-known/oauth-protected-resource/mcp", scope="offline_access" | | Protected resource metadata | api.commonpaper.com | | Authorization server metadata | dev-5g9f1d1h.us.auth0.com | | Registration endpoint | https://dev-5g9f1d1h.us.auth0.com/oidc/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.commonpaper.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.commonpaper.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://dev-5g9f1d1h.us.auth0.com/oidc/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Common Paper. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.commonpaper/contracts | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/commonpaper-com/index.md) ## Sources - [Ora score page for commonpaper.com](https://ora.ai/score/commonpaper.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=commonpaper), read 4 November 2026 - [Common Paper website](https://commonpaper.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Commsharbor MCP server | Agent MCP Directory" description: "Commsharbor has an open MCP server with 38 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/commsharbor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Commsharbor MCP server | Agent MCP Directory > Commsharbor has an open MCP server with 38 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/commsharbor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Commsharbor: MCP server, CLI and agent surfaces Yes: Commsharbor runs a public MCP server at commsharbor.com that listed 38 tools to a client with no credentials on 4 November 2026. Examples: commsharbor\_health, commsharbor\_logout, commsharbor\_me. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Commsharbor | | --- | --- | | Domain | commsharbor.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for commsharbor.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://commsharbor.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | CommsHarbor fb0c5518 | | Capabilities | tools, prompts | | Tools | 38 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,088 ms over 1 attempt | ### Tools listed 38 tools - commsharbor\_health - commsharbor\_logout - commsharbor\_me - commsharbor\_context - commsharbor\_organization\_get - commsharbor\_audit - commsharbor\_platform\_context - commsharbor\_billing\_catalog - commsharbor\_email\_google\_catalog - commsharbor\_email\_google\_connect - commsharbor\_email\_google\_resolve - commsharbor\_email\_google\_disconnect - commsharbor\_email\_domain\_products\_list - commsharbor\_email\_domain\_products\_add - commsharbor\_email\_workspace\_snapshot - commsharbor\_email\_plans - commsharbor\_email\_workspace - commsharbor\_email\_trial\_activate - commsharbor\_email\_domain\_setup - commsharbor\_email\_domain\_create - commsharbor\_email\_domain\_get - commsharbor\_email\_domain\_verify - commsharbor\_email\_domain\_assistance - commsharbor\_email\_mailbox\_create - commsharbor\_email\_mailbox\_update - commsharbor\_email\_mailbox\_password - commsharbor\_email\_mailbox\_suspend - commsharbor\_email\_mailbox\_resume - commsharbor\_email\_alias\_create - commsharbor\_email\_alias\_update - commsharbor\_email\_alias\_suspend - commsharbor\_email\_alias\_resume - commsharbor\_email\_job\_get - commsharbor\_email\_service\_request - commsharbor\_email\_security\_check - commsharbor\_brazil\_email\_report - pricing - get\_api\_x402\_email\_check ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:59Z https://commsharbor.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2165 ms - 20:02:30Z https://commsharbor.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2088 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://commsharbor.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Commsharbor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: commsharbor.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.commsharbor/commsharbor | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/commsharbor-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=commsharbor), read 4 November 2026 - [Commsharbor website](https://commsharbor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Composio MCP server | Agent MCP Directory" description: "Does Composio have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/composio-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Composio MCP server | Agent MCP Directory > Does Composio have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/composio-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Composio: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Composio (composio.dev), so the connector had nothing to connect to. A CLI is on record: composio on pypi. Ora's cached score for composio.dev is 83, grade B, read on 5 November 2026. ## Fact sheet | Company | Composio | | --- | --- | | Domain | composio.dev | | Category | Agent Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 83, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for composio.dev, a vendor-published score) | | Company found through | the vendor's own documentation | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Composio. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for composio.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | composio on pypi (page) | | --- | --- | | Exists | yes | | Latest version | 0.31.0 | | Last publish | 3 November 2026 | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/composio-dev/index.md) ## Sources - [composio on pypi](https://pypi.org/project/composio/), read 4 November 2026 - [Ora score page for composio.dev](https://ora.ai/score/composio.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Composio was found](https://docs.composio.dev/docs/mcp-overview), read 4 November 2026 - [Composio website](https://composio.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Compresr MCP server | Agent MCP Directory" description: "Does Compresr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/compresr-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Compresr MCP server | Agent MCP Directory > Does Compresr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/compresr-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Compresr: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Compresr (compresr.ai), so the connector had nothing to connect to. Ora's cached score for compresr.ai is 49, grade C, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Compresr (registry title: compresr.ai) | | --- | --- | | Domain | compresr.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for compresr.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Compresr. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for compresr.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Compresr. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: compresr.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/compresr-ai/index.md) ## Sources - [Ora score page for compresr.ai](https://ora.ai/score/compresr.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Compresr was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Compresr website](https://compresr.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Compyle MCP server | Agent MCP Directory" description: "Does Compyle have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/compyle-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Compyle MCP server | Agent MCP Directory > Does Compyle have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/compyle-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Compyle: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Compyle (compyle.ai), so the connector had nothing to connect to. Ora's cached score for compyle.ai is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Compyle (registry title: compyle.ai) | | --- | --- | | Domain | compyle.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 19 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for compyle.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Compyle. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for compyle.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Compyle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/compyle-ai/index.md) ## Sources - [Ora score page for compyle.ai](https://ora.ai/score/compyle.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 August 2026, read from GET /api/leaderboard) - [Where Compyle was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Compyle website](https://compyle.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Concourse CI MCP server | Agent MCP Directory" description: "Does Concourse CI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/concourse-ci-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Concourse CI MCP server | Agent MCP Directory > Does Concourse CI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/concourse-ci-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Concourse CI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Concourse CI (concourse-ci.org), so the connector had nothing to connect to. Ora's cached score for concourse-ci.org is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Concourse CI (registry title: concourse-ci.org) | | --- | --- | | Domain | concourse-ci.org | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for concourse-ci.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Concourse CI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for concourse-ci.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Concourse CI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/concourse-ci-org/index.md) ## Sources - [Ora score page for concourse-ci.org](https://ora.ai/score/concourse-ci.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where Concourse CI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Concourse CI website](https://concourse-ci.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Conductor MCP server | Agent MCP Directory" description: "Does Conductor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/conductor-build site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Conductor MCP server | Agent MCP Directory > Does Conductor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/conductor-build Site: Agent MCP Directory Last reviewed: 2026-11-05 # Conductor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Conductor (conductor.build), so the connector had nothing to connect to. Ora's cached score for conductor.build is 72, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Conductor (registry title: conductor.build) | | --- | --- | | Domain | conductor.build | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for conductor.build, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Conductor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for conductor.build, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Conductor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/conductor-build/index.md) ## Sources - [Ora score page for conductor.build](https://ora.ai/score/conductor.build?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Conductor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Conductor website](https://conductor.build), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Confident AI MCP server | Agent MCP Directory" description: "Confident AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/confident-ai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Confident AI MCP server | Agent MCP Directory > Confident AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/confident-ai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Confident AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Confident AI; the connector's guess at mcp.confident-ai.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Confident AI (registry title: confident-ai.com) | | --- | --- | | Domain | confident-ai.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 90, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for confident-ai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.confident-ai.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,986 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://mcp.confident-ai.com/mcp sent initialize result auth-required (HTTP 401) 2050 ms - 20:02:32Z https://mcp.confident-ai.com/mcp sent initialize result auth-required (HTTP 401) 1986 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.confident-ai.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.confident-ai.com | | Authorization server metadata | api.confident-ai.com | | Registration endpoint | https://api.confident-ai.com/api/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.confident-ai.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.confident-ai.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.confident-ai.com/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Confident AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Found: confident-ai.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/confident-ai-com/index.md) ## Sources - [Ora score page for confident-ai.com](https://ora.ai/score/confident-ai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Confident AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Confident AI website](https://confident-ai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ConfigCat MCP server | Agent MCP Directory" description: "ConfigCat: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/configcat-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ConfigCat MCP server | Agent MCP Directory > ConfigCat: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/configcat-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ConfigCat: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for ConfigCat; the connector's guess at mcp.configcat.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ConfigCat (registry title: configcat.com) | | --- | --- | | Domain | configcat.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 51, grade C; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for configcat.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.configcat.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 622 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:59Z https://mcp.configcat.com/mcp sent initialize result auth-required (HTTP 401) 543 ms - 20:02:30Z https://mcp.configcat.com/mcp sent initialize result auth-required (HTTP 401) 622 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="public_api", resource_metadata="https://mcp.configcat.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.configcat.com | | Authorization server metadata | dashboard-api.configcat.com | ### The sign-in route, step by step 1. Request `https://mcp.configcat.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://dashboard-api.configcat.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ConfigCat. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/configcat-com/index.md) ## Sources - [Ora score page for configcat.com](https://ora.ai/score/configcat.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where ConfigCat was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ConfigCat website](https://configcat.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Confluent MCP server | Agent MCP Directory" description: "Does Confluent have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/confluent-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Confluent MCP server | Agent MCP Directory > Does Confluent have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/confluent-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Confluent: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Confluent (confluent.io), so the connector had nothing to connect to. Ora's cached score for confluent.io is 78, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Confluent | | --- | --- | | Domain | confluent.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 78, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for confluent.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Confluent. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for confluent.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Confluent. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/confluent-io/index.md) ## Sources - [Ora score page for confluent.io](https://ora.ai/score/confluent.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Confluent was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Confluent website](https://confluent.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ConnectMachine MCP server | Agent MCP Directory" description: "ConnectMachine: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/connectmachine-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ConnectMachine MCP server | Agent MCP Directory > ConnectMachine: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/connectmachine-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # ConnectMachine: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ConnectMachine at mcp.connectmachine.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ConnectMachine | | --- | --- | | Domain | connectmachine.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for connectmachine.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.connectmachine.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 615 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://mcp.connectmachine.ai/mcp sent initialize result auth-required (HTTP 401) 1188 ms - 20:02:30Z https://mcp.connectmachine.ai/mcp sent initialize result auth-required (HTTP 401) 615 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.connectmachine.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.connectmachine.ai | | Authorization server metadata | mcp.connectmachine.ai | | Registration endpoint | https://mcp.connectmachine.ai/mcp/auth/register | ### The sign-in route, step by step 1. Request `https://mcp.connectmachine.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.connectmachine.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.connectmachine.ai/mcp/auth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ConnectMachine. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.connectmachine/connectmachine | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/connectmachine-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=connectmachine), read 4 November 2026 - [ConnectMachine website](https://connectmachine.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Connie MCP server | Agent MCP Directory" description: "Connie: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/connie-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Connie MCP server | Agent MCP Directory > Connie: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/connie-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Connie: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Connie at mcp.connie.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Connie | | --- | --- | | Domain | connie.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for connie.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.connie.ai | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,295 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://mcp.connie.ai sent initialize result auth-required (HTTP 401) 1675 ms - 20:02:31Z https://mcp.connie.ai sent initialize result auth-required (HTTP 401) 1295 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.connie.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.connie.ai | | Authorization server metadata | mcp.connie.ai | | Registration endpoint | https://mcp.connie.ai/api/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.connie.ai` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.connie.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.connie.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Connie. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.connie/connie | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/connie-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=connie), read 4 November 2026 - [Connie website](https://connie.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Contentful MCP server | Agent MCP Directory" description: "Contentful: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/contentful-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Contentful MCP server | Agent MCP Directory > Contentful: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/contentful-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Contentful: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Contentful; the connector's guess at mcp.contentful.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Contentful | | --- | --- | | Domain | contentful.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 6,420 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for contentful.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.contentful.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 812 ms over 1 attempt | | Documentation | www.contentful.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:11Z https://mcp.contentful.com/mcp sent initialize result auth-required (HTTP 401) 721 ms - 20:01:49Z https://mcp.contentful.com/mcp sent initialize result auth-required (HTTP 401) 812 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.contentful.com | | Authorization server metadata | mcp.contentful.com | | Registration endpoint | https://mcp.contentful.com/register | ### The sign-in route, step by step 1. Request `https://mcp.contentful.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.contentful.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.contentful.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | contentful-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 4.0.14 | | Last publish | 2 November 2026 | | Command names | contentful | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/contentful-com/index.md) ## Sources - [Ora score page for contentful.com](https://ora.ai/score/contentful.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Contentstack MCP server | Agent MCP Directory" description: "Contentstack: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/contentstack-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Contentstack MCP server | Agent MCP Directory > Contentstack: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/contentstack-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Contentstack: MCP server, CLI and agent surfaces Not counted. No source names an endpoint for Contentstack; the connector's guess at mcp.contentstack.com asked for credentials on 4 November 2026 and published no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Contentstack | | --- | --- | | Domain | contentstack.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 67, grade C; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for contentstack.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.contentstack.com/mcp | | --- | --- | | How it was found | mcp.contentstack.com was tried as a guess and answered; see the result below | | Transport | streamable-http | | HTTP status | 403 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,559 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://mcp.contentstack.com/mcp sent initialize result auth-required-no-oauth (HTTP 403) 1675 ms - 20:02:32Z https://mcp.contentstack.com/mcp sent initialize result auth-required-no-oauth (HTTP 403) 1559 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.contentstack.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Contentstack. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/contentstack-com/index.md) ## Sources - [Ora score page for contentstack.com](https://ora.ai/score/contentstack.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where Contentstack was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Contentstack website](https://contentstack.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Context Awesome MCP server | Agent MCP Directory" description: "Context Awesome has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/context-awesome-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Context Awesome MCP server | Agent MCP Directory > Context Awesome has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/context-awesome-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Context Awesome: MCP server, CLI and agent surfaces Yes: Context Awesome runs a public MCP server at www.context-awesome.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: find\_awesome\_section, get\_awesome\_items. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Context Awesome | | --- | --- | | Domain | context-awesome.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for context-awesome.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.context-awesome.com/api/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | mcp-typescript server on vercel 0.1.0 | | Capabilities | tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 880 ms over 1 attempt | ### Tools listed 2 tools - find\_awesome\_section - get\_awesome\_items ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://www.context-awesome.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1039 ms - 20:02:31Z https://www.context-awesome.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 880 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://www.context-awesome.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Context Awesome. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/context-awesome-com/index.md) ## Sources - [Where Context Awesome was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Context Awesome website](https://context-awesome.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Context7 MCP server | Agent MCP Directory" description: "Context7 has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/context7-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Context7 MCP server | Agent MCP Directory > Context7 has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/context7-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Context7: MCP server, CLI and agent surfaces Yes: Context7 runs a public MCP server at mcp.context7.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: resolve-library-id, query-docs. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for context7.com is 81, grade B, read on 5 November 2026. ## Fact sheet | Company | Context7 | | --- | --- | | Domain | context7.com | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 81, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for context7.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.context7.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Context7 4.5.0 | | Capabilities | tools, prompts, resources | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,384 ms over 1 attempt | ### Tools listed 2 tools - resolve-library-id - query-docs ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://mcp.context7.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1420 ms - 20:02:32Z https://mcp.context7.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1384 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.context7.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Context7. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: context7.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: context7.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/context7-com/index.md) ## Sources - [Ora score page for context7.com](https://ora.ai/score/context7.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Context7 was found](https://github.com/mcp/upstash/context7), read 4 November 2026 - [Context7 website](https://context7.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Continue MCP server | Agent MCP Directory" description: "Continue has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/continue-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Continue MCP server | Agent MCP Directory > Continue has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/continue-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Continue: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Continue (docs.continue.dev), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). ## Fact sheet | Company | Continue (registry title: continue.dev) | | --- | --- | | Domain | continue.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 54, grade C; Ora scanned the domain on 18 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for continue.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://docs.continue.dev/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | HTTP status | 404 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 381 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://docs.continue.dev/mcp sent initialize result no-answer (HTTP 404) 683 ms - 20:02:31Z https://docs.continue.dev/mcp sent initialize result no-answer (HTTP 404) 381 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://docs.continue.dev/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Continue. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.continue/docs | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/continue-dev/index.md) ## Sources - [Ora score page for continue.dev](https://ora.ai/score/continue.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 October 2026, read from GET /api/leaderboard) - [Where Continue was found](https://registry.modelcontextprotocol.io/v0/servers?search=dev.continue%2Fdocs), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=continue), read 4 November 2026 - [Continue website](https://continue.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Conveo MCP server | Agent MCP Directory" description: "Conveo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/conveo-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Conveo MCP server | Agent MCP Directory > Conveo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/conveo-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Conveo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Conveo at app.conveo.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Conveo | | --- | --- | | Domain | conveo.ai | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 77, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for conveo.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.conveo.ai/api/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 337 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:00Z https://app.conveo.ai/api/mcp sent initialize result auth-required (HTTP 401) 440 ms - 20:02:32Z https://app.conveo.ai/api/mcp sent initialize result auth-required (HTTP 401) 337 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.conveo.ai/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | app.conveo.ai | | Authorization server metadata | app.conveo.ai | | Registration endpoint | https://app.conveo.ai/register | ### The sign-in route, step by step 1. Request `https://app.conveo.ai/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.conveo.ai/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.conveo.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Conveo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.conveo/conveo | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/conveo-ai/index.md) ## Sources - [Ora score page for conveo.ai](https://ora.ai/score/conveo.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Conveo was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.conveo%2Fconveo), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=conveo), read 4 November 2026 - [Conveo website](https://conveo.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Convex MCP server | Agent MCP Directory" description: "Convex has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/convex-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Convex MCP server | Agent MCP Directory > Convex has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/convex-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Convex: MCP server, CLI and agent surfaces Yes: Convex runs a public MCP server at mcp.convex.dev, found by guessing the subdomain, and it listed 4 tools to a client with no credentials on 4 November 2026. Examples: start\_convex\_app, add\_convex\_to\_existing\_project, get\_convex\_scaling\_guidance. It speaks streamable-http, protocol 2025-06-18. A CLI is on record: convex on npm. ## Fact sheet | Company | Convex | | --- | --- | | Domain | convex.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 71, grade B; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for convex.dev, a vendor-published score) | | Company found through | the vendor's own documentation | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.convex.dev/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | mcp-typescript server on vercel 0.1.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,018 ms over 1 attempt | | Documentation | docs.convex.dev | ### Tools listed 4 tools - start\_convex\_app - add\_convex\_to\_existing\_project - get\_convex\_scaling\_guidance - get\_runbook ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:01Z https://mcp.convex.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 933 ms - 20:02:33Z https://mcp.convex.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1018 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.convex.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | convex on npm (page) | | --- | --- | | Exists | yes | | Latest version | 1.49.0 | | Last publish | 30 October 2026 | | Command names | convex | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/convex-dev/index.md) ## Sources - [Convex MCP documentation](https://docs.convex.dev/ai/convex-mcp-server), read 4 November 2026 - [Ora score page for convex.dev](https://ora.ai/score/convex.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/score) - [Convex website](https://convex.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CookieYes MCP server | Agent MCP Directory" description: "CookieYes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Legal & Compliance." canonical: https://agentmcpdirectory.com/directory/cookieyes-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CookieYes MCP server | Agent MCP Directory > CookieYes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Legal & Compliance. Source: https://agentmcpdirectory.com/directory/cookieyes-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CookieYes: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for CookieYes at app.cookieyes.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | CookieYes | | --- | --- | | Domain | cookieyes.com | | Category | Legal & Compliance (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,765 on the list of 4 November 2026 | | Ora score | 79, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cookieyes.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.cookieyes.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 430 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:00Z https://app.cookieyes.com/mcp sent initialize result auth-required (HTTP 401) 385 ms - 20:01:35Z https://app.cookieyes.com/mcp sent initialize result auth-required (HTTP 401) 430 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.cookieyes.com/.well-known/oauth-protected-resource" | | Protected resource metadata | app.cookieyes.com | | Authorization server metadata | app.cookieyes.com | | Registration endpoint | https://app.cookieyes.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://app.cookieyes.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.cookieyes.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.cookieyes.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CookieYes. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Found: cookieyes.com/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.cookieyes/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cookieyes-com/index.md) ## Sources - [Ora score page for cookieyes.com](https://ora.ai/score/cookieyes.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where CookieYes was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.cookieyes%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cookieyes), read 4 November 2026 - [CookieYes website](https://cookieyes.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Coralogix MCP server | Agent MCP Directory" description: "Does Coralogix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/coralogix-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Coralogix MCP server | Agent MCP Directory > Does Coralogix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/coralogix-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Coralogix: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Coralogix (coralogix.com), so the connector had nothing to connect to. Ora's cached score for coralogix.com is 79, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Coralogix | | --- | --- | | Domain | coralogix.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 79, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for coralogix.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Coralogix. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for coralogix.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (com.coralogix/mcp-server) | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Coralogix. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: coralogix.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: coralogix.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.coralogix/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coralogix-com/index.md) ## Sources - [Ora score page for coralogix.com](https://ora.ai/score/coralogix.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Coralogix was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.coralogix%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=coralogix), read 4 November 2026 - [Coralogix website](https://coralogix.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CoreMedia MCP server | Agent MCP Directory" description: "Does CoreMedia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/coremedia-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CoreMedia MCP server | Agent MCP Directory > Does CoreMedia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/coremedia-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CoreMedia: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for CoreMedia (coremedia.com), so the connector had nothing to connect to. Ora's cached score for coremedia.com is 57, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | CoreMedia (registry title: coremedia.com) | | --- | --- | | Domain | coremedia.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 57, grade C; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for coremedia.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for CoreMedia. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for coremedia.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for CoreMedia. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coremedia-com/index.md) ## Sources - [Ora score page for coremedia.com](https://ora.ai/score/coremedia.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where CoreMedia was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [CoreMedia website](https://coremedia.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CoreNexis API MCP server | Agent MCP Directory" description: "CoreNexis API: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/corenexis-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CoreNexis API MCP server | Agent MCP Directory > CoreNexis API: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/corenexis-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CoreNexis API: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for CoreNexis API at cashly.corenexis.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | CoreNexis API | | --- | --- | | Domain | corenexis.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for corenexis.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://cashly.corenexis.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 542 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:02Z https://cashly.corenexis.com/api/mcp sent initialize result auth-required (HTTP 401) 1255 ms - 20:02:33Z https://cashly.corenexis.com/api/mcp sent initialize result auth-required (HTTP 401) 542 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="cashly", resource_metadata="https://cashly.corenexis.com/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | cashly.corenexis.com | | Authorization server metadata | cashly.corenexis.com | | Registration endpoint | https://cashly.corenexis.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://cashly.corenexis.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://cashly.corenexis.com/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://cashly.corenexis.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CoreNexis API. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.corenexis/api, com.corenexis/cashly | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/corenexis-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=corenexis), read 4 November 2026 - [CoreNexis API website](https://corenexis.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CoreWeave MCP server | Agent MCP Directory" description: "Does CoreWeave have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/coreweave-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CoreWeave MCP server | Agent MCP Directory > Does CoreWeave have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/coreweave-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # CoreWeave: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for CoreWeave (coreweave.com), so the connector had nothing to connect to. Ora's cached score for coreweave.com is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | CoreWeave | | --- | --- | | Domain | coreweave.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 8 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for coreweave.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for CoreWeave. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for coreweave.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for CoreWeave. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coreweave-com/index.md) ## Sources - [Ora score page for coreweave.com](https://ora.ai/score/coreweave.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 September 2026, read from GET /api/leaderboard) - [Where CoreWeave was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [CoreWeave website](https://coreweave.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "COROS MCP server | Agent MCP Directory" description: "COROS: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/coros-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # COROS MCP server | Agent MCP Directory > COROS: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/coros-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # COROS: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for COROS at mcpus.coros.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | COROS | | --- | --- | | Domain | coros.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 45, grade D; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for coros.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcpus.coros.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,677 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:03Z https://mcpus.coros.com/mcp sent initialize result auth-required (HTTP 401) 2173 ms - 20:02:34Z https://mcpus.coros.com/mcp sent initialize result auth-required (HTTP 401) 1677 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcpus.coros.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcpus.coros.com | | Authorization server metadata | mcpus.coros.com | | Registration endpoint | https://mcpus.coros.com/connect/register | ### The sign-in route, step by step 1. Request `https://mcpus.coros.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcpus.coros.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcpus.coros.com/connect/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for COROS. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coros-com/index.md) ## Sources - [Ora score page for coros.com](https://ora.ai/score/coros.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/score) - [Where COROS was found](https://github.com/mcp/coroslab/COROS-MCP), read 4 November 2026 - [COROS website](https://coros.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Corsair MCP server | Agent MCP Directory" description: "Corsair: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/corsair-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Corsair MCP server | Agent MCP Directory > Corsair: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/corsair-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Corsair: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Corsair at mcp.corsair.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Corsair | | --- | --- | | Domain | corsair.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 67, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for corsair.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.corsair.dev/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,547 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:03Z https://mcp.corsair.dev/mcp sent initialize result auth-required (HTTP 401) 1972 ms - 20:02:34Z https://mcp.corsair.dev/mcp sent initialize result auth-required (HTTP 401) 1547 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.corsair.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.corsair.dev | | Authorization server metadata | hub.corsair.dev | | Registration endpoint | https://hub.corsair.dev/api/lug/register | ### The sign-in route, step by step 1. Request `https://mcp.corsair.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.corsair.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://hub.corsair.dev/api/lug/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Corsair. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.corsair/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/corsair-dev/index.md) ## Sources - [Ora score page for corsair.dev](https://ora.ai/score/corsair.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/leaderboard) - [Where Corsair was found](https://registry.modelcontextprotocol.io/v0/servers?search=dev.corsair%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=corsair), read 4 November 2026 - [Corsair website](https://corsair.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cortex MCP server | Agent MCP Directory" description: "Cortex: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cortex-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cortex MCP server | Agent MCP Directory > Cortex: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cortex-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cortex: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Cortex at mcp.cortex.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cortex | | --- | --- | | Domain | cortex.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 57, grade C; Ora scanned the domain on 20 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cortex.io, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cortex.io/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 735 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:03Z https://mcp.cortex.io/mcp sent initialize result auth-required (HTTP 401) 1065 ms - 20:02:34Z https://mcp.cortex.io/mcp sent initialize result auth-required (HTTP 401) 735 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.cortex.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.cortex.io | | Authorization server metadata | mcp.cortex.io | | Registration endpoint | https://mcp.cortex.io/register | | Client ID metadata documents | supported | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.cortex.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.cortex.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.cortex.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cortex. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cortex-io/index.md) ## Sources - [Ora score page for cortex.io](https://ora.ai/score/cortex.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 August 2026, read from GET /api/leaderboard) - [Where Cortex was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Cortex website](https://cortex.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cosine MCP server | Agent MCP Directory" description: "Does Cosine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cosine-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cosine MCP server | Agent MCP Directory > Does Cosine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cosine-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cosine: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cosine (cosine.sh), so the connector had nothing to connect to. Ora's cached score for cosine.sh is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cosine (registry title: cosine.sh) | | --- | --- | | Domain | cosine.sh | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 30 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cosine.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cosine. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cosine.sh, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cosine. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cosine-sh/index.md) ## Sources - [Ora score page for cosine.sh](https://ora.ai/score/cosine.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 August 2026, read from GET /api/leaderboard) - [Where Cosine was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cosine website](https://cosine.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cosmic MCP server | Agent MCP Directory" description: "Does Cosmic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cosmicjs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cosmic MCP server | Agent MCP Directory > Does Cosmic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cosmicjs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cosmic: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cosmic (cosmicjs.com), so the connector had nothing to connect to. Ora's cached score for cosmicjs.com is 75, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Cosmic | | --- | --- | | Domain | cosmicjs.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 75, grade B; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cosmicjs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cosmic. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cosmicjs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (com.cosmicjs/mcp) | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cosmic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.cosmicjs.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.cosmicjs/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cosmicjs-com/index.md) ## Sources - [Ora score page for cosmicjs.com](https://ora.ai/score/cosmicjs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Cosmic was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.cosmicjs%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cosmicjs), read 4 November 2026 - [Cosmic website](https://cosmicjs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Costory MCP server | Agent MCP Directory" description: "Costory: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/costory-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Costory MCP server | Agent MCP Directory > Costory: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/costory-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Costory: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Costory at app-api.costory.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Costory (registry title: Costory FinOps MCP) | | --- | --- | | Domain | costory.io | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for costory.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app-api.costory.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 367 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:03Z https://app-api.costory.io/mcp sent initialize result auth-required (HTTP 401) 803 ms - 20:02:34Z https://app-api.costory.io/mcp sent initialize result auth-required (HTTP 401) 367 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata=https://app-api.costory.io/.well-known/oauth-protected-resource/mcp | | Protected resource metadata | app-api.costory.io | | Authorization server metadata | clerk.costory.io | | Registration endpoint | https://clerk.costory.io/oauth/register | ### The sign-in route, step by step 1. Request `https://app-api.costory.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app-api.costory.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.costory.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Costory. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.costory/finops | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/costory-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=costory), read 4 November 2026 - [Costory website](https://costory.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Courier MCP server | Agent MCP Directory" description: "Courier has an open MCP server with 173 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/courier-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Courier MCP server | Agent MCP Directory > Courier has an open MCP server with 173 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/courier-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Courier: MCP server, CLI and agent surfaces Yes: Courier runs a public MCP server at mcp.courier.com, found by guessing the subdomain, and it listed 173 tools to a client with no credentials on 4 November 2026. Examples: list\_messages, get\_message, get\_message\_content. It speaks streamable-http, protocol 2025-11-25. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | Courier (registry title: courier.com) | | --- | --- | | Domain | courier.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 57, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for courier.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.courier.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | @trycourier/courier-mcp 1.3.7 | | Capabilities | tools | | Tools | 173 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,606 ms over 1 attempt | ### Tools listed 173 tools; the first 40 names are recorded - list\_messages - get\_message - get\_message\_content - get\_message\_history - list\_notifications - get\_notification\_content - get\_notification\_draft\_content - create\_notification - get\_notification - replace\_notification - put\_notification\_content - put\_notification\_element - put\_notification\_locale - list\_notification\_versions - list\_notification\_checks - list\_providers - get\_provider - list\_provider\_catalog - get\_routing\_strategy - list\_routing\_strategies - list\_preference\_sections - get\_preference\_section - list\_preference\_topics - get\_preference\_topic - create\_journey - get\_journey - replace\_journey - create\_journey\_template - put\_journey\_template\_content - put\_journey\_template\_locale - list\_journeys - list\_journey\_templates - get\_journey\_template - get\_journey\_template\_content - get\_notification\_metrics - get\_tenant - list\_tenants - list\_tenant\_users - get\_user\_profile\_by\_id - get\_user\_list\_subscriptions ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:04Z https://mcp.courier.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1438 ms - 20:02:35Z https://mcp.courier.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1606 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.courier.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Courier. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/courier-com/index.md) ## Sources - [Ora score page for courier.com](https://ora.ai/score/courier.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Where Courier was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Courier website](https://courier.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Coval MCP server | Agent MCP Directory" description: "Coval: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/coval-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Coval MCP server | Agent MCP Directory > Coval: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/coval-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Coval: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Coval; the connector's guess at mcp.coval.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Coval (registry title: coval.dev) | | --- | --- | | Domain | coval.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 65, grade C; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for coval.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.coval.dev/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,063 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:04Z https://mcp.coval.dev/mcp sent initialize result auth-required (HTTP 401) 1331 ms - 20:02:35Z https://mcp.coval.dev/mcp sent initialize result auth-required (HTTP 401) 1063 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata=https://mcp.coval.dev/.well-known/oauth-protected-resource/mcp | | Protected resource metadata | mcp.coval.dev | | Authorization server metadata | clerk.coval.dev | | Registration endpoint | https://clerk.coval.dev/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.coval.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.coval.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.coval.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Coval. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/coval-dev/index.md) ## Sources - [Ora score page for coval.dev](https://ora.ai/score/coval.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/leaderboard) - [Where Coval was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Coval website](https://coval.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cpln MCP server | Agent MCP Directory" description: "Cpln: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cpln-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cpln MCP server | Agent MCP Directory > Cpln: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cpln-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cpln: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Cpln at mcp.cpln.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cpln (registry title: Control Plane) | | --- | --- | | Domain | cpln.io | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for cpln.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cpln.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,505 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:04Z https://mcp.cpln.io/mcp sent initialize result auth-required (HTTP 401) 1590 ms - 20:02:36Z https://mcp.cpln.io/mcp sent initialize result auth-required (HTTP 401) 1505 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://mcp.cpln.io/mcp", resource_metadata="https://mcp.cpln.io/.well-known/oauth-protected-resource/mcp", scope="openid offline_access" | | Protected resource metadata | mcp.cpln.io | | Authorization server metadata | auth.cpln.io | | Registration endpoint | https://auth.cpln.io/api/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.cpln.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.cpln.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.cpln.io/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cpln. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.cpln/control-plane | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cpln-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cpln), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Craft MCP server | Agent MCP Directory" description: "Craft: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/craft-do site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Craft MCP server | Agent MCP Directory > Craft: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/craft-do Site: Agent MCP Directory Last reviewed: 2026-11-05 # Craft: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Craft at mcp.craft.do answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Craft | | --- | --- | | Domain | craft.do | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 62, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for craft.do, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.craft.do/my/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,718 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:04Z https://mcp.craft.do/my/mcp sent initialize result auth-required (HTTP 401) 1241 ms - 20:02:36Z https://mcp.craft.do/my/mcp sent initialize result auth-required (HTTP 401) 1718 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.craft.do/.well-known/oauth-protected-resource/my/mcp" | | Protected resource metadata | mcp.craft.do | | Authorization server metadata | mcp.craft.do | | Registration endpoint | https://mcp.craft.do/my/auth/register | ### The sign-in route, step by step 1. Request `https://mcp.craft.do/my/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.craft.do/.well-known/oauth-protected-resource/my/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.craft.do/my/auth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Craft. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: do.craft.mcp/server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/craft-do/index.md) ## Sources - [Ora score page for craft.do](https://ora.ai/score/craft.do?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Craft was found](https://registry.modelcontextprotocol.io/v0/servers?search=do.craft.mcp%2Fserver), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=craft), read 4 November 2026 - [Craft website](https://craft.do), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Craft CMS MCP server | Agent MCP Directory" description: "Does Craft CMS have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/craftcms-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Craft CMS MCP server | Agent MCP Directory > Does Craft CMS have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/craftcms-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Craft CMS: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Craft CMS (craftcms.com), so the connector had nothing to connect to. Ora's cached score for craftcms.com is 44, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Craft CMS (registry title: craftcms.com) | | --- | --- | | Domain | craftcms.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 44, grade D; Ora scanned the domain on 7 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for craftcms.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Craft CMS. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for craftcms.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Craft CMS. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/craftcms-com/index.md) ## Sources - [Ora score page for craftcms.com](https://ora.ai/score/craftcms.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 August 2026, read from GET /api/leaderboard) - [Where Craft CMS was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Craft CMS website](https://craftcms.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Crakseo MCP server | Agent MCP Directory" description: "Crakseo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/crakseo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Crakseo MCP server | Agent MCP Directory > Crakseo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/crakseo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Crakseo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Crakseo at crakseo.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Crakseo (registry title: Free Google Search Console (GSC) & Bing Webmaster Tools) | | --- | --- | | Domain | crakseo.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for crakseo.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://crakseo.com/mcp/seo | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,189 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:05Z https://crakseo.com/mcp/seo sent initialize result auth-required (HTTP 401) 1328 ms - 20:02:36Z https://crakseo.com/mcp/seo sent initialize result auth-required (HTTP 401) 1189 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://crakseo.com/.well-known/oauth-protected-resource/mcp/seo", error="invalid_token" | | Protected resource metadata | crakseo.com | | Authorization server metadata | crakseo.com | | Registration endpoint | https://crakseo.com/api/indexing/oauth/register | ### The sign-in route, step by step 1. Request `https://crakseo.com/mcp/seo` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://crakseo.com/.well-known/oauth-protected-resource/mcp/seo` to find the authorization server. 3. Register a client at the registration endpoint `https://crakseo.com/api/indexing/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Crakseo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: crakseo.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.crakseo/ai-visibility, com.crakseo/backlinks, com.crakseo/keyword-research and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/crakseo-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=crakseo), read 4 November 2026 - [Crakseo website](https://crakseo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cronitor MCP server | Agent MCP Directory" description: "Cronitor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/cronitor-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cronitor MCP server | Agent MCP Directory > Cronitor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/cronitor-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cronitor: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Cronitor at cronitor.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cronitor | | --- | --- | | Domain | cronitor.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cronitor.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://cronitor.io/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,006 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:06Z https://cronitor.io/mcp sent initialize result auth-required (HTTP 401) 2383 ms - 20:02:37Z https://cronitor.io/mcp sent initialize result auth-required (HTTP 401) 2006 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://cronitor.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | cronitor.io | | Authorization server metadata | auth.cronitor.io | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://cronitor.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://cronitor.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cronitor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: cronitor.io/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.cronitor/cronitor | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cronitor-io/index.md) ## Sources - [Ora score page for cronitor.io](https://ora.ai/score/cronitor.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Cronitor was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.cronitor%2Fcronitor), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cronitor), read 4 November 2026 - [Cronitor website](https://cronitor.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CryptoAPIs IO MCP server | Agent MCP Directory" description: "CryptoAPIs IO has an open MCP server with 60 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cryptoapis-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CryptoAPIs IO MCP server | Agent MCP Directory > CryptoAPIs IO has an open MCP server with 60 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cryptoapis-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # CryptoAPIs IO: MCP server, CLI and agent surfaces Yes: CryptoAPIs IO runs a public MCP server at ai.cryptoapis.io that listed 60 tools to a client with no credentials on 4 November 2026. Examples: address\_history\_\_manage\_address, address\_history\_\_evm\_address\_history, address\_history\_\_utxo\_address\_history. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | CryptoAPIs IO | | --- | --- | | Domain | cryptoapis.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for cryptoapis.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.cryptoapis.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | cryptoapis-mcp-http-server 1.0.0 | | Capabilities | tools | | Tools | 60 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 729 ms over 1 attempt | ### Tools listed 60 tools; the first 40 names are recorded - address\_history\_\_manage\_address - address\_history\_\_evm\_address\_history - address\_history\_\_utxo\_address\_history - address\_history\_\_system\_info - address\_latest\_\_evm\_address\_latest - address\_latest\_\_utxo\_address\_latest - address\_latest\_\_solana\_address\_latest - address\_latest\_\_xrp\_address\_latest - address\_latest\_\_kaspa\_address\_latest - address\_latest\_\_system\_info - aml\_\_aml - aml\_\_system\_info - block\_data\_\_evm\_block\_data - block\_data\_\_utxo\_block\_data - block\_data\_\_xrp\_block\_data - block\_data\_\_system\_info - blockchain\_events\_\_blockchain\_events\_manage - blockchain\_events\_\_blockchain\_events\_create - blockchain\_events\_\_system\_info - blockchain\_fees\_\_blockchain\_fees\_utxo - blockchain\_fees\_\_blockchain\_fees\_evm - blockchain\_fees\_\_blockchain\_fees\_xrp - blockchain\_fees\_\_blockchain\_fees\_tezos - blockchain\_fees\_\_blockchain\_fees\_solana - blockchain\_fees\_\_system\_info - broadcast\_\_broadcast\_signed\_transaction - broadcast\_\_system\_info - contracts\_\_evm\_contract\_data - contracts\_\_solana\_contract\_data - contracts\_\_system\_info - hd\_wallet\_\_manage\_hd\_wallet - hd\_wallet\_\_hd\_wallet\_data\_utxo - hd\_wallet\_\_hd\_wallet\_data\_evm - hd\_wallet\_\_hd\_wallet\_data\_xrp - hd\_wallet\_\_system\_info - market\_data\_\_market\_data\_metadata - market\_data\_\_market\_data\_exchange\_rates - market\_data\_\_market\_data\_assets - market\_data\_\_system\_info - prepare\_transactions\_\_prepare\_transactions\_evm ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:05Z https://ai.cryptoapis.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 908 ms - 20:02:36Z https://ai.cryptoapis.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 729 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://ai.cryptoapis.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CryptoAPIs IO. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cryptoapis-io/index.md) ## Sources - [CryptoAPIs IO website](https://cryptoapis.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CTGT MCP server | Agent MCP Directory" description: "Does CTGT have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/ctgt-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CTGT MCP server | Agent MCP Directory > Does CTGT have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/ctgt-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # CTGT: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for CTGT (ctgt.ai), so the connector had nothing to connect to. Ora's cached score for ctgt.ai is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | CTGT (registry title: ctgt.ai) | | --- | --- | | Domain | ctgt.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 30 July 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ctgt.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for CTGT. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ctgt.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for CTGT. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ctgt-ai/index.md) ## Sources - [Ora score page for ctgt.ai](https://ora.ai/score/ctgt.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 July 2026, read from GET /api/leaderboard) - [Where CTGT was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [CTGT website](https://ctgt.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "cubic MCP server | Agent MCP Directory" description: "cubic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cubic-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # cubic MCP server | Agent MCP Directory > cubic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cubic-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # cubic: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for cubic at www.cubic.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | cubic | | --- | --- | | Domain | cubic.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 82, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cubic.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.cubic.dev/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 972 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:06Z https://www.cubic.dev/api/mcp sent initialize result auth-required (HTTP 401) 865 ms - 20:02:36Z https://www.cubic.dev/api/mcp sent initialize result auth-required (HTTP 401) 972 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.cubic.dev/.well-known/oauth-protected-resource/api/mcp", scope="openid email profile" | | Protected resource metadata | www.cubic.dev | | Authorization server metadata | mcafvrhahbqdwfrtncql.supabase.co | | Registration endpoint | https://mcafvrhahbqdwfrtncql.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://www.cubic.dev/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.cubic.dev/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcafvrhahbqdwfrtncql.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for cubic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | Found: cubic.dev/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: cubic.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.cubic/cubic | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cubic-dev/index.md) ## Sources - [Ora score page for cubic.dev](https://ora.ai/score/cubic.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cubic), read 4 November 2026 - [cubic website](https://cubic.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cursor MCP server | Agent MCP Directory" description: "Does Cursor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cursor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cursor MCP server | Agent MCP Directory > Does Cursor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cursor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cursor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cursor (cursor.com), so the connector had nothing to connect to. Ora's cached score for cursor.com is 74, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cursor | | --- | --- | | Domain | cursor.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 3,133 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cursor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cursor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cursor.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cursor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cursor-com/index.md) ## Sources - [Ora score page for cursor.com](https://ora.ai/score/cursor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Cursor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cursor website](https://cursor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CustomDomain™ MCP server | Agent MCP Directory" description: "CustomDomain™: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/customdomain-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CustomDomain™ MCP server | Agent MCP Directory > CustomDomain™: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/customdomain-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # CustomDomain™: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for CustomDomain™ at mcp.customdomain.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | CustomDomain™ | | --- | --- | | Domain | customdomain.ai | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for customdomain.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.customdomain.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,180 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:06Z https://mcp.customdomain.ai/mcp sent initialize result auth-required (HTTP 401) 1229 ms - 20:02:37Z https://mcp.customdomain.ai/mcp sent initialize result auth-required (HTTP 401) 1180 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", error="invalid_token", resource_metadata="https://mcp.customdomain.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.customdomain.ai | | Authorization server metadata | api.customdomain.ai | | Registration endpoint | https://api.customdomain.ai/oauth/agent/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.customdomain.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.customdomain.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.customdomain.ai/oauth/agent/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CustomDomain™. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.customdomain/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/customdomain-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=customdomain), read 4 November 2026 - [CustomDomain™ website](https://customdomain.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CustomGPT.ai MCP server | Agent MCP Directory" description: "CustomGPT.ai has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/customgpt-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CustomGPT.ai MCP server | Agent MCP Directory > CustomGPT.ai has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/customgpt-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # CustomGPT.ai: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for CustomGPT.ai (mcp.customgpt.ai), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 200, GET HTTP 200 application/json). ## Fact sheet | Company | CustomGPT.ai | | --- | --- | | Domain | customgpt.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for customgpt.ai when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.customgpt.ai | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | HTTP status | 200 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 878 ms over 2 attempts | | Result | no MCP answer (POST HTTP 200, GET HTTP 200 application/json) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:06Z https://mcp.customgpt.ai sent initialize result no-answer (HTTP 200) 1213 ms - 20:02:36Z https://mcp.customgpt.ai sent initialize result no-answer (HTTP 200) 878 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | API (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.customgpt.ai`. The connector could not tell what it wants: no MCP answer (POST HTTP 200, GET HTTP 200 application/json). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CustomGPT.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/customgpt-ai/index.md) ## Sources - [Where CustomGPT.ai was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [CustomGPT.ai website](https://customgpt.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cyberdesk MCP server | Agent MCP Directory" description: "Does Cyberdesk have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cyberdesk-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cyberdesk MCP server | Agent MCP Directory > Does Cyberdesk have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/cyberdesk-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cyberdesk: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Cyberdesk (cyberdesk.io), so the connector had nothing to connect to. Ora's cached score for cyberdesk.io is 74, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Cyberdesk (registry title: cyberdesk.io) | | --- | --- | | Domain | cyberdesk.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 74, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cyberdesk.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Cyberdesk. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for cyberdesk.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Cyberdesk. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cyberdesk-io/index.md) ## Sources - [Ora score page for cyberdesk.io](https://ora.ai/score/cyberdesk.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Cyberdesk was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Cyberdesk website](https://cyberdesk.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "cyon MCP server | Agent MCP Directory" description: "cyon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/cyon-ch site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # cyon MCP server | Agent MCP Directory > cyon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/cyon-ch Site: Agent MCP Directory Last reviewed: 2026-11-05 # cyon: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for cyon at mcp.cyon.ch answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | cyon | | --- | --- | | Domain | cyon.ch | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,911 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for cyon.ch when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cyon.ch/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 716 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:06Z https://mcp.cyon.ch/mcp sent initialize result auth-required (HTTP 401) 664 ms - 20:01:43Z https://mcp.cyon.ch/mcp sent initialize result auth-required (HTTP 401) 716 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.cyon.ch/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.cyon.ch | | Authorization server metadata | my.cyon.ch | | Registration endpoint | https://my.cyon.ch/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.cyon.ch/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.cyon.ch/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://my.cyon.ch/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for cyon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ch.cyon/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cyon-ch/index.md) ## Sources - [Where cyon was found](https://registry.modelcontextprotocol.io/v0/servers?search=ch.cyon%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cyon), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Cypress Cloud MCP server | Agent MCP Directory" description: "Cypress Cloud: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/cypress-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Cypress Cloud MCP server | Agent MCP Directory > Cypress Cloud: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/cypress-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cypress Cloud: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Cypress Cloud at mcp.cypress.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Cypress Cloud (registry title: Cypress Cloud MCP) | | --- | --- | | Domain | cypress.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 62, grade C; Ora scanned the domain on 30 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for cypress.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.cypress.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,290 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:07Z https://mcp.cypress.io/mcp sent initialize result auth-required (HTTP 401) 1330 ms - 20:02:38Z https://mcp.cypress.io/mcp sent initialize result auth-required (HTTP 401) 1290 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="cypress-cloud-mcp", resource_metadata="https://mcp.cypress.io/.well-known/oauth-protected-resource/mcp", scope="mcp:tools" | | Protected resource metadata | mcp.cypress.io | | Authorization server metadata | cloud.cypress.io | | Registration endpoint | https://cloud.cypress.io/oauth/mcp/register | ### The sign-in route, step by step 1. Request `https://mcp.cypress.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.cypress.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://cloud.cypress.io/oauth/mcp/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Cypress Cloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.cypress.mcp/cypress-cloud | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/cypress-io/index.md) ## Sources - [Ora score page for cypress.io](https://ora.ai/score/cypress.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 September 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=cypress), read 4 November 2026 - [Cypress Cloud website](https://cypress.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dabloons MCP server | Agent MCP Directory" description: "Dabloons: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/dabloons-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dabloons MCP server | Agent MCP Directory > Dabloons: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/dabloons-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dabloons: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Dabloons at dabloons.net answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Dabloons | | --- | --- | | Domain | dabloons.net | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for dabloons.net when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://dabloons.net/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 203 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:07Z https://dabloons.net/mcp sent initialize result auth-required (HTTP 401) 682 ms - 20:02:37Z https://dabloons.net/mcp sent initialize result auth-required (HTTP 401) 203 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://dabloons.net/.well-known/oauth-protected-resource/mcp", scope="agent" | | Protected resource metadata | dabloons.net | | Authorization server metadata | dabloons.net | | Registration endpoint | https://dabloons.net/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://dabloons.net/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://dabloons.net/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://dabloons.net/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dabloons. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dabloons-net/index.md) ## Sources - [Dabloons website](https://dabloons.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Daft MCP server | Agent MCP Directory" description: "Does Daft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/daft-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Daft MCP server | Agent MCP Directory > Does Daft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/daft-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Daft: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Daft (daft.ai), so the connector had nothing to connect to. Ora's cached score for daft.ai is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Daft (registry title: daft.ai) | | --- | --- | | Domain | daft.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for daft.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Daft. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for daft.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Daft. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/daft-ai/index.md) ## Sources - [Ora score page for daft.ai](https://ora.ai/score/daft.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Daft was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Daft website](https://daft.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dagger MCP server | Agent MCP Directory" description: "Does Dagger have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dagger-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dagger MCP server | Agent MCP Directory > Does Dagger have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/dagger-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dagger: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Dagger (dagger.io), so the connector had nothing to connect to. Ora's cached score for dagger.io is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Dagger (registry title: dagger.io) | | --- | --- | | Domain | dagger.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dagger.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Dagger. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for dagger.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Dagger. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dagger-io/index.md) ## Sources - [Ora score page for dagger.io](https://ora.ai/score/dagger.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Dagger was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Dagger website](https://dagger.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dailybot MCP server | Agent MCP Directory" description: "Does Dailybot have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dailybot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dailybot MCP server | Agent MCP Directory > Does Dailybot have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/dailybot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dailybot: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Dailybot (dailybot.com), so the connector had nothing to connect to. Ora's cached score for dailybot.com is 76, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Dailybot (registry title: dailybot.com) | | --- | --- | | Domain | dailybot.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 76, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dailybot.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Dailybot. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for dailybot.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Dailybot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.dailybot.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: dailybot.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dailybot-com/index.md) ## Sources - [Ora score page for dailybot.com](https://ora.ai/score/dailybot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Dailybot was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Dailybot website](https://dailybot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dappier MCP server | Agent MCP Directory" description: "Dappier has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/dappier-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dappier MCP server | Agent MCP Directory > Dappier has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/dappier-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dappier: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Dappier (mcp.dappier.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 402, GET HTTP 402 text/plain;charset=utf-8). ## Fact sheet | Company | Dappier | | --- | --- | | Domain | dappier.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for dappier.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dappier.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | HTTP status | 402 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 130 ms over 2 attempts | | Result | no MCP answer (POST HTTP 402, GET HTTP 402 text/plain;charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:08Z https://mcp.dappier.com/mcp sent initialize result no-answer (HTTP 402) 692 ms - 20:02:37Z https://mcp.dappier.com/mcp sent initialize result no-answer (HTTP 402) 130 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.dappier.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 402, GET HTTP 402 text/plain;charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dappier. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dappier-com/index.md) ## Sources - [Where Dappier was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Dappier website](https://dappier.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "dari.dev MCP server | Agent MCP Directory" description: "Does dari.dev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dari-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # dari.dev MCP server | Agent MCP Directory > Does dari.dev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/dari-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # dari.dev: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for dari.dev, so the connector had nothing to connect to. Ora's cached score for dari.dev is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | dari.dev | | --- | --- | | Domain | dari.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dari.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for dari.dev. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for dari.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for dari.dev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dari-dev/index.md) ## Sources - [Ora score page for dari.dev](https://ora.ai/score/dari.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/leaderboard) - [Where dari.dev was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [dari.dev website](https://dari.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dart MCP server | Agent MCP Directory" description: "Dart: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dartai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dart MCP server | Agent MCP Directory > Dart: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dartai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dart: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Dart at mcp.dartai.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Dart | | --- | --- | | Domain | dartai.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 57, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dartai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dartai.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,084 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:08Z https://mcp.dartai.com/mcp sent initialize result auth-required (HTTP 401) 1053 ms - 20:02:38Z https://mcp.dartai.com/mcp sent initialize result auth-required (HTTP 401) 1084 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer scope="read write", resource_metadata="https://mcp.dartai.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.dartai.com | | Authorization server metadata | mcp.dartai.com | | Registration endpoint | https://mcp.dartai.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.dartai.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.dartai.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.dartai.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dart. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.dartai/dart | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dartai-com/index.md) ## Sources - [Ora score page for dartai.com](https://ora.ai/score/dartai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where Dart was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.dartai%2Fdart), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=dartai), read 4 November 2026 - [Dart website](https://dartai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Datadog MCP server | Agent MCP Directory" description: "Datadog: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/datadoghq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Datadog MCP server | Agent MCP Directory > Datadog: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/datadoghq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Datadog: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Datadog at mcp.datadoghq.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Datadog | | --- | --- | | Domain | datadoghq.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 281 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for datadoghq.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.datadoghq.com/api/unstable/mcp-server/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,102 ms over 1 attempt | | Documentation | docs.datadoghq.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:53Z https://mcp.datadoghq.com/api/unstable/mcp-server/mcp sent initialize result auth-required (HTTP 401) 1031 ms - 20:01:29Z https://mcp.datadoghq.com/api/unstable/mcp-server/mcp sent initialize result auth-required (HTTP 401) 1102 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.datadoghq.com/.well-known/oauth-protected-resource/api/unstable/mcp-server/mcp" | | Protected resource metadata | mcp.datadoghq.com | | Authorization server metadata | mcp.datadoghq.com | | Registration endpoint | https://app.datadoghq.com/api/v2/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.datadoghq.com/.well-known/oauth-protected-resource/api/unstable/mcp-server/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.datadoghq.com/api/v2/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @datadog/datadog-ci on npm (page) | | --- | --- | | Exists | yes | | Latest version | 5.27.0 | | Last publish | 4 November 2026 | | Command names | datadog-ci | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/datadoghq-com/index.md) ## Sources - [Datadog MCP documentation](https://docs.datadoghq.com/bits_ai/mcp_server/), read 4 November 2026 - [Ora score page for datadoghq.com](https://ora.ai/score/datadoghq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/score) - [Datadog website](https://datadoghq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Datasaur MCP server | Agent MCP Directory" description: "Does Datasaur have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/datasaur-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Datasaur MCP server | Agent MCP Directory > Does Datasaur have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/datasaur-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Datasaur: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Datasaur (datasaur.ai), so the connector had nothing to connect to. Ora's cached score for datasaur.ai is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Datasaur (registry title: datasaur.ai) | | --- | --- | | Domain | datasaur.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for datasaur.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Datasaur. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for datasaur.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Datasaur. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/datasaur-ai/index.md) ## Sources - [Ora score page for datasaur.ai](https://ora.ai/score/datasaur.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where Datasaur was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Datasaur website](https://datasaur.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DC Hub MCP server | Agent MCP Directory" description: "DC Hub has an open MCP server with 94 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dchub-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DC Hub MCP server | Agent MCP Directory > DC Hub has an open MCP server with 94 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dchub-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # DC Hub: MCP server, CLI and agent surfaces Yes: DC Hub runs a public MCP server at dchub.cloud that listed 94 tools to a client with no credentials on 4 November 2026. Examples: execute\_plan, claim\_free\_key, search. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | DC Hub (registry title: DC Hub: Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber) | | --- | --- | | Domain | dchub.cloud | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for dchub.cloud when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://dchub.cloud/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | DC Hub Intelligence 2.12.45 | | Capabilities | tools, resources, prompts | | Tools | 94 | | Resources | 80 | | Prompts | 14 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,816 ms over 1 attempt | ### Tools listed 94 tools; the first 40 names are recorded - execute\_plan - claim\_free\_key - search - fetch - search\_facilities - get\_facility - get\_market\_intel - get\_market\_dcpi\_rank - predict\_market\_trajectory - get\_gas\_index - get\_gas\_economics - get\_grid\_scoreboard - compare\_isos - get\_intelligence\_index - list\_transactions - get\_news - semantic\_search - search\_intelligence - get\_market\_context - get\_iso\_context - get\_pipeline - get\_power\_pipeline - get\_infra\_projects - get\_power\_availability\_timeline - get\_global\_power - get\_interconnection\_queue - get\_refined\_queue - get\_retirement\_headroom - get\_hosting\_capacity - analyze\_parcel - rank\_sites - discover\_tools - plan\_query - save\_to\_shortlist - get\_shortlist - set\_shortlist\_alert - suggest\_reallocation - get\_grid\_data - get\_changes - get\_facility\_risk\_delta ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:10Z https://dchub.cloud/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2827 ms - 20:02:40Z https://dchub.cloud/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2816 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://dchub.cloud/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DC Hub. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: cloud.dchub/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dchub-cloud/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=dchub), read 4 November 2026 - [DC Hub website](https://dchub.cloud), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Deci MCP server | Agent MCP Directory" description: "Does Deci have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/deci-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Deci MCP server | Agent MCP Directory > Does Deci have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/deci-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Deci: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Deci (deci.ai), so the connector had nothing to connect to. Ora's cached score for deci.ai is 44, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Deci (registry title: deci.ai) | | --- | --- | | Domain | deci.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 44, grade D; Ora scanned the domain on 28 June 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for deci.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Deci. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for deci.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Deci. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deci-ai/index.md) ## Sources - [Ora score page for deci.ai](https://ora.ai/score/deci.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 June 2026, read from GET /api/leaderboard) - [Where Deci was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Deci website](https://deci.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dedalus Labs MCP server | Agent MCP Directory" description: "Dedalus Labs has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/dedaluslabs-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dedalus Labs MCP server | Agent MCP Directory > Dedalus Labs has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/dedaluslabs-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dedalus Labs: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Dedalus Labs; the connector tried mcp.dedaluslabs.ai as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 503, GET HTTP 503 text/html). ## Fact sheet | Company | Dedalus Labs (registry title: dedaluslabs.ai) | | --- | --- | | Domain | dedaluslabs.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 85, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dedaluslabs.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dedaluslabs.ai/mcp | | --- | --- | | How it was found | mcp.dedaluslabs.ai was tried as a guess and did not answer | | HTTP status | 503 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,033 ms over 2 attempts | | Result | no MCP answer (POST HTTP 503, GET HTTP 503 text/html) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:09Z https://mcp.dedaluslabs.ai/mcp sent initialize result no-answer (HTTP 503) 956 ms - 20:02:39Z https://mcp.dedaluslabs.ai/mcp sent initialize result no-answer (HTTP 503) 1033 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.dedaluslabs.ai/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 503, GET HTTP 503 text/html). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dedalus Labs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dedaluslabs-ai/index.md) ## Sources - [Ora score page for dedaluslabs.ai](https://ora.ai/score/dedaluslabs.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Dedalus Labs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Dedalus Labs website](https://dedaluslabs.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Deed MCP server | Agent MCP Directory" description: "Deed has an open MCP server with 28 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/deed-page site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Deed MCP server | Agent MCP Directory > Deed has an open MCP server with 28 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/deed-page Site: Agent MCP Directory Last reviewed: 2026-11-05 # Deed: MCP server, CLI and agent surfaces Yes: Deed runs a public MCP server at deed.page that listed 28 tools to a client with no credentials on 4 November 2026. Examples: publish\_site, update\_site, get\_site. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Deed (registry title: deed.page) | | --- | --- | | Domain | deed.page | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for deed.page when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://deed.page/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | deed.page 1.19.0 | | Capabilities | tools | | Tools | 28 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 616 ms over 1 attempt | ### Tools listed 28 tools - publish\_site - update\_site - get\_site - list\_sites - delete\_site - rotate\_token - revoke\_token - agent\_seats - whoami - get\_upgrade\_link - claim\_share\_credit - list\_versions - restore\_version - add\_domain - list\_domains - remove\_domain - domain\_status - plan\_upload - finalize\_upload - get\_manifest - site\_analytics - site\_visits - set\_site\_access - set\_listing - set\_badge - create\_webhook - list\_webhooks - delete\_webhook ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:08Z https://deed.page/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 623 ms - 20:02:38Z https://deed.page/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 616 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://deed.page/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Deed. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: deed.page (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deed-page/index.md) ## Sources - [Deed website](https://deed.page), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Deepnote MCP server | Agent MCP Directory" description: "Does Deepnote have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/deepnote-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Deepnote MCP server | Agent MCP Directory > Does Deepnote have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/deepnote-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Deepnote: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Deepnote (deepnote.com), so the connector had nothing to connect to. Ora's cached score for deepnote.com is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Deepnote (registry title: deepnote.com) | | --- | --- | | Domain | deepnote.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 16 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for deepnote.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Deepnote. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for deepnote.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Deepnote. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deepnote-com/index.md) ## Sources - [Ora score page for deepnote.com](https://ora.ai/score/deepnote.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 September 2026, read from GET /api/leaderboard) - [Where Deepnote was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Deepnote website](https://deepnote.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DeepSource MCP server | Agent MCP Directory" description: "DeepSource: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/deepsource-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DeepSource MCP server | Agent MCP Directory > DeepSource: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/deepsource-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DeepSource: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for DeepSource; the connector's guess at mcp.deepsource.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | DeepSource (registry title: deepsource.com) | | --- | --- | | Domain | deepsource.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 68, grade C; Ora scanned the domain on 6 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for deepsource.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.deepsource.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 990 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:09Z https://mcp.deepsource.com/mcp sent initialize result auth-required (HTTP 401) 996 ms - 20:02:39Z https://mcp.deepsource.com/mcp sent initialize result auth-required (HTTP 401) 990 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="deepsource-mcp" | | Protected resource metadata | mcp.deepsource.com | | Authorization server metadata | mcp.deepsource.com | | Registration endpoint | https://app.deepsource.com/mcp/o/register/ | ### The sign-in route, step by step 1. Request `https://mcp.deepsource.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.deepsource.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.deepsource.com/mcp/o/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DeepSource. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deepsource-com/index.md) ## Sources - [Ora score page for deepsource.com](https://ora.ai/score/deepsource.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 September 2026, read from GET /api/leaderboard) - [Where DeepSource was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [DeepSource website](https://deepsource.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DeepWiki MCP server | Agent MCP Directory" description: "DeepWiki has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/deepwiki-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DeepWiki MCP server | Agent MCP Directory > DeepWiki has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/deepwiki-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DeepWiki: MCP server, CLI and agent surfaces Yes: DeepWiki runs a public MCP server at mcp.deepwiki.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: ask\_wiki\_question, read\_wiki\_contents, read\_wiki\_structure. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | DeepWiki | | --- | --- | | Domain | deepwiki.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for deepwiki.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.deepwiki.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | DeepWiki 4.0.2 | | Capabilities | logging, prompts, resources, tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,035 ms over 1 attempt | ### Tools listed 3 tools - ask\_wiki\_question - read\_wiki\_contents - read\_wiki\_structure ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:57:10Z https://mcp.deepwiki.com/sse sent initialize result no-answer (HTTP 410) 1379 ms - 20:02:40Z https://mcp.deepwiki.com/sse sent initialize result no-answer (HTTP 410) 1600 ms - 20:02:42Z https://mcp.deepwiki.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2035 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.deepwiki.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DeepWiki. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deepwiki-com/index.md) ## Sources - [Where DeepWiki was found](https://github.com/mcp/CognitionAI/deepwiki), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Deno MCP server | Agent MCP Directory" description: "Does Deno have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/deno-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Deno MCP server | Agent MCP Directory > Does Deno have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/deno-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Deno: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Deno (deno.com), so the connector had nothing to connect to. A CLI is on record: deno on npm. Ora's cached score for deno.com is 65, grade C, read on 5 November 2026. ## Fact sheet | Company | Deno | | --- | --- | | Domain | deno.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for deno.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Deno. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for deno.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | deno on npm (page) | | --- | --- | | Exists | yes | | Latest version | 2.9.6 | | Last publish | 27 August 2026 | | Command names | deno | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deno-com/index.md) ## Sources - [Ora score page for deno.com](https://ora.ai/score/deno.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Deno was found](https://docs.deno.com/runtime/), read 4 November 2026 - [Deno website](https://deno.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rocketship MCP server | Agent MCP Directory" description: "Rocketship: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/deployrocketship-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rocketship MCP server | Agent MCP Directory > Rocketship: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/deployrocketship-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rocketship: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rocketship at deployrocketship.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Rocketship | | --- | --- | | Domain | deployrocketship.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for deployrocketship.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://deployrocketship.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 924 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:10Z https://deployrocketship.com/mcp sent initialize result auth-required (HTTP 401) 1044 ms - 20:02:40Z https://deployrocketship.com/mcp sent initialize result auth-required (HTTP 401) 924 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://deployrocketship.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | deployrocketship.com | | Authorization server metadata | deployrocketship.com | | Registration endpoint | https://deployrocketship.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://deployrocketship.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://deployrocketship.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://deployrocketship.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rocketship. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.deployrocketship/rocketship | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deployrocketship-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=deployrocketship), read 4 November 2026 - [Rocketship website](https://deployrocketship.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Depot MCP server | Agent MCP Directory" description: "Depot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/depot-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Depot MCP server | Agent MCP Directory > Depot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/depot-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Depot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Depot; the connector's guess at mcp.depot.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Depot | | --- | --- | | Domain | depot.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for depot.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.depot.dev/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,845 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:12Z https://mcp.depot.dev/mcp sent initialize result auth-required (HTTP 401) 3025 ms - 20:02:41Z https://mcp.depot.dev/mcp sent initialize result auth-required (HTTP 401) 1845 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authorization needed", resource_metadata="https://mcp.depot.dev/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.depot.dev | | Authorization server metadata | signin.depot.dev | | Registration endpoint | https://signin.depot.dev/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.depot.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.depot.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://signin.depot.dev/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Depot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/depot-dev/index.md) ## Sources - [Ora score page for depot.dev](https://ora.ai/score/depot.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Depot was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Depot website](https://depot.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Designbase MCP server | Agent MCP Directory" description: "Does Designbase have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/designbase-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Designbase MCP server | Agent MCP Directory > Does Designbase have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/designbase-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Designbase: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Designbase (designbase.com), so the connector had nothing to connect to. Ora's cached score for designbase.com is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Designbase (registry title: designbase.com) | | --- | --- | | Domain | designbase.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for designbase.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Designbase. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for designbase.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Designbase. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/designbase-com/index.md) ## Sources - [Ora score page for designbase.com](https://ora.ai/score/designbase.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Designbase was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Designbase website](https://designbase.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Designesy MCP server | Agent MCP Directory" description: "Designesy has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/designesy-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Designesy MCP server | Agent MCP Directory > Designesy has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/designesy-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Designesy: MCP server, CLI and agent surfaces Yes: Designesy runs a public MCP server at www.designesy.org that listed 17 tools to a client with no credentials on 4 November 2026. Examples: designesy\_catalog, designesy\_contract, designesy\_design\_review. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Designesy | | --- | --- | | Domain | designesy.org | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for designesy.org when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.designesy.org/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | designesy 1.13.10 | | Capabilities | tools, resources | | Tools | 17 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,565 ms over 1 attempt | ### Tools listed 17 tools - designesy\_catalog - designesy\_contract - designesy\_design\_review - designesy\_skill\_md - designesy\_agent\_json - designesy\_llms\_txt - designesy\_llms\_full\_txt - designesy\_score - designesy\_tokens\_score - designesy\_a11y\_score - designesy\_motion\_score - designesy\_drift\_score - designesy\_readiness\_score - designesy\_guardrails - designesy\_monitor\_score - designesy\_compare - designesy\_report ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:13Z https://www.designesy.org/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 3185 ms - 20:02:41Z https://www.designesy.org/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1565 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.designesy.org/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Designesy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/designesy-org/index.md) ## Sources - [Where Designesy was found](https://github.com/mcp/LE-VAI/designesy-org), read 4 November 2026 - [Designesy website](https://designesy.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DeskCrew MCP server | Agent MCP Directory" description: "Does DeskCrew have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/deskcrew-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DeskCrew MCP server | Agent MCP Directory > Does DeskCrew have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/deskcrew-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # DeskCrew: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for DeskCrew (deskcrew.io), so the connector had nothing to connect to. An OpenAPI file is published. The company was added from the GitHub MCP Registry. A company can be added by submitting an endpoint. ## Fact sheet | Company | DeskCrew | | --- | --- | | Domain | deskcrew.io | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | None found | | Ora score | none: Ora returned no cached score for deskcrew.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for DeskCrew. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for deskcrew.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (io.deskcrew/support) | | GitHub MCP Registry | Listed | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for DeskCrew. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: deskcrew.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.deskcrew/support | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/deskcrew-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=deskcrew), read 4 November 2026 - [DeskCrew website](https://deskcrew.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Desktopcommander MCP server | Agent MCP Directory" description: "Desktopcommander: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/desktopcommander-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Desktopcommander MCP server | Agent MCP Directory > Desktopcommander: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/desktopcommander-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Desktopcommander: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Desktopcommander at mcp.desktopcommander.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Desktopcommander (registry title: Remote Desktop Commander) | | --- | --- | | Domain | desktopcommander.app | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for desktopcommander.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.desktopcommander.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 502 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:10Z https://mcp.desktopcommander.app/mcp sent initialize result auth-required (HTTP 401) 347 ms - 20:02:40Z https://mcp.desktopcommander.app/mcp sent initialize result auth-required (HTTP 401) 502 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.desktopcommander.app/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.desktopcommander.app | | Authorization server metadata | mcp.desktopcommander.app | | Registration endpoint | https://mcp.desktopcommander.app/register | ### The sign-in route, step by step 1. Request `https://mcp.desktopcommander.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.desktopcommander.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.desktopcommander.app/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Desktopcommander. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.desktopcommander/remote-desktop-commander | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/desktopcommander-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=desktopcommander), read 4 November 2026 - [Desktopcommander website](https://desktopcommander.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DevCycle MCP server | Agent MCP Directory" description: "DevCycle: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/devcycle-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DevCycle MCP server | Agent MCP Directory > DevCycle: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/devcycle-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DevCycle: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for DevCycle at mcp.devcycle.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | DevCycle (registry title: devcycle.com) | | --- | --- | | Domain | devcycle.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 76, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for devcycle.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.devcycle.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 224 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:10Z https://mcp.devcycle.com/mcp sent initialize result auth-required (HTTP 401) 143 ms - 20:02:40Z https://mcp.devcycle.com/mcp sent initialize result auth-required (HTTP 401) 224 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.devcycle.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.devcycle.com | | Authorization server metadata | mcp.devcycle.com | | Registration endpoint | https://mcp.devcycle.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.devcycle.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.devcycle.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.devcycle.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DevCycle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.devcycle/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/devcycle-com/index.md) ## Sources - [Ora score page for devcycle.com](https://ora.ai/score/devcycle.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where DevCycle was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.devcycle%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=devcycle), read 4 November 2026 - [DevCycle website](https://devcycle.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Devin MCP server | Agent MCP Directory" description: "Devin has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/devin-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Devin MCP server | Agent MCP Directory > Devin has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/devin-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Devin: MCP server, CLI and agent surfaces Yes: Devin runs a public MCP server at mcp.deepwiki.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: ask\_wiki\_question, read\_wiki\_contents, read\_wiki\_structure. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for devin.ai is 67, grade C, read on 5 November 2026. ## Fact sheet | Company | Devin | | --- | --- | | Domain | devin.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 67, grade C; Ora scanned the domain on 16 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for devin.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.deepwiki.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | DeepWiki 4.0.2 | | Capabilities | logging, prompts, resources, tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,587 ms over 1 attempt | ### Tools listed 3 tools - ask\_wiki\_question - read\_wiki\_contents - read\_wiki\_structure ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:57:11Z https://mcp.deepwiki.com/sse sent initialize result no-answer (HTTP 410) 437 ms - 20:02:41Z https://mcp.deepwiki.com/sse sent initialize result no-answer (HTTP 410) 916 ms - 20:02:42Z https://mcp.deepwiki.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1587 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.deepwiki.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Devin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: devin.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/devin-ai/index.md) ## Sources - [Ora score page for devin.ai](https://ora.ai/score/devin.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 September 2026, read from GET /api/score) - [Where Devin was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Devin website](https://devin.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Devo MCP server | Agent MCP Directory" description: "Does Devo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/devo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Devo MCP server | Agent MCP Directory > Does Devo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/devo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Devo: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Devo (devo.com), so the connector had nothing to connect to. Ora's cached score for devo.com is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Devo (registry title: devo.com) | | --- | --- | | Domain | devo.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for devo.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Devo. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for devo.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Devo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/devo-com/index.md) ## Sources - [Ora score page for devo.com](https://ora.ai/score/devo.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Devo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Devo website](https://devo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Devtron MCP server | Agent MCP Directory" description: "Devtron: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/devtron-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Devtron MCP server | Agent MCP Directory > Devtron: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/devtron-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Devtron: MCP server, CLI and agent surfaces Not counted. No source names an endpoint for Devtron; the connector's guess at mcp.devtron.ai asked for credentials on 4 November 2026 and published no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Devtron (registry title: devtron.ai) | | --- | --- | | Domain | devtron.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 48, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for devtron.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.devtron.ai/mcp | | --- | --- | | How it was found | mcp.devtron.ai was tried as a guess and answered; see the result below | | Transport | streamable-http | | HTTP status | 403 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,476 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:12Z https://mcp.devtron.ai/mcp sent initialize result auth-required-no-oauth (HTTP 403) 1333 ms - 20:02:42Z https://mcp.devtron.ai/mcp sent initialize result auth-required-no-oauth (HTTP 403) 1476 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.devtron.ai/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Devtron. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/devtron-ai/index.md) ## Sources - [Ora score page for devtron.ai](https://ora.ai/score/devtron.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Devtron was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Devtron website](https://devtron.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DevZero MCP server | Agent MCP Directory" description: "Does DevZero have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/devzero-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DevZero MCP server | Agent MCP Directory > Does DevZero have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/devzero-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # DevZero: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for DevZero (devzero.io), so the connector had nothing to connect to. Ora's cached score for devzero.io is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | DevZero (registry title: devzero.io) | | --- | --- | | Domain | devzero.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 11 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for devzero.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for DevZero. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for devzero.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for DevZero. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/devzero-io/index.md) ## Sources - [Ora score page for devzero.io](https://ora.ai/score/devzero.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 September 2026, read from GET /api/leaderboard) - [Where DevZero was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [DevZero website](https://devzero.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DialMCP MCP server | Agent MCP Directory" description: "DialMCP: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/dialmcp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DialMCP MCP server | Agent MCP Directory > DialMCP: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/dialmcp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DialMCP: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for DialMCP at mcp.dialmcp.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | DialMCP | | --- | --- | | Domain | dialmcp.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for dialmcp.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dialmcp.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 161 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:11Z https://mcp.dialmcp.com/mcp sent initialize result auth-required (HTTP 401) 520 ms - 20:02:41Z https://mcp.dialmcp.com/mcp sent initialize result auth-required (HTTP 401) 161 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token", resource_metadata="https://mcp.dialmcp.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.dialmcp.com | | Authorization server metadata | mcp.dialmcp.com | | Registration endpoint | https://mcp.dialmcp.com/register | ### The sign-in route, step by step 1. Request `https://mcp.dialmcp.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.dialmcp.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.dialmcp.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DialMCP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.dialmcp/dialmcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dialmcp-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=dialmcp), read 4 November 2026 - [DialMCP website](https://dialmcp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Didit One MCP server | Agent MCP Directory" description: "Didit One: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/didit-me site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Didit One MCP server | Agent MCP Directory > Didit One: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/didit-me Site: Agent MCP Directory Last reviewed: 2026-11-05 # Didit One: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Didit One; the connector's guess at mcp.didit.me answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Didit One (registry title: didit.me) | | --- | --- | | Domain | didit.me | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 83, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for didit.me, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.didit.me/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 622 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:12Z https://mcp.didit.me/mcp sent initialize result auth-required (HTTP 401) 797 ms - 20:02:42Z https://mcp.didit.me/mcp sent initialize result auth-required (HTTP 401) 622 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.didit.me/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.didit.me | | Authorization server metadata | business.didit.me | | Registration endpoint | https://business.didit.me/api/auth/oauth-register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.didit.me/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.didit.me/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://business.didit.me/api/auth/oauth-register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Didit One. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/didit-me/index.md) ## Sources - [Ora score page for didit.me](https://ora.ai/score/didit.me?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Didit One was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Didit One website](https://didit.me), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Digestseo MCP server | Agent MCP Directory" description: "Digestseo has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/digestseo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Digestseo MCP server | Agent MCP Directory > Digestseo has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/digestseo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Digestseo: MCP server, CLI and agent surfaces Yes: Digestseo runs a public MCP server at web-validator-mcp.digestseo.com that listed 8 tools to a client with no credentials on 4 November 2026. Examples: validate\_html, validate\_css, audit\_seo\_metadata. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Digestseo (registry title: Web Validator by DigestSEO) | | --- | --- | | Domain | digestseo.com | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for digestseo.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://web-validator-mcp.digestseo.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | web-validator-by-digestseo 0.5.0 | | Capabilities | resources, tools | | Tools | 8 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 246 ms over 1 attempt | ### Tools listed 8 tools - validate\_html - validate\_css - audit\_seo\_metadata - validate\_schema\_markup - check\_broken\_links - generate\_validation\_report - audit\_public\_webpage - audit\_public\_site ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:12Z https://web-validator-mcp.digestseo.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 874 ms - 20:02:42Z https://web-validator-mcp.digestseo.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 246 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://web-validator-mcp.digestseo.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Digestseo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.github.AKzar1el/mcp-web-validator | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/digestseo-com/index.md) ## Sources - [Where Digestseo was found](https://github.com/mcp/AKzar1el/mcp-web-validator), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=digestseo), read 4 November 2026 - [Digestseo website](https://digestseo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DigitalOcean MCP server | Agent MCP Directory" description: "DigitalOcean: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/digitalocean-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DigitalOcean MCP server | Agent MCP Directory > DigitalOcean: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/digitalocean-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DigitalOcean: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for DigitalOcean; the connector's guess at mcp.digitalocean.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | DigitalOcean | | --- | --- | | Domain | digitalocean.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 607 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for digitalocean.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.digitalocean.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,238 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://mcp.digitalocean.com/mcp sent initialize result auth-required (HTTP 401) 844 ms - 20:01:31Z https://mcp.digitalocean.com/mcp sent initialize result auth-required (HTTP 401) 1238 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.digitalocean.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.digitalocean.com | | Authorization server metadata | cloud.digitalocean.com | | Registration endpoint | https://cloud.digitalocean.com/v1/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.digitalocean.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.digitalocean.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://cloud.digitalocean.com/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DigitalOcean. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/digitalocean-com/index.md) ## Sources - [Ora score page for digitalocean.com](https://ora.ai/score/digitalocean.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where DigitalOcean was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [DigitalOcean website](https://digitalocean.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Directus MCP server | Agent MCP Directory" description: "Does Directus have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/directus-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Directus MCP server | Agent MCP Directory > Does Directus have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/directus-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Directus: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Directus (directus.io), so the connector had nothing to connect to. Ora's cached score for directus.io is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Directus (registry title: directus.io) | | --- | --- | | Domain | directus.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 17 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for directus.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Directus. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for directus.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Directus. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/directus-io/index.md) ## Sources - [Ora score page for directus.io](https://ora.ai/score/directus.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 August 2026, read from GET /api/leaderboard) - [Where Directus was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Directus website](https://directus.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dittowords MCP server | Agent MCP Directory" description: "Does Dittowords have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dittowords-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dittowords MCP server | Agent MCP Directory > Does Dittowords have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/dittowords-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dittowords: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Dittowords (dittowords.com), so the connector had nothing to connect to. Ora's cached score for dittowords.com is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Dittowords (registry title: dittowords.com) | | --- | --- | | Domain | dittowords.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 4 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dittowords.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Dittowords. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for dittowords.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Dittowords. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dittowords-com/index.md) ## Sources - [Ora score page for dittowords.com](https://ora.ai/score/dittowords.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 October 2026, read from GET /api/leaderboard) - [Where Dittowords was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Dittowords website](https://dittowords.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Divblox MCP server | Agent MCP Directory" description: "Divblox: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/divblox-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Divblox MCP server | Agent MCP Directory > Divblox: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/divblox-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Divblox: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Divblox at mcp.divblox.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Divblox (registry title: Divblox MCP) | | --- | --- | | Domain | divblox.app | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for divblox.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.divblox.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,662 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:14Z https://mcp.divblox.app/mcp sent initialize result auth-required (HTTP 401) 2300 ms - 20:02:43Z https://mcp.divblox.app/mcp sent initialize result auth-required (HTTP 401) 1662 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.divblox.app/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.divblox.app | | Authorization server metadata | mcp.divblox.app | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.divblox.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.divblox.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Divblox. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/divblox-app/index.md) ## Sources - [Where Divblox was found](https://github.com/mcp/divblox-group/divblox-mcp), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dm MCP server | Agent MCP Directory" description: "Dm has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dm-de site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dm MCP server | Agent MCP Directory > Dm has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dm-de Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dm: MCP server, CLI and agent surfaces Yes: Dm runs a public MCP server at mcp.dm.de that listed 5 tools to a client with no credentials on 4 November 2026. Examples: searchProducts, getStoreAvailability, findNearbyStores. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for dm.de is 51, grade C, read on 5 November 2026. ## Fact sheet | Company | Dm (registry title: dm.de) | | --- | --- | | Domain | dm.de | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 6,351 on the list of 4 November 2026 | | Ora score | 51, grade C; Ora scanned the domain on 13 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for dm.de, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dm.de/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | dm-drogeriemarkt 3.4.11 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 5 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 820 ms over 1 attempt | ### Tools listed 5 tools - searchProducts - getStoreAvailability - findNearbyStores - getProductDetails - renderProductTiles ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:11Z https://mcp.dm.de/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 998 ms - 20:01:49Z https://mcp.dm.de/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 820 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.dm.de/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: de.dm.mcp/dm-drogerie-markt | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dm-de/index.md) ## Sources - [Ora score page for dm.de](https://ora.ai/score/dm.de?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 13 October 2026, read from GET /api/score) - [Where Dm was found](https://registry.modelcontextprotocol.io/v0/servers?search=de.dm.mcp%2Fdm-drogerie-markt), read 4 November 2026 - [Dm website](https://dm.de), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DMCA.com MCP server | Agent MCP Directory" description: "DMCA.com has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dmca-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DMCA.com MCP server | Agent MCP Directory > DMCA.com has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dmca-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DMCA.com: MCP server, CLI and agent surfaces Yes: DMCA.com runs a public MCP server at mcp.dmca.com that listed 10 tools to a client with no credentials on 4 November 2026. Examples: createCase, createComplianceCase, createDIYCase. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | DMCA.com (registry title: DMCA.com Cases) | | --- | --- | | Domain | dmca.com | | Category | Security (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 4,102 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for dmca.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dmca.com/runtime/webhooks/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | dmca-cases 1.2.1 | | Capabilities | logging, tools | | Tools | 10 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,339 ms over 1 attempt | ### Tools listed 10 tools - createCase - createComplianceCase - createDIYCase - getCaseById - getSiteReport - listCases - listComplianceCases - listDIYCases - login - updateCase ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:05Z https://mcp.dmca.com/runtime/webhooks/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1442 ms - 20:01:41Z https://mcp.dmca.com/runtime/webhooks/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1339 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.dmca.com/runtime/webhooks/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DMCA.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.dmca/dmca-cases | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dmca-com/index.md) ## Sources - [Where DMCA.com was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.dmca%2Fdmca-cases), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=dmca), read 4 November 2026 - [DMCA.com website](https://dmca.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Docker MCP server | Agent MCP Directory" description: "Docker has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/docker-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Docker MCP server | Agent MCP Directory > Docker has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/docker-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Docker: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Docker; the connector tried mcp.docker.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). ## Fact sheet | Company | Docker | | --- | --- | | Domain | docker.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Tranco rank | 537 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for docker.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.docker.com/mcp | | --- | --- | | How it was found | mcp.docker.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 920 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 no content-type) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://mcp.docker.com/mcp sent initialize result no-answer (HTTP 404) 945 ms - 20:01:30Z https://mcp.docker.com/mcp sent initialize result no-answer (HTTP 404) 920 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.docker.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Docker. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/docker-com/index.md) ## Sources - [Ora score page for docker.com](https://ora.ai/score/docker.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/score) - [Where Docker was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Docker website](https://docker.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Docket MCP server | Agent MCP Directory" description: "Does Docket have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/docketqa-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Docket MCP server | Agent MCP Directory > Does Docket have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/docketqa-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Docket: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Docket (docketqa.com), so the connector had nothing to connect to. Ora's cached score for docketqa.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Docket (registry title: docketqa.com) | | --- | --- | | Domain | docketqa.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for docketqa.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Docket. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for docketqa.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Docket. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/docketqa-com/index.md) ## Sources - [Ora score page for docketqa.com](https://ora.ai/score/docketqa.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/leaderboard) - [Where Docket was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Docket website](https://docketqa.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DocNexus MCP server | Agent MCP Directory" description: "DocNexus: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/docnexus-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DocNexus MCP server | Agent MCP Directory > DocNexus: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/docnexus-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # DocNexus: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for DocNexus at mcp.docnexus.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | DocNexus | | --- | --- | | Domain | docnexus.ai | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for docnexus.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.docnexus.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,734 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:14Z https://mcp.docnexus.ai/mcp sent initialize result auth-required (HTTP 401) 1129 ms - 20:02:44Z https://mcp.docnexus.ai/mcp sent initialize result auth-required (HTTP 401) 1734 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.docnexus.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.docnexus.ai | | Authorization server metadata | mcp.docnexus.ai | | Registration endpoint | https://mcp.docnexus.ai/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.docnexus.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.docnexus.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.docnexus.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DocNexus. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.docnexus.mcp/docnexus | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/docnexus-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=docnexus), read 4 November 2026 - [DocNexus website](https://docnexus.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DocSpring MCP server | Agent MCP Directory" description: "DocSpring: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/docspring-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DocSpring MCP server | Agent MCP Directory > DocSpring: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/docspring-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DocSpring: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for DocSpring at mcp.docspring.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | DocSpring | | --- | --- | | Domain | docspring.com | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for docspring.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.docspring.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,699 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:14Z https://mcp.docspring.com/mcp sent initialize result auth-required (HTTP 401) 1695 ms - 20:02:44Z https://mcp.docspring.com/mcp sent initialize result auth-required (HTTP 401) 1699 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.docspring.com/.well-known/oauth-protected-resource/mcp", scope="read write delete integrations" | | Protected resource metadata | mcp.docspring.com | | Authorization server metadata | app.docspring.com | | Registration endpoint | https://app.docspring.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.docspring.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.docspring.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.docspring.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DocSpring. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.docspring/mcp, com.docspring/mcp-eu | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/docspring-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=docspring), read 4 November 2026 - [DocSpring website](https://docspring.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dodo Payments MCP server | Agent MCP Directory" description: "Dodo Payments: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/dodopayments-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dodo Payments MCP server | Agent MCP Directory > Dodo Payments: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/dodopayments-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dodo Payments: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Dodo Payments at mcp.dodopayments.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Dodo Payments | | --- | --- | | Domain | dodopayments.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 84, grade B; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for dodopayments.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dodopayments.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 569 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:57:13Z https://mcp.dodopayments.com/sse sent initialize result no-answer (HTTP 404) 154 ms - 20:02:42Z https://mcp.dodopayments.com/sse sent initialize result no-answer (HTTP 404) 141 ms - 20:02:43Z https://mcp.dodopayments.com/mcp sent initialize result auth-required (HTTP 401) 569 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.dodopayments.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.dodopayments.com | | Authorization server metadata | auth.dodopayments.com | | Registration endpoint | https://auth.dodopayments.com/oauth2/register | | Client ID metadata documents | supported | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.dodopayments.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.dodopayments.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.dodopayments.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dodo Payments. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dodopayments-com/index.md) ## Sources - [Ora score page for dodopayments.com](https://ora.ai/score/dodopayments.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/score) - [Where Dodo Payments was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Dodo Payments website](https://dodopayments.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dojah MCP server | Agent MCP Directory" description: "Does Dojah have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dojah-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dojah MCP server | Agent MCP Directory > Does Dojah have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/dojah-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dojah: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Dojah (dojah.io), so the connector had nothing to connect to. Ora's cached score for dojah.io is 77, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Dojah (registry title: dojah.io) | | --- | --- | | Domain | dojah.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dojah.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Dojah. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for dojah.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Dojah. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dojah-io/index.md) ## Sources - [Ora score page for dojah.io](https://ora.ai/score/dojah.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Dojah was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Dojah website](https://dojah.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dorik MCP server | Agent MCP Directory" description: "Does Dorik have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dorik-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dorik MCP server | Agent MCP Directory > Does Dorik have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/dorik-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dorik: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Dorik (dorik.com), so the connector had nothing to connect to. Ora's cached score for dorik.com is 35, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Dorik (registry title: dorik.com) | | --- | --- | | Domain | dorik.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 35, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dorik.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Dorik. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for dorik.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Dorik. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dorik-com/index.md) ## Sources - [Ora score page for dorik.com](https://ora.ai/score/dorik.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Dorik was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Dorik website](https://dorik.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Double MCP server | Agent MCP Directory" description: "Does Double have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/double-bot site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Double MCP server | Agent MCP Directory > Does Double have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/double-bot Site: Agent MCP Directory Last reviewed: 2026-11-05 # Double: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Double (double.bot), so the connector had nothing to connect to. Ora's cached score for double.bot is 54, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Double (registry title: double.bot) | | --- | --- | | Domain | double.bot | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 54, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for double.bot, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Double. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for double.bot, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Double. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/double-bot/index.md) ## Sources - [Ora score page for double.bot](https://ora.ai/score/double.bot?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where Double was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Double website](https://double.bot), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Draftbit MCP server | Agent MCP Directory" description: "Draftbit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/draftbit-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Draftbit MCP server | Agent MCP Directory > Draftbit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/draftbit-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Draftbit: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Draftbit; the connector's guess at mcp.draftbit.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Draftbit (registry title: draftbit.com) | | --- | --- | | Domain | draftbit.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 61, grade C; Ora scanned the domain on 26 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for draftbit.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.draftbit.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,151 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:15Z https://mcp.draftbit.com/mcp sent initialize result auth-required (HTTP 401) 1389 ms - 20:02:44Z https://mcp.draftbit.com/mcp sent initialize result auth-required (HTTP 401) 1151 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.draftbit.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.draftbit.com | | Authorization server metadata | clerk.draftbit.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.draftbit.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.draftbit.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Draftbit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/draftbit-com/index.md) ## Sources - [Ora score page for draftbit.com](https://ora.ai/score/draftbit.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 September 2026, read from GET /api/leaderboard) - [Where Draftbit was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Draftbit website](https://draftbit.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dragoneye MCP server | Agent MCP Directory" description: "Dragoneye: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/dragoneye-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dragoneye MCP server | Agent MCP Directory > Dragoneye: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/dragoneye-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dragoneye: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Dragoneye at nexus.api.dragoneye.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Dragoneye (registry title: dragoneye.ai) | | --- | --- | | Domain | dragoneye.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for dragoneye.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://nexus.api.dragoneye.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,278 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:16Z https://nexus.api.dragoneye.ai/mcp sent initialize result auth-required (HTTP 401) 2621 ms - 20:02:46Z https://nexus.api.dragoneye.ai/mcp sent initialize result auth-required (HTTP 401) 2278 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://nexus.api.dragoneye.ai/.well-known/oauth-protected-resource/mcp/" | | Protected resource metadata | nexus.api.dragoneye.ai | | Authorization server metadata | auth.dragoneye.ai | | Registration endpoint | https://auth.dragoneye.ai/oauth/2.1/register | ### The sign-in route, step by step 1. Request `https://nexus.api.dragoneye.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://nexus.api.dragoneye.ai/.well-known/oauth-protected-resource/mcp/` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.dragoneye.ai/oauth/2.1/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dragoneye. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.dragoneye/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dragoneye-ai/index.md) ## Sources - [Ora score page for dragoneye.ai](https://ora.ai/score/dragoneye.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Dragoneye was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.dragoneye%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=dragoneye), read 4 November 2026 - [Dragoneye website](https://dragoneye.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Draw MCP server | Agent MCP Directory" description: "Draw has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/draw-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Draw MCP server | Agent MCP Directory > Draw has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/draw-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Draw: MCP server, CLI and agent surfaces Yes: Draw runs a public MCP server at mcp.draw.io that listed 3 tools to a client with no credentials on 4 November 2026. Examples: create\_diagram, search\_shapes, get\_drawio\_reference. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for draw.io is 13, grade F, read on 5 November 2026. ## Fact sheet | Company | Draw (registry title: draw.io) | | --- | --- | | Domain | draw.io | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 13, grade F; Ora scanned the domain on 16 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for draw.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.draw.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | drawio-mcp-app 1.5.0 | | Capabilities | tools, resources | | Tools | 3 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 300 ms over 1 attempt | ### Tools listed 3 tools - create\_diagram - search\_shapes - get\_drawio\_reference ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:14Z https://mcp.draw.io/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 231 ms - 20:02:44Z https://mcp.draw.io/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 300 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.draw.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Draw. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.draw/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/draw-io/index.md) ## Sources - [Ora score page for draw.io](https://ora.ai/score/draw.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=draw), read 4 November 2026 - [Draw website](https://draw.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DrDroid MCP server | Agent MCP Directory" description: "Does DrDroid have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/drdroid-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DrDroid MCP server | Agent MCP Directory > Does DrDroid have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/drdroid-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # DrDroid: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for DrDroid (drdroid.io), so the connector had nothing to connect to. Ora's cached score for drdroid.io is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | DrDroid (registry title: drdroid.io) | | --- | --- | | Domain | drdroid.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for drdroid.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for DrDroid. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for drdroid.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for DrDroid. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/drdroid-io/index.md) ## Sources - [Ora score page for drdroid.io](https://ora.ai/score/drdroid.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/leaderboard) - [Where DrDroid was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [DrDroid website](https://drdroid.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dreamwork MCP server | Agent MCP Directory" description: "Dreamwork has an open MCP server with 74 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dreamworkhq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dreamwork MCP server | Agent MCP Directory > Dreamwork has an open MCP server with 74 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dreamworkhq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dreamwork: MCP server, CLI and agent surfaces Yes: Dreamwork runs a public MCP server at mcp.dreamworkhq.com that listed 74 tools to a client with no credentials on 4 November 2026. Examples: list\_matches, get\_job, save\_job. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Dreamwork | | --- | --- | | Domain | dreamworkhq.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for dreamworkhq.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.dreamworkhq.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | dreamwork 1.9.2 | | Capabilities | tools, prompts | | Tools | 74 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,534 ms over 1 attempt | ### Tools listed 74 tools; the first 40 names are recorded - list\_matches - get\_job - save\_job - dismiss\_match - restore\_match - list\_dismissed\_matches - get\_pipeline - move\_pipeline - mark\_applied\_offsite - import\_job - cancel\_apply - get\_application\_questions - answer\_application\_questions - dismiss\_application\_questions - generate\_pack - prepare\_applications - get\_pack\_status - edit\_cover\_letter - edit\_resume - format\_resume - edit\_answer - strengthen\_application - restore\_material - get\_application\_documents - replace\_application\_document - get\_preferences - update\_preferences - get\_application\_readiness - save\_application\_answers - parse\_preferences\_text - get\_career\_record - remember\_hypothesis - confirm\_hypothesis - forget\_hypothesis - get\_resume\_download\_link - get\_resume\_work\_history - get\_communication\_preferences - update\_communication\_preferences - get\_autopilot\_settings - update\_autopilot\_settings ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:16Z https://mcp.dreamworkhq.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1950 ms - 20:02:46Z https://mcp.dreamworkhq.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1534 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.dreamworkhq.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dreamwork. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dreamworkhq-com/index.md) ## Sources - [Dreamwork website](https://dreamworkhq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DropTheHassle MCP server | Agent MCP Directory" description: "DropTheHassle has an open MCP server with 52 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dropthehassle-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DropTheHassle MCP server | Agent MCP Directory > DropTheHassle has an open MCP server with 52 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dropthehassle-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DropTheHassle: MCP server, CLI and agent surfaces Yes: DropTheHassle runs a public MCP server at dropthehassle.com that listed 52 tools to a client with no credentials on 4 November 2026. Examples: whoami, list\_sites, search\_domain. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | DropTheHassle | | --- | --- | | Domain | dropthehassle.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for dropthehassle.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://dropthehassle.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | dropthehassle 0.5.1 | | Capabilities | tools | | Tools | 52 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 708 ms over 1 attempt | ### Tools listed 52 tools; the first 40 names are recorded - whoami - list\_sites - search\_domain - check\_trademark - domain\_email - sign\_in - deploy\_site - list\_site\_files - get\_site\_file - edit\_site\_file - send\_claim\_mail - point\_domain - choose\_link - set\_backend - get\_checkout\_link - site\_of\_the\_day\_badge - award\_readiness - site\_status - site\_analytics - rollback\_site - delete\_site - transfer\_domain\_out - domain\_renewal - email\_status - get\_email\_checkout\_link - connect\_domain - make\_primary\_domain - split\_domain - update\_site\_settings - set\_site\_image - set\_site\_password - clear\_site\_password - set\_analytics\_level - check\_live - resend\_owner\_verification - claim\_site - list\_invoices - resend\_receipt - remove\_email\_address - turn\_off\_email ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:15Z https://dropthehassle.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 970 ms - 20:02:45Z https://dropthehassle.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 708 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://dropthehassle.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DropTheHassle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dropthehassle-com/index.md) ## Sources - [DropTheHassle website](https://dropthehassle.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "DSers MCP server | Agent MCP Directory" description: "DSers: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dsers-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # DSers MCP server | Agent MCP Directory > DSers: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dsers-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # DSers: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for DSers at ai.dsers.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | DSers (registry title: DSers Official MCP Server) | | --- | --- | | Domain | dsers.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for dsers.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.dsers.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,753 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:16Z https://ai.dsers.com/mcp sent initialize result auth-required (HTTP 401) 1854 ms - 20:02:46Z https://ai.dsers.com/mcp sent initialize result auth-required (HTTP 401) 1753 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://ai.dsers.com/.well-known/oauth-protected-resource" | | Protected resource metadata | ai.dsers.com | | Authorization server metadata | ai.dsers.com | | Registration endpoint | https://ai.dsers.com/oauth/register | ### The sign-in route, step by step 1. Request `https://ai.dsers.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://ai.dsers.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://ai.dsers.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for DSers. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dsers-com/index.md) ## Sources - [Where DSers was found](https://github.com/mcp/dsers/dsers-mcp-server), read 4 November 2026 - [DSers website](https://dsers.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dueback MCP server | Agent MCP Directory" description: "Dueback has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dueback-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dueback MCP server | Agent MCP Directory > Dueback has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/dueback-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dueback: MCP server, CLI and agent surfaces Yes: Dueback runs a public MCP server at api.dueback.co that listed 5 tools to a client with no credentials on 4 November 2026. Examples: detect\_negotiable\_bill, start\_negotiation\_case, get\_case\_status. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Dueback | | --- | --- | | Domain | dueback.co | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for dueback.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.dueback.co/mcp/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | dueback 0.1.3 | | Capabilities | prompts, resources, tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 797 ms over 1 attempt | ### Tools listed 5 tools - detect\_negotiable\_bill - start\_negotiation\_case - get\_case\_status - list\_my\_cases - list\_verified\_savings ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:16Z https://api.dueback.co/mcp/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 923 ms - 20:02:45Z https://api.dueback.co/mcp/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 797 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.dueback.co/mcp/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dueback. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dueback-co/index.md) ## Sources - [Where Dueback was found](https://github.com/mcp/dunrossmai-rgb/dueback-mcp), read 4 November 2026 - [Dueback website](https://dueback.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Duffel MCP server | Agent MCP Directory" description: "Does Duffel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/duffel-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Duffel MCP server | Agent MCP Directory > Does Duffel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/duffel-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Duffel: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Duffel (duffel.com), so the connector had nothing to connect to. Ora's cached score for duffel.com is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Duffel (registry title: duffel.com) | | --- | --- | | Domain | duffel.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for duffel.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Duffel. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for duffel.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Duffel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/duffel-com/index.md) ## Sources - [Ora score page for duffel.com](https://ora.ai/score/duffel.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Duffel was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Duffel website](https://duffel.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dynatrace MCP server | Agent MCP Directory" description: "Does Dynatrace have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/dynatrace-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dynatrace MCP server | Agent MCP Directory > Does Dynatrace have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/dynatrace-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dynatrace: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Dynatrace (dynatrace.com), so the connector had nothing to connect to. Ora's cached score for dynatrace.com is 82, grade B, read on 5 November 2026. The company was added from the GitHub MCP Registry. ## Fact sheet | Company | Dynatrace | | --- | --- | | Domain | dynatrace.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 407 on the list of 4 November 2026 | | Ora score | 82, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for dynatrace.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Dynatrace. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for dynatrace.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | Listed | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Dynatrace. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/dynatrace-com/index.md) ## Sources - [Ora score page for dynatrace.com](https://ora.ai/score/dynatrace.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Dynatrace was found](https://github.com/mcp/Dynatrace/dynatrace-for-ai), read 4 November 2026 - [Dynatrace website](https://dynatrace.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "EAN-Search.org MCP server | Agent MCP Directory" description: "EAN-Search.org: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/ean-search-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # EAN-Search.org MCP server | Agent MCP Directory > EAN-Search.org: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/ean-search-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # EAN-Search.org: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for EAN-Search.org at www.ean-search.org answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | EAN-Search.org | | --- | --- | | Domain | ean-search.org | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for ean-search.org when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.ean-search.org/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 485 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:16Z https://www.ean-search.org/mcp sent initialize result auth-required (HTTP 401) 582 ms - 20:02:46Z https://www.ean-search.org/mcp sent initialize result auth-required (HTTP 401) 485 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://www.ean-search.org/.well-known/oauth-protected-resource" | | Protected resource metadata | www.ean-search.org | | Authorization server metadata | www.ean-search.org | | Registration endpoint | https://www.ean-search.org/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://www.ean-search.org/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.ean-search.org/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.ean-search.org/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for EAN-Search.org. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ean-search-org/index.md) ## Sources - [Where EAN-Search.org was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [EAN-Search.org website](https://ean-search.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "EasyGerber MCP server | Agent MCP Directory" description: "EasyGerber has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/easygerber-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # EasyGerber MCP server | Agent MCP Directory > EasyGerber has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/easygerber-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # EasyGerber: MCP server, CLI and agent surfaces Yes: EasyGerber runs a public MCP server at www.easygerber.com that listed 15 tools to a client with no credentials on 4 November 2026. Examples: submit\_feedback, get\_profile, list\_organizations. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | EasyGerber (registry title: EasyGerber: AI PCB design, layout, and routing) | | --- | --- | | Domain | easygerber.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for easygerber.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.easygerber.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | easygerber 0.1.0 | | Capabilities | tools | | Tools | 15 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,961 ms over 1 attempt | ### Tools listed 15 tools - submit\_feedback - get\_profile - list\_organizations - search\_parts - get\_part - list\_boards - get\_board - create\_board - update\_board - delete\_board - generate\_layout - get\_generation - stop\_generation - check\_board\_layout - export\_board ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:18Z https://www.easygerber.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2497 ms - 20:02:47Z https://www.easygerber.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1961 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.easygerber.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for EasyGerber. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/easygerber-com/index.md) ## Sources - [EasyGerber website](https://easygerber.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Easyship MCP server | Agent MCP Directory" description: "Easyship: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/easyship-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Easyship MCP server | Agent MCP Directory > Easyship: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/easyship-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Easyship: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Easyship at mcp.easyship.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Easyship | | --- | --- | | Domain | easyship.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 59, grade C; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for easyship.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.easyship.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 711 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:17Z https://mcp.easyship.com/mcp sent initialize result auth-required (HTTP 401) 795 ms - 20:02:46Z https://mcp.easyship.com/mcp sent initialize result auth-required (HTTP 401) 711 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.easyship.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.easyship.com | | Authorization server metadata | mcp.easyship.com | | Registration endpoint | https://mcp.easyship.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.easyship.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.easyship.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.easyship.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Easyship. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.easyship/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/easyship-com/index.md) ## Sources - [Ora score page for easyship.com](https://ora.ai/score/easyship.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=easyship), read 4 November 2026 - [Easyship website](https://easyship.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Edgaze MCP server | Agent MCP Directory" description: "Edgaze: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/edgaze-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Edgaze MCP server | Agent MCP Directory > Edgaze: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/edgaze-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Edgaze: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Edgaze at mcp.edgaze.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Edgaze | | --- | --- | | Domain | edgaze.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for edgaze.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.edgaze.ai | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,048 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:17Z https://mcp.edgaze.ai sent initialize result auth-required (HTTP 401) 951 ms - 20:02:47Z https://mcp.edgaze.ai sent initialize result auth-required (HTTP 401) 1048 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Edgaze", resource_metadata="https://mcp.edgaze.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.edgaze.ai | | Authorization server metadata | mcp.edgaze.ai | | Registration endpoint | https://server.edgaze.ai/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://mcp.edgaze.ai` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.edgaze.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://server.edgaze.ai/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Edgaze. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.edgaze.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.edgaze/edgaze | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/edgaze-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=edgaze), read 4 November 2026 - [Edgaze website](https://edgaze.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Editalmd MCP server | Agent MCP Directory" description: "Editalmd has an open MCP server with 78 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/editalmd-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Editalmd MCP server | Agent MCP Directory > Editalmd has an open MCP server with 78 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/editalmd-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Editalmd: MCP server, CLI and agent surfaces Yes: Editalmd runs a public MCP server at editalmd.com that listed 78 tools to a client with no credentials on 4 November 2026. Examples: evaluation\_quota, evaluation\_premium, evaluation\_basic. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Editalmd | | --- | --- | | Domain | editalmd.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for editalmd.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://editalmd.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | EditalMD fb0c5518 | | Capabilities | tools, prompts | | Tools | 78 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,418 ms over 1 attempt | ### Tools listed 78 tools; the first 40 names are recorded - evaluation\_quota - evaluation\_premium - evaluation\_basic - evaluation\_basic\_result - company\_documents - attach\_company\_document - remove\_company\_document - analyze\_participation - get\_participation - list\_my\_companies - search\_companies - add\_company - select\_company - remove\_company - awarded\_prices - framework\_agreements - procurement\_plans - tenders\_outside\_pncp - my\_account - my\_documents - my\_procurements - documento\_vincular - documento\_acesso - account\_tracking - claim\_guest\_tracking - lookup\_reference - preview\_alert - update\_alert - list\_saved - save\_procurement - remove\_saved - gerar\_markdown - generation\_status - original\_status - request\_original - criar\_cobranca - estado\_cobranca - list\_examples - get\_document - get\_document\_dossier ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:19Z https://editalmd.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2713 ms - 20:02:48Z https://editalmd.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2418 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://editalmd.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Editalmd. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: editalmd.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.editalmd/editalmd | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/editalmd-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=editalmd), read 4 November 2026 - [Editalmd website](https://editalmd.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Egnyte MCP server | Agent MCP Directory" description: "Egnyte: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/egnyte-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Egnyte MCP server | Agent MCP Directory > Egnyte: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/egnyte-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Egnyte: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Egnyte at mcp-server.egnyte.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Egnyte | | --- | --- | | Domain | egnyte.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,430 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for egnyte.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp-server.egnyte.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 564 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:59Z https://mcp-server.egnyte.com/mcp sent initialize result auth-required (HTTP 401) 994 ms - 20:01:34Z https://mcp-server.egnyte.com/mcp sent initialize result auth-required (HTTP 401) 564 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp-server.egnyte.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp-server.egnyte.com | | Authorization server metadata | mcp-oauth.egnyte.com | | Registration endpoint | https://mcp-oauth.egnyte.com/clients | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp-server.egnyte.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp-server.egnyte.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp-oauth.egnyte.com/clients` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Egnyte. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.egnyte/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/egnyte-com/index.md) ## Sources - [Where Egnyte was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=egnyte), read 4 November 2026 - [Egnyte website](https://egnyte.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Elastic MCP server | Agent MCP Directory" description: "Does Elastic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/elastic-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Elastic MCP server | Agent MCP Directory > Does Elastic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/elastic-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Elastic: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Elastic (elastic.co), so the connector had nothing to connect to. Ora's cached score for elastic.co is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Elastic | | --- | --- | | Domain | elastic.co | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,243 on the list of 4 November 2026 | | Ora score | 59, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for elastic.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Elastic. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for elastic.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Elastic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/elastic-co/index.md) ## Sources - [Ora score page for elastic.co](https://ora.ai/score/elastic.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/score) - [Where Elastic was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Elastic website](https://elastic.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Electroneek MCP server | Agent MCP Directory" description: "Does Electroneek have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/electroneek-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Electroneek MCP server | Agent MCP Directory > Does Electroneek have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/electroneek-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Electroneek: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Electroneek (electroneek.com), so the connector had nothing to connect to. Ora's cached score for electroneek.com is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Electroneek (registry title: electroneek.com) | | --- | --- | | Domain | electroneek.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for electroneek.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Electroneek. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for electroneek.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Electroneek. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/electroneek-com/index.md) ## Sources - [Ora score page for electroneek.com](https://ora.ai/score/electroneek.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Electroneek was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Electroneek website](https://electroneek.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Elementary Data MCP server | Agent MCP Directory" description: "Elementary Data has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/elementary-data-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Elementary Data MCP server | Agent MCP Directory > Elementary Data has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/elementary-data-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Elementary Data: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Elementary Data; the connector tried mcp.elementary-data.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: ERR\_TLS\_CERT\_ALTNAME\_INVALID. Ora's cached score for elementary-data.com is 56, grade C, read on 5 November 2026. ## Fact sheet | Company | Elementary Data (registry title: elementary-data.com) | | --- | --- | | Domain | elementary-data.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 56, grade C; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for elementary-data.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.elementary-data.com/mcp | | --- | --- | | How it was found | mcp.elementary-data.com was tried as a guess and did not answer | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 160 ms over 1 attempt | | Result | ERR_TLS_CERT_ALTNAME_INVALID | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:18Z https://mcp.elementary-data.com/mcp sent initialize result no-answer 255 ms - 20:02:47Z https://mcp.elementary-data.com/mcp sent initialize result no-answer 160 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.elementary-data.com/mcp`. The connector could not tell what it wants: ERR\_TLS\_CERT\_ALTNAME\_INVALID. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Elementary Data. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/elementary-data-com/index.md) ## Sources - [Ora score page for elementary-data.com](https://ora.ai/score/elementary-data.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/leaderboard) - [Where Elementary Data was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Elementary Data website](https://elementary-data.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ElevenFlo MCP server | Agent MCP Directory" description: "ElevenFlo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/elevenflo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ElevenFlo MCP server | Agent MCP Directory > ElevenFlo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/elevenflo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ElevenFlo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ElevenFlo at elevenflo.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ElevenFlo (registry title: ElevenFlo MCP) | | --- | --- | | Domain | elevenflo.com | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for elevenflo.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://elevenflo.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,439 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:19Z https://elevenflo.com/mcp sent initialize result auth-required (HTTP 401) 1291 ms - 20:02:48Z https://elevenflo.com/mcp sent initialize result auth-required (HTTP 401) 1439 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://elevenflo.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | elevenflo.com | | Authorization server metadata | elevenflo.com | | Registration endpoint | https://elevenflo.com/api/accounts/mcp/oauth/register/ | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://elevenflo.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://elevenflo.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://elevenflo.com/api/accounts/mcp/oauth/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ElevenFlo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.elevenflo/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/elevenflo-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=elevenflo), read 4 November 2026 - [ElevenFlo website](https://elevenflo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ElevenLabs MCP server | Agent MCP Directory" description: "ElevenLabs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/elevenlabs-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ElevenLabs MCP server | Agent MCP Directory > ElevenLabs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/elevenlabs-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # ElevenLabs: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ElevenLabs at api.us.elevenlabs.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ElevenLabs | | --- | --- | | Domain | elevenlabs.io | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,230 on the list of 4 November 2026 | | Ora score | 86, grade A; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for elevenlabs.io, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.us.elevenlabs.io/v1/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 721 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:02Z https://api.us.elevenlabs.io/v1/mcp sent initialize result auth-required (HTTP 401) 652 ms - 20:01:38Z https://api.us.elevenlabs.io/v1/mcp sent initialize result auth-required (HTTP 401) 721 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.us.elevenlabs.io/.well-known/oauth-protected-resource" | | Protected resource metadata | api.us.elevenlabs.io | | Authorization server metadata | api.us.elevenlabs.io | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.us.elevenlabs.io/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.us.elevenlabs.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ElevenLabs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.elevenlabs/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/elevenlabs-io/index.md) ## Sources - [Ora score page for elevenlabs.io](https://ora.ai/score/elevenlabs.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Where ElevenLabs was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.elevenlabs%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=elevenlabs), read 4 November 2026 - [ElevenLabs website](https://elevenlabs.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Elfsight AI MCP server | Agent MCP Directory" description: "Elfsight AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM." canonical: https://agentmcpdirectory.com/directory/elfsight-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Elfsight AI MCP server | Agent MCP Directory > Elfsight AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM. Source: https://agentmcpdirectory.com/directory/elfsight-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Elfsight AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Elfsight AI at mcp.elfsight.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Elfsight AI (registry title: Elfsight AI Chatbot) | | --- | --- | | Domain | elfsight.com | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 7,565 on the list of 4 November 2026 | | Ora score | 45, grade D; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for elfsight.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.elfsight.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 810 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:13Z https://mcp.elfsight.com/mcp sent initialize result auth-required (HTTP 401) 695 ms - 20:01:52Z https://mcp.elfsight.com/mcp sent initialize result auth-required (HTTP 401) 810 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.elfsight.com/.well-known/oauth-protected-resource/mcp", scope="mcp" | | Protected resource metadata | mcp.elfsight.com | | Authorization server metadata | core.service.elfsight.com | | Registration endpoint | https://core.service.elfsight.com/mcp-auth/register-mcp-client | ### The sign-in route, step by step 1. Request `https://mcp.elfsight.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.elfsight.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://core.service.elfsight.com/mcp-auth/register-mcp-client` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Elfsight AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.elfsight/ai-chatbot, com.elfsight/elfsight | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/elfsight-com/index.md) ## Sources - [Ora score page for elfsight.com](https://ora.ai/score/elfsight.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=elfsight), read 4 November 2026 - [Elfsight AI website](https://elfsight.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ellipsis MCP server | Agent MCP Directory" description: "Ellipsis has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/ellipsis-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ellipsis MCP server | Agent MCP Directory > Ellipsis has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/ellipsis-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ellipsis: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Ellipsis; the connector tried mcp.ellipsis.dev as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | Ellipsis (registry title: ellipsis.dev) | | --- | --- | | Domain | ellipsis.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 69, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ellipsis.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.ellipsis.dev/mcp | | --- | --- | | How it was found | mcp.ellipsis.dev was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,097 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:19Z https://mcp.ellipsis.dev/mcp sent initialize result no-answer (HTTP 404) 1025 ms - 20:02:48Z https://mcp.ellipsis.dev/mcp sent initialize result no-answer (HTTP 404) 1097 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.ellipsis.dev/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ellipsis. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ellipsis-dev/index.md) ## Sources - [Ora score page for ellipsis.dev](https://ora.ai/score/ellipsis.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Ellipsis was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ellipsis website](https://ellipsis.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Embrace MCP server | Agent MCP Directory" description: "Embrace: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/embrace-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Embrace MCP server | Agent MCP Directory > Embrace: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/embrace-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Embrace: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Embrace; the connector's guess at mcp.embrace.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Embrace (registry title: embrace.io) | | --- | --- | | Domain | embrace.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 38, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for embrace.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.embrace.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,091 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:20Z https://mcp.embrace.io/mcp sent initialize result auth-required (HTTP 401) 1942 ms - 20:02:50Z https://mcp.embrace.io/mcp sent initialize result auth-required (HTTP 401) 2091 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="http://mcp.embrace.io/.well-known/oauth-protected-resource", scope="mcp:read mcp:write mcp:tools:call" | | Protected resource metadata | mcp.embrace.io | | Authorization server metadata | dash-api.embrace.io | | Registration endpoint | https://dash-api.embrace.io/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.embrace.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `http://mcp.embrace.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://dash-api.embrace.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Embrace. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/embrace-io/index.md) ## Sources - [Ora score page for embrace.io](https://ora.ai/score/embrace.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Embrace was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Embrace website](https://embrace.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "emem MCP server | Agent MCP Directory" description: "emem has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/emem-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # emem MCP server | Agent MCP Directory > emem has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/emem-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # emem: MCP server, CLI and agent surfaces Yes: emem runs a public MCP server at emem.dev that listed 18 tools to a client with no credentials on 4 November 2026. Examples: emem\_entity, emem\_locate, emem\_recall. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for emem.dev is 85, grade B, read on 5 November 2026. ## Fact sheet | Company | emem (registry title: emem, the verifiable memory protocol for the physical world) | | --- | --- | | Domain | emem.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 85, grade B; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for emem.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://emem.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | emem 2.4.4 | | Capabilities | extensions, prompts, resources, tasks, tools | | Tools | 18 | | Resources | 21 | | Prompts | 12 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,934 ms over 1 attempt | ### Tools listed 18 tools - emem\_entity - emem\_locate - emem\_recall - emem\_memory\_token - emem\_memory\_token\_resolve - emem\_verify\_receipt - emem\_memory\_contradictions - emem\_guard\_verdict - emem\_tools - emem\_ask - search - fetch - emem\_echo\_verify - emem\_memory\_bundle - emem\_entity\_resolve - emem\_entity\_link - emem\_find\_similar - emem\_intent ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:21Z https://emem.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2050 ms - 20:02:50Z https://emem.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1934 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://emem.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for emem. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/emem-dev/index.md) ## Sources - [Ora score page for emem.dev](https://ora.ai/score/emem.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/score) - [Where emem was found](https://github.com/mcp/Vortx-AI/emem), read 4 November 2026 - [emem website](https://emem.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "EmpirioLabs AI MCP server | Agent MCP Directory" description: "EmpirioLabs AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/empiriolabs-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # EmpirioLabs AI MCP server | Agent MCP Directory > EmpirioLabs AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/empiriolabs-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # EmpirioLabs AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for EmpirioLabs AI at mcp.empiriolabs.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | EmpirioLabs AI | | --- | --- | | Domain | empiriolabs.ai | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for empiriolabs.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.empiriolabs.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,260 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:20Z https://mcp.empiriolabs.ai/mcp sent initialize result auth-required (HTTP 401) 1261 ms - 20:02:49Z https://mcp.empiriolabs.ai/mcp sent initialize result auth-required (HTTP 401) 1260 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.empiriolabs.ai/.well-known/oauth-protected-resource/mcp", scope="models text search media jobs agents account batch gpu hosted_agents" | | Protected resource metadata | mcp.empiriolabs.ai | | Authorization server metadata | platform.empiriolabs.ai | | Registration endpoint | https://platform.empiriolabs.ai/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.empiriolabs.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.empiriolabs.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://platform.empiriolabs.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for EmpirioLabs AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.empiriolabs/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/empiriolabs-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=empiriolabs), read 4 November 2026 - [EmpirioLabs AI website](https://empiriolabs.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Encord MCP server | Agent MCP Directory" description: "Encord: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/encord-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Encord MCP server | Agent MCP Directory > Encord: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/encord-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Encord: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Encord; the connector's guess at mcp.encord.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Encord (registry title: encord.com) | | --- | --- | | Domain | encord.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 69, grade C; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for encord.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.encord.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,414 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:21Z https://mcp.encord.com/mcp sent initialize result auth-required (HTTP 401) 1444 ms - 20:02:50Z https://mcp.encord.com/mcp sent initialize result auth-required (HTTP 401) 1414 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.encord.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.encord.com | | Authorization server metadata | authkit.encord.com | | Registration endpoint | https://authkit.encord.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.encord.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.encord.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://authkit.encord.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Encord. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/encord-com/index.md) ## Sources - [Ora score page for encord.com](https://ora.ai/score/encord.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Encord was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Encord website](https://encord.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Env0 MCP server | Agent MCP Directory" description: "Does Env0 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/env0-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Env0 MCP server | Agent MCP Directory > Does Env0 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/env0-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Env0: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Env0 (env0.com), so the connector had nothing to connect to. Ora's cached score for env0.com is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Env0 (registry title: env0.com) | | --- | --- | | Domain | env0.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for env0.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Env0. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for env0.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Env0. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/env0-com/index.md) ## Sources - [Ora score page for env0.com](https://ora.ai/score/env0.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Env0 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Env0 website](https://env0.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Eodly MCP server | Agent MCP Directory" description: "Eodly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/eodly-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Eodly MCP server | Agent MCP Directory > Eodly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/eodly-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Eodly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Eodly at eodly.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Eodly (registry title: Layergen Eodly) | | --- | --- | | Domain | eodly.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 85, grade B; Ora scanned the domain on 7 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for eodly.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://eodly.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 731 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:22Z https://eodly.io/mcp sent initialize result auth-required (HTTP 401) 1158 ms - 20:02:50Z https://eodly.io/mcp sent initialize result auth-required (HTTP 401) 731 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://eodly.io/.well-known/oauth-protected-resource" | | Protected resource metadata | eodly.io | | Authorization server metadata | eodly.io | | Registration endpoint | https://eodly.io/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://eodly.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://eodly.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://eodly.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Eodly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: eodly.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/eodly-io/index.md) ## Sources - [Ora score page for eodly.io](https://ora.ai/score/eodly.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 September 2026, read from GET /api/score) - [Where Eodly was found](https://github.com/mcp/layergen/eodly-mcp), read 4 November 2026 - [Eodly website](https://eodly.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Epidemic Sound MCP server | Agent MCP Directory" description: "Epidemic Sound: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/epidemicsound-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Epidemic Sound MCP server | Agent MCP Directory > Epidemic Sound: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/epidemicsound-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Epidemic Sound: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Epidemic Sound at www.epidemicsound.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Epidemic Sound (registry title: epidemicsound.com) | | --- | --- | | Domain | epidemicsound.com | | Category | Gaming & Media (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for epidemicsound.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.epidemicsound.com/a/mcp-service/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 679 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:22Z https://www.epidemicsound.com/a/mcp-service/mcp sent initialize result auth-required (HTTP 401) 1125 ms - 20:02:50Z https://www.epidemicsound.com/a/mcp-service/mcp sent initialize result auth-required (HTTP 401) 679 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.epidemicsound.com/.well-known/oauth-protected-resource" | | Protected resource metadata | www.epidemicsound.com | | Authorization server metadata | login.epidemicsound.com | | Registration endpoint | https://login.epidemicsound.com/auth/realms/accounts/clients-registrations/openid-connect | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://www.epidemicsound.com/a/mcp-service/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.epidemicsound.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://login.epidemicsound.com/auth/realms/accounts/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Epidemic Sound. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.epidemicsound/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/epidemicsound-com/index.md) ## Sources - [Ora score page for epidemicsound.com](https://ora.ai/score/epidemicsound.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/leaderboard) - [Where Epidemic Sound was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.epidemicsound%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=epidemicsound), read 4 November 2026 - [Epidemic Sound website](https://epidemicsound.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Epinu MCP server | Agent MCP Directory" description: "Epinu has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/epinu-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Epinu MCP server | Agent MCP Directory > Epinu has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/epinu-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Epinu: MCP server, CLI and agent surfaces Yes: Epinu runs a public MCP server at api.epinu.ai that listed 5 tools to a client with no credentials on 4 November 2026. Examples: projects\_search, getting\_started, marketplace\_listings\_search. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Epinu | | --- | --- | | Domain | epinu.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for epinu.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.epinu.ai/api/agent/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | epinu-agent-api 0.1.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 936 ms over 1 attempt | ### Tools listed 5 tools - projects\_search - getting\_started - marketplace\_listings\_search - search - fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:22Z https://api.epinu.ai/api/agent/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1132 ms - 20:02:51Z https://api.epinu.ai/api/agent/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 936 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.epinu.ai/api/agent/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Epinu. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.epinu/epinu | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/epinu-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=epinu), read 4 November 2026 - [Epinu website](https://epinu.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Epsilla MCP server | Agent MCP Directory" description: "Does Epsilla have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/epsilla-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Epsilla MCP server | Agent MCP Directory > Does Epsilla have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/epsilla-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Epsilla: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Epsilla (epsilla.com), so the connector had nothing to connect to. Ora's cached score for epsilla.com is 57, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Epsilla (registry title: epsilla.com) | | --- | --- | | Domain | epsilla.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 57, grade C; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for epsilla.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Epsilla. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for epsilla.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Epsilla. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/epsilla-com/index.md) ## Sources - [Ora score page for epsilla.com](https://ora.ai/score/epsilla.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 September 2026, read from GET /api/leaderboard) - [Where Epsilla was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Epsilla website](https://epsilla.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "eResource Scheduler MCP server | Agent MCP Directory" description: "eResource Scheduler: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/eresourcescheduler-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # eResource Scheduler MCP server | Agent MCP Directory > eResource Scheduler: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/eresourcescheduler-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # eResource Scheduler: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for eResource Scheduler at app.eresourcescheduler.cloud answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | eResource Scheduler | | --- | --- | | Domain | eresourcescheduler.cloud | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for eresourcescheduler.cloud when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.eresourcescheduler.cloud/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 671 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:22Z https://app.eresourcescheduler.cloud/mcp sent initialize result auth-required (HTTP 401) 795 ms - 20:02:51Z https://app.eresourcescheduler.cloud/mcp sent initialize result auth-required (HTTP 401) 671 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://app.eresourcescheduler.cloud/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | app.eresourcescheduler.cloud | | Authorization server metadata | app.eresourcescheduler.cloud | | Registration endpoint | https://app.eresourcescheduler.cloud/login/oauth/register | ### The sign-in route, step by step 1. Request `https://app.eresourcescheduler.cloud/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.eresourcescheduler.cloud/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.eresourcescheduler.cloud/login/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for eResource Scheduler. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: cloud.eresourcescheduler.app/eresource-scheduler | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/eresourcescheduler-cloud/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=eresourcescheduler), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "esimgomobile MCP server | Agent MCP Directory" description: "esimgomobile has an open MCP server with 39 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/esimgomobile-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # esimgomobile MCP server | Agent MCP Directory > esimgomobile has an open MCP server with 39 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/esimgomobile-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # esimgomobile: MCP server, CLI and agent surfaces Yes: esimgomobile runs a public MCP server at mcp.esimgomobile.com that listed 39 tools to a client with no credentials on 4 November 2026. Examples: forecast\_data\_threshold, check\_activation\_details\_format, list\_sample\_esims. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | esimgomobile (registry title: esimgomobile: Travel eSIM Tools) | | --- | --- | | Domain | esimgomobile.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for esimgomobile.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.esimgomobile.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | esimgomobile 0.1.0 | | Capabilities | resources, tools | | Tools | 39 | | Resources | 8 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 179 ms over 1 attempt | ### Tools listed 39 tools - forecast\_data\_threshold - check\_activation\_details\_format - list\_sample\_esims - run\_speed\_test - get\_public\_ip - check\_roaming\_status - measure\_latency - grade\_connection\_quality - detect\_captive\_portal - check\_dns\_leaks - get\_wifi\_security\_checklist - lookup\_speed\_requirements - check\_coverage - estimate\_data\_usage - calculate\_roaming\_cost - plan\_multi\_country\_esim - check\_device\_compatibility - check\_carrier\_lock - find\_best\_network - get\_airport\_connectivity - find\_free\_wifi - get\_country\_fact\_sheet - check\_internet\_freedom - get\_installation\_guide - troubleshoot\_esim - lookup\_apn\_settings - setup\_dual\_sim - setup\_data\_saver - format\_international\_number - calculate\_data\_budget - list\_available\_plans - recommend\_plan - get\_travel\_data\_checklist - search\_plans - get\_plan\_details - compare\_plans - validate\_order\_draft - plan\_trip - list\_country\_networks ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:22Z https://mcp.esimgomobile.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 609 ms - 20:02:50Z https://mcp.esimgomobile.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 179 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.esimgomobile.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for esimgomobile. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.esimgomobile/esimgomobile | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/esimgomobile-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=esimgomobile), read 4 November 2026 - [esimgomobile website](https://esimgomobile.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Etherscan MCP server | Agent MCP Directory" description: "Etherscan has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/etherscan-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Etherscan MCP server | Agent MCP Directory > Etherscan has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/etherscan-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Etherscan: MCP server, CLI and agent surfaces Yes: Etherscan runs a public MCP server at mcp-keyless.etherscan.io that listed 17 tools to a client with no credentials on 4 November 2026. Examples: get\_native\_balance, get\_transactions, get\_internal\_transactions. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Etherscan | | --- | --- | | Domain | etherscan.io | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 5,489 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for etherscan.io when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp-keyless.etherscan.io/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | etherscan-mcp 2.4.0 | | Capabilities | tools, resources | | Tools | 17 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,219 ms over 1 attempt | ### Tools listed 17 tools - get\_native\_balance - get\_transactions - get\_internal\_transactions - get\_token\_transfers - resolve\_ens\_name - get\_contract\_source - get\_contract\_abi - get\_contract\_creation - get\_transaction\_receipt\_status - get\_transaction\_status - get\_gas\_oracle - get\_block\_by\_timestamp - get\_supported\_chains - get\_logs - get\_transaction\_by\_hash - get\_transaction\_receipt - render\_etherscan\_widget ### Connector log 4 connections on 4 November 2026, read-only methods only - 19:56:08Z https://mcp.etherscan.io/mcp sent initialize result auth-required-no-oauth (HTTP 401) 807 ms - 19:56:09Z https://mcp-keyless.etherscan.io/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 875 ms - 20:01:46Z https://mcp.etherscan.io/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1197 ms - 20:01:47Z https://mcp-keyless.etherscan.io/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1219 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp-keyless.etherscan.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Etherscan. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.etherscan/etherscan-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/etherscan-io/index.md) ## Sources - [Where Etherscan was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.etherscan%2Fetherscan-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=etherscan), read 4 November 2026 - [Etherscan website](https://etherscan.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Everhour MCP server | Agent MCP Directory" description: "Does Everhour have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/everhour-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Everhour MCP server | Agent MCP Directory > Does Everhour have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/everhour-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Everhour: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Everhour (everhour.com), so the connector had nothing to connect to. Ora's cached score for everhour.com is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Everhour (registry title: everhour.com) | | --- | --- | | Domain | everhour.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for everhour.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Everhour. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for everhour.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Everhour. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/everhour-com/index.md) ## Sources - [Ora score page for everhour.com](https://ora.ai/score/everhour.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/leaderboard) - [Where Everhour was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Everhour website](https://everhour.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Evermuse MCP server | Agent MCP Directory" description: "Evermuse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/evermuse-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Evermuse MCP server | Agent MCP Directory > Evermuse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/evermuse-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Evermuse: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Evermuse at api.evermuse.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Evermuse | | --- | --- | | Domain | evermuse.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for evermuse.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.evermuse.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 773 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:23Z https://api.evermuse.com/api/mcp sent initialize result auth-required (HTTP 401) 947 ms - 20:02:51Z https://api.evermuse.com/api/mcp sent initialize result auth-required (HTTP 401) 773 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.evermuse.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.evermuse.com | | Authorization server metadata | api.evermuse.com | | Registration endpoint | https://api.evermuse.com/oauth/register | ### The sign-in route, step by step 1. Request `https://api.evermuse.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.evermuse.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.evermuse.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Evermuse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.evermuse/evermuse | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/evermuse-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=evermuse), read 4 November 2026 - [Evermuse website](https://evermuse.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "EveryCalc MCP server | Agent MCP Directory" description: "EveryCalc has an open MCP server with 69 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/everycalc-xyz site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # EveryCalc MCP server | Agent MCP Directory > EveryCalc has an open MCP server with 69 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/everycalc-xyz Site: Agent MCP Directory Last reviewed: 2026-11-05 # EveryCalc: MCP server, CLI and agent surfaces Yes: EveryCalc runs a public MCP server at everycalc.xyz that listed 69 tools to a client with no credentials on 4 November 2026. Examples: calculate\_mortgage, calculate\_refinance, calculate\_affordability. It speaks streamable-http, protocol 2025-03-26. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | EveryCalc | | --- | --- | | Domain | everycalc.xyz | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for everycalc.xyz when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://everycalc.xyz/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | everycalc 1.1.0 | | Capabilities | tools | | Tools | 69 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 138 ms over 1 attempt | ### Tools listed 69 tools; the first 40 names are recorded - calculate\_mortgage - calculate\_refinance - calculate\_affordability - calculate\_loan - calculate\_compound\_interest - calculate\_percentage - calculate\_tip - calculate\_salary - calculate\_age - calculate\_auto\_loan - calculate\_date\_duration - calculate\_debt\_payoff - calculate\_inflation - calculate\_rent\_vs\_buy - calculate\_roth\_vs\_traditional - calculate\_unit\_converter - calculate\_word\_counter - calculate\_401k - calculate\_arm\_vs\_fixed - calculate\_biweekly\_mortgage - calculate\_bmi\_tdee - calculate\_capital\_gains\_tax - calculate\_car\_affordability - calculate\_credit\_card\_payoff - calculate\_emergency\_fund - calculate\_income\_tax\_estimator - calculate\_lease\_vs\_buy - calculate\_net\_worth - calculate\_paycheck - calculate\_property\_tax\_estimator - calculate\_raise\_vs\_inflation - calculate\_retirement\_savings\_planner - calculate\_roth\_conversion - calculate\_sba\_loan - calculate\_social\_security\_estimator - calculate\_aft - calculate\_bah - calculate\_brs\_vs\_high3 - calculate\_gi\_bill - calculate\_les\_decoder ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:22Z https://everycalc.xyz/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 377 ms - 20:02:51Z https://everycalc.xyz/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 138 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://everycalc.xyz/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for EveryCalc. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/everycalc-xyz/index.md) ## Sources - [EveryCalc website](https://everycalc.xyz), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Evidently AI MCP server | Agent MCP Directory" description: "Does Evidently AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/evidentlyai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Evidently AI MCP server | Agent MCP Directory > Does Evidently AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/evidentlyai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Evidently AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Evidently AI (evidentlyai.com), so the connector had nothing to connect to. Ora's cached score for evidentlyai.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Evidently AI (registry title: evidentlyai.com) | | --- | --- | | Domain | evidentlyai.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for evidentlyai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Evidently AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for evidentlyai.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Evidently AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/evidentlyai-com/index.md) ## Sources - [Ora score page for evidentlyai.com](https://ora.ai/score/evidentlyai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/leaderboard) - [Where Evidently AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Evidently AI website](https://evidentlyai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Exa MCP server | Agent MCP Directory" description: "Exa has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/exa-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Exa MCP server | Agent MCP Directory > Exa has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/exa-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Exa: MCP server, CLI and agent surfaces Yes: Exa runs a public MCP server at mcp.exa.ai that listed 2 tools to a client with no credentials on 4 November 2026. Examples: web\_search\_exa, web\_fetch\_exa. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for exa.ai is 91, grade A, read on 5 November 2026. ## Fact sheet | Company | Exa | | --- | --- | | Domain | exa.ai | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 91, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for exa.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.exa.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | exa-search-server 3.5.0 | | Capabilities | tools, prompts, resources | | Tools | 2 | | Resources | 1 | | Prompts | 1 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,211 ms over 1 attempt | ### Tools listed 2 tools - web\_search\_exa - web\_fetch\_exa ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:24Z https://mcp.exa.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1141 ms - 20:02:52Z https://mcp.exa.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1211 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.exa.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Exa. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: exa.ai/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.exa/exa | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Yes: exa | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/exa-ai/index.md) ## Sources - [Ora score page for exa.ai](https://ora.ai/score/exa.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Exa was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=exa), read 4 November 2026 - [Exa website](https://exa.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Example4 MCP server | Agent MCP Directory" description: "Example4 has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/example4-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Example4 MCP server | Agent MCP Directory > Example4 has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/example4-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Example4: MCP server, CLI and agent surfaces Yes: Example4 runs a public MCP server at mcp.example4.ai that listed 16 tools to a client with no credentials on 4 November 2026. Examples: xmp4\_callees, xmp4\_callers, xmp4\_deps. It speaks streamable-http, protocol 2025-03-26. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Example4 (registry title: xmp4: Semantic code knowledge for your stack) | | --- | --- | | Domain | example4.ai | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for example4.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.example4.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | xmp4 1.2.7 | | Capabilities | tools | | Tools | 16 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 554 ms over 1 attempt | ### Tools listed 16 tools - xmp4\_callees - xmp4\_callers - xmp4\_deps - xmp4\_grep - xmp4\_guide - xmp4\_hierarchy - xmp4\_info - xmp4\_outline - xmp4\_projects - xmp4\_search - xmp4\_server - xmp4\_source - xmp4\_symbol\_at - xmp4\_tests\_for - xmp4\_usages - xmp4\_view ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:23Z https://mcp.example4.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 907 ms - 20:02:51Z https://mcp.example4.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 554 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.example4.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Example4. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.example4/xmp4 | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/example4-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=example4), read 4 November 2026 - [Example4 website](https://example4.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Explorium MCP server | Agent MCP Directory" description: "Explorium: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/explorium-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Explorium MCP server | Agent MCP Directory > Explorium: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/explorium-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Explorium: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Explorium at vibeprospecting.explorium.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Explorium (registry title: Vibe Prospecting) | | --- | --- | | Domain | explorium.ai | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 87, grade A; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for explorium.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://vibeprospecting.explorium.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 238 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:23Z https://vibeprospecting.explorium.ai/mcp sent initialize result auth-required (HTTP 401) 273 ms - 20:02:51Z https://vibeprospecting.explorium.ai/mcp sent initialize result auth-required (HTTP 401) 238 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token" | | Authorization server metadata | vibeprospecting.explorium.ai | | Registration endpoint | https://vibeprospecting.explorium.ai/register | ### The sign-in route, step by step 1. Request `https://vibeprospecting.explorium.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://vibeprospecting.explorium.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Explorium. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.explorium/mcp-explorium | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/explorium-ai/index.md) ## Sources - [Ora score page for explorium.ai](https://ora.ai/score/explorium.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=explorium), read 4 November 2026 - [Explorium website](https://explorium.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Expo MCP server | Agent MCP Directory" description: "Expo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/expo-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Expo MCP server | Agent MCP Directory > Expo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/expo-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Expo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Expo at mcp.expo.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Expo | | --- | --- | | Domain | expo.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 6,150 on the list of 4 November 2026 | | Ora score | 66, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for expo.dev, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.expo.dev/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 110 ms over 1 attempt | | Documentation | docs.expo.dev | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:09Z https://mcp.expo.dev/mcp sent initialize result auth-required (HTTP 401) 139 ms - 20:01:48Z https://mcp.expo.dev/mcp sent initialize result auth-required (HTTP 401) 110 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.expo.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.expo.dev | | Authorization server metadata | mcp.expo.dev | | Registration endpoint | https://mcp.expo.dev/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.expo.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.expo.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.expo.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | eas-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 27.4.1 | | Last publish | 4 November 2026 | | Command names | eas | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/expo-dev/index.md) ## Sources - [Expo MCP documentation](https://docs.expo.dev/eas/ai/mcp/), read 4 November 2026 - [Ora score page for expo.dev](https://ora.ai/score/expo.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Expo website](https://expo.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Extend MCP server | Agent MCP Directory" description: "Extend: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/extend-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Extend MCP server | Agent MCP Directory > Extend: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/extend-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Extend: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Extend at mcp.extend.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Extend (registry title: extend.ai) | | --- | --- | | Domain | extend.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 90, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for extend.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.extend.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,956 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:25Z https://mcp.extend.ai/mcp sent initialize result auth-required (HTTP 401) 2610 ms - 20:02:53Z https://mcp.extend.ai/mcp sent initialize result auth-required (HTTP 401) 1956 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authorization required", resource_metadata="https://mcp.extend.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.extend.ai | | Authorization server metadata | id.extend.ai | | Registration endpoint | https://id.extend.ai/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.extend.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.extend.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://id.extend.ai/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Extend. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: docs.extend.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.extend/extend | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/extend-ai/index.md) ## Sources - [Ora score page for extend.ai](https://ora.ai/score/extend.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Extend was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.extend%2Fextend), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=extend), read 4 November 2026 - [Extend website](https://extend.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FairValid MCP server | Agent MCP Directory" description: "FairValid: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/fairvalid-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FairValid MCP server | Agent MCP Directory > FairValid: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/fairvalid-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FairValid: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for FairValid at mcp.fairvalid.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | FairValid | | --- | --- | | Domain | fairvalid.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for fairvalid.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.fairvalid.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 979 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:24Z https://mcp.fairvalid.com/mcp sent initialize result auth-required (HTTP 401) 1374 ms - 20:02:52Z https://mcp.fairvalid.com/mcp sent initialize result auth-required (HTTP 401) 979 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="FairValid MCP", resource_metadata="https://mcp.fairvalid.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="Authenticate with a valid token granting the required permission." | | Protected resource metadata | mcp.fairvalid.com | | Authorization server metadata | fairvalid.com | | Registration endpoint | https://fairvalid.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.fairvalid.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.fairvalid.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://fairvalid.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FairValid. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fairvalid-com/index.md) ## Sources - [FairValid website](https://fairvalid.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fastero MCP server | Agent MCP Directory" description: "Fastero: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/fastero-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fastero MCP server | Agent MCP Directory > Fastero: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/fastero-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fastero: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Fastero at api.fastero.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Fastero | | --- | --- | | Domain | fastero.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for fastero.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.fastero.com/api/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,077 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:24Z https://api.fastero.com/api/v1/mcp sent initialize result auth-required (HTTP 401) 1397 ms - 20:02:52Z https://api.fastero.com/api/v1/mcp sent initialize result auth-required (HTTP 401) 1077 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.fastero.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.fastero.com | | Authorization server metadata | api.fastero.com | | Registration endpoint | https://api.fastero.com/api/v1/oauth/register | ### The sign-in route, step by step 1. Request `https://api.fastero.com/api/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.fastero.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.fastero.com/api/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Fastero. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.fastero/fastero | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fastero-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fastero), read 4 November 2026 - [Fastero website](https://fastero.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FastJVM MCP server | Agent MCP Directory" description: "Does FastJVM have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fastjvm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FastJVM MCP server | Agent MCP Directory > Does FastJVM have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/fastjvm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FastJVM: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for FastJVM (fastjvm.com), so the connector had nothing to connect to. Ora's cached score for fastjvm.com is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | FastJVM (registry title: fastjvm.com) | | --- | --- | | Domain | fastjvm.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fastjvm.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for FastJVM. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for fastjvm.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for FastJVM. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fastjvm-com/index.md) ## Sources - [Ora score page for fastjvm.com](https://ora.ai/score/fastjvm.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/leaderboard) - [Where FastJVM was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [FastJVM website](https://fastjvm.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fastly MCP server | Agent MCP Directory" description: "Does Fastly have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fastly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fastly MCP server | Agent MCP Directory > Does Fastly have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/fastly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fastly: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Fastly (fastly.com), so the connector had nothing to connect to. Ora's cached score for fastly.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Fastly | | --- | --- | | Domain | fastly.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 6,999 on the list of 4 November 2026 | | Ora score | 70, grade B; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for fastly.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Fastly. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for fastly.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Fastly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fastly-com/index.md) ## Sources - [Ora score page for fastly.com](https://ora.ai/score/fastly.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/score) - [Where Fastly was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Fastly website](https://fastly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fastmail MCP server | Agent MCP Directory" description: "Does Fastmail have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fastmail-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fastmail MCP server | Agent MCP Directory > Does Fastmail have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/fastmail-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fastmail: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Fastmail (fastmail.com), so the connector had nothing to connect to. Ora's cached score for fastmail.com is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Fastmail (registry title: fastmail.com) | | --- | --- | | Domain | fastmail.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fastmail.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Fastmail. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for fastmail.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Fastmail. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fastmail-com/index.md) ## Sources - [Ora score page for fastmail.com](https://ora.ai/score/fastmail.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Fastmail was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Fastmail website](https://fastmail.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fastshot MCP server | Agent MCP Directory" description: "Does Fastshot have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fastshot-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fastshot MCP server | Agent MCP Directory > Does Fastshot have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/fastshot-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fastshot: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Fastshot (fastshot.ai), so the connector had nothing to connect to. Ora's cached score for fastshot.ai is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Fastshot (registry title: fastshot.ai) | | --- | --- | | Domain | fastshot.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fastshot.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Fastshot. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for fastshot.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Fastshot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fastshot-ai/index.md) ## Sources - [Ora score page for fastshot.ai](https://ora.ai/score/fastshot.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Fastshot was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Fastshot website](https://fastshot.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fathom MCP server | Agent MCP Directory" description: "Fathom: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fathom-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fathom MCP server | Agent MCP Directory > Fathom: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/fathom-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fathom: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Fathom at api.fathom.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Fathom | | --- | --- | | Domain | fathom.ai | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 61, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fathom.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.fathom.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 660 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:25Z https://api.fathom.ai/mcp sent initialize result auth-required (HTTP 401) 573 ms - 20:02:53Z https://api.fathom.ai/mcp sent initialize result auth-required (HTTP 401) 660 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.fathom.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.fathom.ai | | Authorization server metadata | api.fathom.ai | | Registration endpoint | https://api.fathom.ai/mcp/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.fathom.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.fathom.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.fathom.ai/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Fathom. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.fathom.api/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fathom-ai/index.md) ## Sources - [Ora score page for fathom.ai](https://ora.ai/score/fathom.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where Fathom was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fathom), read 4 November 2026 - [Fathom website](https://fathom.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Faxette MCP server | Agent MCP Directory" description: "Faxette has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/faxette-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Faxette MCP server | Agent MCP Directory > Faxette has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/faxette-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Faxette: MCP server, CLI and agent surfaces Yes: Faxette runs a public MCP server at mcp.faxette.com that listed 15 tools to a client with no credentials on 4 November 2026. Examples: open\_fax\_review, get\_fax\_review, prepare\_fax\_upload. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Faxette | | --- | --- | | Domain | faxette.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for faxette.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.faxette.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | faxette 0.5.0 | | Capabilities | resources, tools, prompts | | Tools | 15 | | Resources | 1 | | Prompts | 2 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,815 ms over 1 attempt | ### Tools listed 15 tools - open\_fax\_review - get\_fax\_review - prepare\_fax\_upload - update\_fax\_review - get\_capabilities - lookup\_fax\_number - get\_fax\_report - resend\_fax - create\_document - create\_fax - get\_fax\_status - get\_account - get\_faxes - get\_fax - send\_fax ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:26Z https://mcp.faxette.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1615 ms - 20:02:54Z https://mcp.faxette.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1815 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.faxette.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Faxette. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.faxette/faxette, com.faxette/faxette-eu | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/faxette-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=faxette), read 4 November 2026 - [Faxette website](https://faxette.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Faxforagents MCP server | Agent MCP Directory" description: "Faxforagents has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/faxforagents-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Faxforagents MCP server | Agent MCP Directory > Faxforagents has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/faxforagents-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Faxforagents: MCP server, CLI and agent surfaces Yes: Faxforagents runs a public MCP server at mcp.faxforagents.com that listed 15 tools to a client with no credentials on 4 November 2026. Examples: get\_guide, get\_fax\_capabilities, prepare\_fax. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Faxforagents | | --- | --- | | Domain | faxforagents.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for faxforagents.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.faxforagents.com/mcp/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | faxforagents 1.8.2 | | Capabilities | prompts, resources, tools | | Tools | 15 | | Resources | 10 | | Prompts | 2 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 777 ms over 1 attempt | ### Tools listed 15 tools - get\_guide - get\_fax\_capabilities - prepare\_fax - get\_fax\_document - quote\_fax - send\_approved\_fax - get\_fax\_status - list\_faxes - get\_fax\_balance - cancel\_fax - request\_human\_review - get\_review\_status - list\_inbox - read\_inbound\_fax - extract\_fax\_data ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:25Z https://mcp.faxforagents.com/mcp/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 714 ms - 20:02:53Z https://mcp.faxforagents.com/mcp/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 777 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.faxforagents.com/mcp/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Faxforagents. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/faxforagents-com/index.md) ## Sources - [Faxforagents website](https://faxforagents.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ferryhopper MCP server | Agent MCP Directory" description: "Ferryhopper has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ferryhopper-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ferryhopper MCP server | Agent MCP Directory > Ferryhopper has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ferryhopper-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ferryhopper: MCP server, CLI and agent surfaces Yes: Ferryhopper runs a public MCP server at mcp.ferryhopper.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: get\_ports, get\_disruptions, get\_direct\_connections\_for\_ports. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Ferryhopper | | --- | --- | | Domain | ferryhopper.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for ferryhopper.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.ferryhopper.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | FerryhopperMCP 1.0.0 | | Capabilities | tools, resources | | Tools | 6 | | Resources | 4 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 678 ms over 1 attempt | ### Tools listed 6 tools - get\_ports - get\_disruptions - get\_direct\_connections\_for\_ports - search\_trips - search\_ferry\_trips - trip\_details ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:26Z https://mcp.ferryhopper.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 772 ms - 20:02:53Z https://mcp.ferryhopper.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 678 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.ferryhopper.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ferryhopper. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ferryhopper-com/index.md) ## Sources - [Where Ferryhopper was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Ferryhopper website](https://ferryhopper.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fiber AI MCP server | Agent MCP Directory" description: "Fiber AI has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fiber-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fiber AI MCP server | Agent MCP Directory > Fiber AI has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/fiber-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fiber AI: MCP server, CLI and agent surfaces Yes: Fiber AI runs a public MCP server at mcp.fiber.ai that listed 5 tools to a client with no credentials on 4 November 2026. Examples: search\_endpoints, list\_tag\_packs, list\_all\_endpoints. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for fiber.ai is 35, grade D, read on 5 November 2026. ## Fact sheet | Company | Fiber AI | | --- | --- | | Domain | fiber.ai | | Category | HR & Recruiting (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 35, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for fiber.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.fiber.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | fiber-core 3.2.0 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 5 | | Resources | 3 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,634 ms over 1 attempt | ### Tools listed 5 tools - search\_endpoints - list\_tag\_packs - list\_all\_endpoints - get\_endpoint\_details\_full - call\_operation ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:27Z https://mcp.fiber.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1768 ms - 20:02:55Z https://mcp.fiber.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1634 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.fiber.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Fiber AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.fiber/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fiber-ai/index.md) ## Sources - [Ora score page for fiber.ai](https://ora.ai/score/fiber.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/score) - [Where Fiber AI was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.fiber%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fiber), read 4 November 2026 - [Fiber AI website](https://fiber.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fiddler AI MCP server | Agent MCP Directory" description: "Does Fiddler AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fiddler-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fiddler AI MCP server | Agent MCP Directory > Does Fiddler AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/fiddler-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fiddler AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Fiddler AI (fiddler.ai), so the connector had nothing to connect to. Ora's cached score for fiddler.ai is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Fiddler AI | | --- | --- | | Domain | fiddler.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fiddler.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Fiddler AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for fiddler.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Fiddler AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fiddler-ai/index.md) ## Sources - [Ora score page for fiddler.ai](https://ora.ai/score/fiddler.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 September 2026, read from GET /api/leaderboard) - [Where Fiddler AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Fiddler AI website](https://fiddler.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Figma MCP server | Agent MCP Directory" description: "Figma: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/figma-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Figma MCP server | Agent MCP Directory > Figma: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/figma-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Figma: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Figma at mcp.figma.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Figma | | --- | --- | | Domain | figma.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 910 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for figma.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.figma.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,171 ms over 1 attempt | | Documentation | developers.figma.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:56Z https://mcp.figma.com/mcp sent initialize result auth-required (HTTP 401) 1065 ms - 20:01:32Z https://mcp.figma.com/mcp sent initialize result auth-required (HTTP 401) 1171 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.figma.com/.well-known/oauth-protected-resource",scope="mcp:connect",authorization_uri="https://api.figma.com/.well-known/oauth-authorization-server" | | Protected resource metadata | mcp.figma.com | | Authorization server metadata | api.figma.com | | Registration endpoint | https://api.figma.com/v1/oauth/mcp/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.figma.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.figma.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.figma.com/v1/oauth/mcp/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Figma. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: figma.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.figma.mcp/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/figma-com/index.md) ## Sources - [Figma MCP documentation](https://developers.figma.com/docs/figma-mcp-server/), read 4 November 2026 - [Ora score page for figma.com](https://ora.ai/score/figma.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=figma), read 4 November 2026 - [Figma website](https://figma.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FinancialFilings MCP server | Agent MCP Directory" description: "FinancialFilings: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/financialfilings-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FinancialFilings MCP server | Agent MCP Directory > FinancialFilings: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/financialfilings-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FinancialFilings: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for FinancialFilings at mcp.financialfilings.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | FinancialFilings | | --- | --- | | Domain | financialfilings.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for financialfilings.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.financialfilings.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 571 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:26Z https://mcp.financialfilings.com/mcp sent initialize result auth-required (HTTP 401) 593 ms - 20:02:54Z https://mcp.financialfilings.com/mcp sent initialize result auth-required (HTTP 401) 571 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://mcp.financialfilings.com/.well-known/oauth-protected-resource/mcp", scope="openid email profile" | | Protected resource metadata | mcp.financialfilings.com | | Authorization server metadata | mcp.financialfilings.com | | Registration endpoint | https://mcp.financialfilings.com/register | ### The sign-in route, step by step 1. Request `https://mcp.financialfilings.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.financialfilings.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.financialfilings.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FinancialFilings. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.financialfilings/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/financialfilings-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=financialfilings), read 4 November 2026 - [FinancialFilings website](https://financialfilings.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Findabis MCP server | Agent MCP Directory" description: "Findabis has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/findabis-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Findabis MCP server | Agent MCP Directory > Findabis has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/findabis-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Findabis: MCP server, CLI and agent surfaces Yes: Findabis runs a public MCP server at findabis.com that listed 10 tools to a client with no credentials on 4 November 2026. Examples: find\_clinics, find\_pharmacies, find\_products. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Findabis | | --- | --- | | Domain | findabis.com | | Category | Healthcare (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for findabis.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://findabis.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | findabis 0.5.0 | | Capabilities | tools, resources, prompts | | Tools | 10 | | Resources | 3 | | Prompts | 3 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 771 ms over 1 attempt | ### Tools listed 10 tools - find\_clinics - find\_pharmacies - find\_products - get\_product - find\_strains - find\_brands - get\_listing - compare\_providers - search\_findabis - get\_directory\_facts ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:27Z https://findabis.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 895 ms - 20:02:54Z https://findabis.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 771 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://findabis.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Findabis. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.findabis/findabis | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/findabis-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=findabis), read 4 November 2026 - [Findabis website](https://findabis.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Find-A-Domain MCP server | Agent MCP Directory" description: "Find-A-Domain has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/findadomain-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Find-A-Domain MCP server | Agent MCP Directory > Find-A-Domain has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/findadomain-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Find-A-Domain: MCP server, CLI and agent surfaces Yes: Find-A-Domain runs a public MCP server at api.findadomain.dev that listed 2 tools to a client with no credentials on 4 November 2026. Examples: check\_domain, list\_tlds. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Find-A-Domain | | --- | --- | | Domain | findadomain.dev | | Category | Productivity (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for findadomain.dev when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.findadomain.dev/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | findadomain-api 1.1.0 | | Capabilities | logging, tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 487 ms over 1 attempt | ### Tools listed 2 tools - check\_domain - list\_tlds ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:27Z https://api.findadomain.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 832 ms - 20:02:54Z https://api.findadomain.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 487 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://api.findadomain.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Find-A-Domain. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/findadomain-dev/index.md) ## Sources - [Where Find-A-Domain was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Find-A-Domain website](https://findadomain.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Firebase MCP server | Agent MCP Directory" description: "Does Firebase have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/firebase-google-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Firebase MCP server | Agent MCP Directory > Does Firebase have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/firebase-google-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Firebase: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Firebase (firebase.google.com), so the connector had nothing to connect to. A CLI is on record: firebase-tools on npm. Ora's cached score for firebase.google.com is 56, grade C, read on 5 November 2026. ## Fact sheet | Company | Firebase | | --- | --- | | Domain | firebase.google.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for firebase.google.com, a vendor-published score) | | Company found through | the vendor's own documentation | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Firebase. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for firebase.google.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | firebase-tools on npm (page) | | --- | --- | | Exists | yes | | Latest version | 15.35.0 | | Last publish | 4 November 2026 | | Command names | firebase | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/firebase-google-com/index.md) ## Sources - [Ora score page for firebase.google.com](https://ora.ai/score/firebase.google.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/score) - [Where Firebase was found](https://firebase.google.com/docs/cli/mcp-server), read 4 November 2026 - [Firebase website](https://firebase.google.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fireflies.ai MCP server | Agent MCP Directory" description: "Fireflies.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/fireflies-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fireflies.ai MCP server | Agent MCP Directory > Fireflies.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/fireflies-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fireflies.ai: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Fireflies.ai at api.fireflies.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Fireflies.ai | | --- | --- | | Domain | fireflies.ai | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 80, grade B; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fireflies.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.fireflies.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 940 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:27Z https://api.fireflies.ai/mcp sent initialize result auth-required (HTTP 401) 864 ms - 20:02:55Z https://api.fireflies.ai/mcp sent initialize result auth-required (HTTP 401) 940 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="email profile", resource_metadata="https://api.fireflies.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.fireflies.ai | | Authorization server metadata | api.fireflies.ai | | Registration endpoint | https://api.fireflies.ai/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.fireflies.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.fireflies.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.fireflies.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Fireflies.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.fireflies/fireflies | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fireflies-ai/index.md) ## Sources - [Ora score page for fireflies.ai](https://ora.ai/score/fireflies.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where Fireflies.ai was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fireflies), read 4 November 2026 - [Fireflies.ai website](https://fireflies.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FireHydrant MCP server | Agent MCP Directory" description: "Does FireHydrant have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/firehydrant-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FireHydrant MCP server | Agent MCP Directory > Does FireHydrant have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/firehydrant-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FireHydrant: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for FireHydrant (firehydrant.com), so the connector had nothing to connect to. Ora's cached score for firehydrant.com is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | FireHydrant (registry title: firehydrant.com) | | --- | --- | | Domain | firehydrant.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for firehydrant.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for FireHydrant. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for firehydrant.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for FireHydrant. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/firehydrant-com/index.md) ## Sources - [Ora score page for firehydrant.com](https://ora.ai/score/firehydrant.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where FireHydrant was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [FireHydrant website](https://firehydrant.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Firmafakta MCP server | Agent MCP Directory" description: "Firmafakta: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/firmafakta-se site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Firmafakta MCP server | Agent MCP Directory > Firmafakta: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/firmafakta-se Site: Agent MCP Directory Last reviewed: 2026-11-05 # Firmafakta: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Firmafakta at mcp.firmafakta.se answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Firmafakta | | --- | --- | | Domain | firmafakta.se | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for firmafakta.se when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.firmafakta.se | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 841 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:28Z https://mcp.firmafakta.se sent initialize result auth-required (HTTP 401) 1054 ms - 20:02:55Z https://mcp.firmafakta.se sent initialize result auth-required (HTTP 401) 841 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.firmafakta.se/.well-known/oauth-protected-resource", scope="segmentera" | | Protected resource metadata | mcp.firmafakta.se | | Authorization server metadata | firmafakta.se | | Registration endpoint | https://firmafakta.se/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.firmafakta.se` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.firmafakta.se/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://firmafakta.se/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Firmafakta. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/firmafakta-se/index.md) ## Sources - [Firmafakta website](https://firmafakta.se), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Flagsmith MCP server | Agent MCP Directory" description: "Flagsmith: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/flagsmith-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Flagsmith MCP server | Agent MCP Directory > Flagsmith: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/flagsmith-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Flagsmith: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Flagsmith; the connector's guess at mcp.flagsmith.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Flagsmith (registry title: flagsmith.com) | | --- | --- | | Domain | flagsmith.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 47, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for flagsmith.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.flagsmith.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 723 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:28Z https://mcp.flagsmith.com/mcp sent initialize result auth-required (HTTP 401) 766 ms - 20:02:55Z https://mcp.flagsmith.com/mcp sent initialize result auth-required (HTTP 401) 723 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.flagsmith.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.flagsmith.com | | Authorization server metadata | api.flagsmith.com | | Registration endpoint | https://api.flagsmith.com/o/register/ | ### The sign-in route, step by step 1. Request `https://mcp.flagsmith.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.flagsmith.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.flagsmith.com/o/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Flagsmith. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flagsmith-com/index.md) ## Sources - [Ora score page for flagsmith.com](https://ora.ai/score/flagsmith.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Flagsmith was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Flagsmith website](https://flagsmith.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FlickDirect MCP server | Agent MCP Directory" description: "FlickDirect has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/flickdirect-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FlickDirect MCP server | Agent MCP Directory > FlickDirect has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/flickdirect-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FlickDirect: MCP server, CLI and agent surfaces Yes: FlickDirect runs a public MCP server at connect.flickdirect.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: search\_fdmd, get\_fdmd\_movie. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | FlickDirect (registry title: FlickDirect Connect: Movie MCP Server) | | --- | --- | | Domain | flickdirect.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for flickdirect.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://connect.flickdirect.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | FlickDirect Connect 1.5.1.0 | | Capabilities | logging, tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,781 ms over 2 attempts | | Result | initialize error: Protocol version '2026-07-28' is not available through the initialize handshake. | ### Tools listed 2 tools - search\_fdmd - get\_fdmd\_movie ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:30Z https://connect.flickdirect.com/mcp sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 2004 ms - 20:02:57Z https://connect.flickdirect.com/mcp sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 1781 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://connect.flickdirect.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FlickDirect. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.flickdirect.connect/flickdirect-connect | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flickdirect-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=flickdirect), read 4 November 2026 - [FlickDirect website](https://flickdirect.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Flightcontrol MCP server | Agent MCP Directory" description: "Does Flightcontrol have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/flightcontrol-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Flightcontrol MCP server | Agent MCP Directory > Does Flightcontrol have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/flightcontrol-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Flightcontrol: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Flightcontrol (flightcontrol.dev), so the connector had nothing to connect to. Ora's cached score for flightcontrol.dev is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Flightcontrol (registry title: flightcontrol.dev) | | --- | --- | | Domain | flightcontrol.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for flightcontrol.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Flightcontrol. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for flightcontrol.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Flightcontrol. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flightcontrol-dev/index.md) ## Sources - [Ora score page for flightcontrol.dev](https://ora.ai/score/flightcontrol.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Flightcontrol was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Flightcontrol website](https://flightcontrol.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Flightpowers MCP server | Agent MCP Directory" description: "Flightpowers has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/flightpowers-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Flightpowers MCP server | Agent MCP Directory > Flightpowers has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/flightpowers-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Flightpowers: MCP server, CLI and agent surfaces Yes: Flightpowers runs a public MCP server at hotels.flightpowers.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: search\_hotels, find\_hotel\_by\_name, compare\_hotel\_rates. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Flightpowers (registry title: Google Flights Search (Real-Time Fares)) | | --- | --- | | Domain | flightpowers.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for flightpowers.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://hotels.flightpowers.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | booking-hotels-mcp 1.0.0 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 4 | | Resources | 0 | | Prompts | 3 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,244 ms over 1 attempt | ### Tools listed 4 tools - search\_hotels - find\_hotel\_by\_name - compare\_hotel\_rates - search\_airbnb ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:30Z https://hotels.flightpowers.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1546 ms - 20:02:57Z https://hotels.flightpowers.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1244 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://hotels.flightpowers.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Flightpowers. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: flightpowers.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.flightpowers/booking, com.flightpowers/google-flights | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flightpowers-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=flightpowers), read 4 November 2026 - [Flightpowers website](https://flightpowers.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FlightQueue MCP server | Agent MCP Directory" description: "FlightQueue: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security." canonical: https://agentmcpdirectory.com/directory/flightqueue-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FlightQueue MCP server | Agent MCP Directory > FlightQueue: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security. Source: https://agentmcpdirectory.com/directory/flightqueue-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FlightQueue: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for FlightQueue at mcp.flightqueue.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | FlightQueue | | --- | --- | | Domain | flightqueue.com | | Category | Security (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for flightqueue.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.flightqueue.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 195 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:29Z https://mcp.flightqueue.com/mcp sent initialize result auth-required (HTTP 401) 537 ms - 20:02:56Z https://mcp.flightqueue.com/mcp sent initialize result auth-required (HTTP 401) 195 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.flightqueue.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token", scope="read" | | Protected resource metadata | mcp.flightqueue.com | | Authorization server metadata | mcp.flightqueue.com | | Registration endpoint | https://mcp.flightqueue.com/register | ### The sign-in route, step by step 1. Request `https://mcp.flightqueue.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.flightqueue.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.flightqueue.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FlightQueue. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.flightqueue/flightqueue | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flightqueue-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=flightqueue), read 4 November 2026 - [FlightQueue website](https://flightqueue.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FlightSeatMap MCP server | Agent MCP Directory" description: "FlightSeatMap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/flightseatmap-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FlightSeatMap MCP server | Agent MCP Directory > FlightSeatMap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/flightseatmap-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FlightSeatMap: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for FlightSeatMap at mcp.flightseatmap.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | FlightSeatMap | | --- | --- | | Domain | flightseatmap.com | | Category | Travel & Hospitality (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for flightseatmap.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.flightseatmap.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,252 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:30Z https://mcp.flightseatmap.com/mcp sent initialize result auth-required (HTTP 401) 1407 ms - 20:02:57Z https://mcp.flightseatmap.com/mcp sent initialize result auth-required (HTTP 401) 1252 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Flight Seatmap", resource_metadata="https://mcp.flightseatmap.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.flightseatmap.com | | Authorization server metadata | mcp.flightseatmap.com | | Registration endpoint | https://mcp.flightseatmap.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.flightseatmap.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.flightseatmap.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.flightseatmap.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FlightSeatMap. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.flightseatmap/flightseatmap | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flightseatmap-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=flightseatmap), read 4 November 2026 - [FlightSeatMap website](https://flightseatmap.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Floot MCP server | Agent MCP Directory" description: "Floot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/floot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Floot MCP server | Agent MCP Directory > Floot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/floot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Floot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Floot at mcp.floot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Floot (registry title: floot.com) | | --- | --- | | Domain | floot.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 60, grade C; Ora scanned the domain on 20 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for floot.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.floot.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,495 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:30Z https://mcp.floot.com/mcp sent initialize result auth-required (HTTP 401) 1398 ms - 20:02:58Z https://mcp.floot.com/mcp sent initialize result auth-required (HTTP 401) 1495 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.floot.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.floot.com | | Authorization server metadata | mcp.floot.com | | Registration endpoint | https://mcp.floot.com/register | ### The sign-in route, step by step 1. Request `https://mcp.floot.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.floot.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.floot.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Floot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: floot.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.floot/floot | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/floot-com/index.md) ## Sources - [Ora score page for floot.com](https://ora.ai/score/floot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 August 2026, read from GET /api/leaderboard) - [Where Floot was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.floot%2Ffloot), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=floot), read 4 November 2026 - [Floot website](https://floot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FlowLeap MCP server | Agent MCP Directory" description: "FlowLeap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/flowleap-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FlowLeap MCP server | Agent MCP Directory > FlowLeap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/flowleap-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # FlowLeap: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for FlowLeap at api.flowleap.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | FlowLeap (registry title: FlowLeap Patent AI) | | --- | --- | | Domain | flowleap.co | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for flowleap.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.flowleap.co/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 756 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:30Z https://api.flowleap.co/mcp sent initialize result auth-required (HTTP 401) 1234 ms - 20:02:57Z https://api.flowleap.co/mcp sent initialize result auth-required (HTTP 401) 756 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="flowleap", resource_metadata="https://api.flowleap.co/.well-known/oauth-protected-resource/mcp", scope="patent-data" | | Protected resource metadata | api.flowleap.co | | Authorization server metadata | clerk.flowleap.co | | Registration endpoint | https://clerk.flowleap.co/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.flowleap.co/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.flowleap.co/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.flowleap.co/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FlowLeap. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.flowleap/flowleap | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flowleap-co/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=flowleap), read 4 November 2026 - [FlowLeap website](https://flowleap.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Flowra MCP server | Agent MCP Directory" description: "Flowra: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/flowra-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Flowra MCP server | Agent MCP Directory > Flowra: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/flowra-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Flowra: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Flowra at mcp.flowra.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Flowra | | --- | --- | | Domain | flowra.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for flowra.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.flowra.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 442 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:29Z https://mcp.flowra.dev/mcp sent initialize result auth-required (HTTP 401) 540 ms - 20:02:57Z https://mcp.flowra.dev/mcp sent initialize result auth-required (HTTP 401) 442 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Flowra MCP", resource_metadata="https://mcp.flowra.dev/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.flowra.dev | | Authorization server metadata | mcp.flowra.dev | | Registration endpoint | https://mcp.flowra.dev/register | ### The sign-in route, step by step 1. Request `https://mcp.flowra.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.flowra.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.flowra.dev/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Flowra. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flowra-dev/index.md) ## Sources - [Flowra website](https://flowra.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Flowtel MCP server | Agent MCP Directory" description: "Does Flowtel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/flowtel-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Flowtel MCP server | Agent MCP Directory > Does Flowtel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/flowtel-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Flowtel: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Flowtel (flowtel.ai), so the connector had nothing to connect to. Ora's cached score for flowtel.ai is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Flowtel (registry title: flowtel.ai) | | --- | --- | | Domain | flowtel.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 27 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for flowtel.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Flowtel. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for flowtel.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Flowtel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flowtel-ai/index.md) ## Sources - [Ora score page for flowtel.ai](https://ora.ai/score/flowtel.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 September 2026, read from GET /api/leaderboard) - [Where Flowtel was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Flowtel website](https://flowtel.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FlutterFlow MCP server | Agent MCP Directory" description: "Does FlutterFlow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/flutterflow-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FlutterFlow MCP server | Agent MCP Directory > Does FlutterFlow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/flutterflow-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # FlutterFlow: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for FlutterFlow (flutterflow.io), so the connector had nothing to connect to. Ora's cached score for flutterflow.io is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | FlutterFlow (registry title: flutterflow.io) | | --- | --- | | Domain | flutterflow.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for flutterflow.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for FlutterFlow. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for flutterflow.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for FlutterFlow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flutterflow-io/index.md) ## Sources - [Ora score page for flutterflow.io](https://ora.ai/score/flutterflow.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where FlutterFlow was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [FlutterFlow website](https://flutterflow.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Flux MCP server | Agent MCP Directory" description: "Does Flux have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/fluxcd-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Flux MCP server | Agent MCP Directory > Does Flux have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/fluxcd-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Flux: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Flux (fluxcd.io), so the connector had nothing to connect to. Ora's cached score for fluxcd.io is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Flux (registry title: fluxcd.io) | | --- | --- | | Domain | fluxcd.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fluxcd.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Flux. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for fluxcd.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Flux. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fluxcd-io/index.md) ## Sources - [Ora score page for fluxcd.io](https://ora.ai/score/fluxcd.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Flux was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Flux website](https://fluxcd.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fly MCP server | Agent MCP Directory" description: "Fly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fly-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fly MCP server | Agent MCP Directory > Fly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/fly-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Fly at mcp.fly.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Fly (registry title: Fly MCP) | | --- | --- | | Domain | fly.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 96, grade A+; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for fly.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.fly.io | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 620 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:31Z https://mcp.fly.io sent initialize result auth-required (HTTP 401) 737 ms - 20:02:58Z https://mcp.fly.io sent initialize result auth-required (HTTP 401) 620 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.fly.io/.well-known/oauth-protected-resource", scope="fly:apps:delete fly:certificates:read fly:context:read fly:machines:delete fly:machines:exec fly:machines:read fly:machines:sensitive:read fly:machines:write fly:mpg:read fly:mpg:write fly:network:read fly:organizations:read fly:read fly:secrets:delete fly:secrets:read fly:secrets:write fly:volumes:delete fly:volumes:read fly:volumes:write sprites:read sprites:write" | | Protected resource metadata | mcp.fly.io | | Authorization server metadata | fly.io | | Registration endpoint | https://fly.io/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.fly.io` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.fly.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://fly.io/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Fly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: fly.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.fly/fly-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fly-io/index.md) ## Sources - [Ora score page for fly.io](https://ora.ai/score/fly.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/leaderboard) - [Where Fly was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.fly%2Ffly-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fly), read 4 November 2026 - [Fly website](https://fly.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FlyBest MCP server | Agent MCP Directory" description: "FlyBest: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Travel & Hospitality." canonical: https://agentmcpdirectory.com/directory/flybest-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FlyBest MCP server | Agent MCP Directory > FlyBest: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Travel & Hospitality. Source: https://agentmcpdirectory.com/directory/flybest-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # FlyBest: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for FlyBest at ai.flybest.org answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | FlyBest (registry title: FlyBest Travel: Hotel Booking with Advisor Benefits) | | --- | --- | | Domain | flybest.org | | Category | Travel & Hospitality (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for flybest.org when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.flybest.org/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,471 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:32Z https://ai.flybest.org/mcp sent initialize result auth-required (HTTP 401) 1550 ms - 20:02:59Z https://ai.flybest.org/mcp sent initialize result auth-required (HTTP 401) 1471 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://ai.flybest.org/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | ai.flybest.org | | Authorization server metadata | ai.flybest.org | | Registration endpoint | https://ai.flybest.org/register | ### The sign-in route, step by step 1. Request `https://ai.flybest.org/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://ai.flybest.org/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://ai.flybest.org/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FlyBest. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/flybest-org/index.md) ## Sources - [FlyBest website](https://flybest.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Follore MCP server | Agent MCP Directory" description: "Follore: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/follore-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Follore MCP server | Agent MCP Directory > Follore: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/follore-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Follore: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Follore at follore.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Follore | | --- | --- | | Domain | follore.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for follore.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://follore.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 2,013 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:32Z https://follore.com/mcp sent initialize result auth-required (HTTP 401) 2176 ms - 20:02:59Z https://follore.com/mcp sent initialize result auth-required (HTTP 401) 2013 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://follore.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | follore.com | | Authorization server metadata | follore.com | | Registration endpoint | https://follore.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://follore.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://follore.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://follore.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Follore. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.follore/follore | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/follore-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=follore), read 4 November 2026 - [Follore website](https://follore.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Font Awesome MCP server | Agent MCP Directory" description: "Does Font Awesome have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fontawesome-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Font Awesome MCP server | Agent MCP Directory > Does Font Awesome have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/fontawesome-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Font Awesome: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Font Awesome (fontawesome.com), so the connector had nothing to connect to. Ora's cached score for fontawesome.com is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Font Awesome (registry title: fontawesome.com) | | --- | --- | | Domain | fontawesome.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 714 on the list of 4 November 2026 | | Ora score | 56, grade C; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for fontawesome.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Font Awesome. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for fontawesome.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Font Awesome. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fontawesome-com/index.md) ## Sources - [Ora score page for fontawesome.com](https://ora.ai/score/fontawesome.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/score) - [Where Font Awesome was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Font Awesome website](https://fontawesome.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Formasty MCP server | Agent MCP Directory" description: "Formasty: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security." canonical: https://agentmcpdirectory.com/directory/formasty-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Formasty MCP server | Agent MCP Directory > Formasty: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security. Source: https://agentmcpdirectory.com/directory/formasty-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Formasty: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Formasty at app.formasty.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Formasty | | --- | --- | | Domain | formasty.com | | Category | Security (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 70, grade B; Ora scanned the domain on 26 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for formasty.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.formasty.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 178 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:31Z https://app.formasty.com/api/mcp sent initialize result auth-required (HTTP 401) 702 ms - 20:02:58Z https://app.formasty.com/api/mcp sent initialize result auth-required (HTTP 401) 178 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.formasty.com/.well-known/oauth-protected-resource/api/mcp", scope="forms:read forms:create forms:update forms:delete forms:publish forms:steps:write forms:fields:write forms:logic:write forms:design:write submissions:read submissions:create submissions:update submissions:delete offline_access", error="invalid_token", error_description="Missing bearer token." | | Protected resource metadata | app.formasty.com | | Authorization server metadata | app.formasty.com | | Registration endpoint | https://app.formasty.com/oauth/register | ### The sign-in route, step by step 1. Request `https://app.formasty.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.formasty.com/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.formasty.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Formasty. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: formasty.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.formasty/form-builder | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/formasty-com/index.md) ## Sources - [Ora score page for formasty.com](https://ora.ai/score/formasty.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=formasty), read 4 November 2026 - [Formasty website](https://formasty.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Forter MCP server | Agent MCP Directory" description: "Forter has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/forter-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Forter MCP server | Agent MCP Directory > Forter has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/forter-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Forter: MCP server, CLI and agent surfaces Yes: Forter runs a public MCP server at www.forter.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: get\_fraud\_decision, evaluate\_login\_risk, evaluate\_signup\_risk. It speaks streamable-http, protocol 2025-03-26. Ora's cached score for forter.com is 92, grade A, read on 5 November 2026. ## Fact sheet | Company | Forter (registry title: forter.com) | | --- | --- | | Domain | forter.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 203 on the list of 4 November 2026 | | Ora score | 92, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for forter.com, a vendor-published score) | | Company found through | the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.forter.com/mcp | | --- | --- | | How it was found | listed in the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | forter-demo 1.0.0 | | Capabilities | tools, resources | | Tools | 5 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,374 ms over 1 attempt | ### Tools listed 5 tools - get\_fraud\_decision - evaluate\_login\_risk - evaluate\_signup\_risk - lookup\_dispute\_evidence - check\_agent\_trust ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:53Z https://www.forter.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1508 ms - 20:01:28Z https://www.forter.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1374 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.forter.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Forter. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.forter.com (JSON, via the shared crawl). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: forter.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: forter.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Found: forter.com/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: forter.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/forter-com/index.md) ## Sources - [Ora score page for forter.com](https://ora.ai/score/forter.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Forter was found](https://forter.com/.well-known/mcp.json), read 4 November 2026 - [Forter website](https://forter.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Frase MCP server | Agent MCP Directory" description: "Frase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/frase-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Frase MCP server | Agent MCP Directory > Frase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/frase-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Frase: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Frase at next.frase.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Frase (registry title: Frase SEO) | | --- | --- | | Domain | frase.io | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 89, grade A; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for frase.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://next.frase.io/api/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 721 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:32Z https://next.frase.io/api/mcp sent initialize result auth-required (HTTP 401) 1109 ms - 20:02:58Z https://next.frase.io/api/mcp sent initialize result auth-required (HTTP 401) 721 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://next.frase.io/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | next.frase.io | | Authorization server metadata | next.frase.io | | Registration endpoint | https://next.frase.io/api/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://next.frase.io/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://next.frase.io/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://next.frase.io/api/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Frase. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: next.frase.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: frase.io/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Found: frase.io/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: frase.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.frase/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/frase-io/index.md) ## Sources - [Ora score page for frase.io](https://ora.ai/score/frase.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where Frase was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.frase%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=frase), read 4 November 2026 - [Frase website](https://frase.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Freestyle MCP server | Agent MCP Directory" description: "Freestyle: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/freestyle-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Freestyle MCP server | Agent MCP Directory > Freestyle: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/freestyle-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Freestyle: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Freestyle; the connector's guess at mcp.freestyle.sh answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Freestyle (registry title: freestyle.sh) | | --- | --- | | Domain | freestyle.sh | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 68, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for freestyle.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.freestyle.sh/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,430 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:32Z https://mcp.freestyle.sh/mcp sent initialize result auth-required (HTTP 401) 1452 ms - 20:02:59Z https://mcp.freestyle.sh/mcp sent initialize result auth-required (HTTP 401) 1430 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.freestyle.sh/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.freestyle.sh | | Authorization server metadata | mcp.freestyle.sh | | Registration endpoint | https://mcp.freestyle.sh/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.freestyle.sh/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.freestyle.sh/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.freestyle.sh/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Freestyle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.freestyle.sh (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/freestyle-sh/index.md) ## Sources - [Ora score page for freestyle.sh](https://ora.ai/score/freestyle.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where Freestyle was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Freestyle website](https://freestyle.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Frihet MCP server | Agent MCP Directory" description: "Frihet: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/frihet-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Frihet MCP server | Agent MCP Directory > Frihet: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/frihet-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Frihet: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Frihet at mcp.frihet.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Frihet (registry title: Frihet ERP) | | --- | --- | | Domain | frihet.io | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for frihet.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.frihet.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 208 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:32Z https://mcp.frihet.io/mcp sent initialize result auth-required (HTTP 401) 774 ms - 20:02:58Z https://mcp.frihet.io/mcp sent initialize result auth-required (HTTP 401) 208 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.frihet.io/.well-known/oauth-protected-resource", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.frihet.io | | Authorization server metadata | mcp.frihet.io | | Registration endpoint | https://mcp.frihet.io/register | ### The sign-in route, step by step 1. Request `https://mcp.frihet.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.frihet.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.frihet.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Frihet. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.frihet.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.frihet/erp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/frihet-io/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=frihet), read 4 November 2026 - [Frihet website](https://frihet.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fuentio MCP server | Agent MCP Directory" description: "Fuentio has an open MCP server with 19 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fuentio-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fuentio MCP server | Agent MCP Directory > Fuentio has an open MCP server with 19 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/fuentio-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fuentio: MCP server, CLI and agent surfaces Yes: Fuentio runs a public MCP server at api.fuentio.com that listed 19 tools to a client with no credentials on 4 November 2026. Examples: lookup\_company, search\_companies, get\_company\_history. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Fuentio (registry title: Fuentio: UK, France & Spain company data from official registries) | | --- | --- | | Domain | fuentio.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for fuentio.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.fuentio.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | fuentio 0.1.0 | | Capabilities | completions, prompts, resources, tools | | Tools | 19 | | Resources | 4 | | Prompts | 4 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 898 ms over 1 attempt | ### Tools listed 19 tools - lookup\_company - search\_companies - get\_company\_history - verify\_company - get\_receipt - resolve\_company - explain\_match - what\_changed - screen\_company - check\_insolvency - check\_address - get\_graph - report\_issue - get\_evidence - check\_vat - watch\_company - review\_report - check\_supplier\_list - list\_coverage ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:33Z https://api.fuentio.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1161 ms - 20:02:59Z https://api.fuentio.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 898 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.fuentio.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Fuentio. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.fuentio/company-data | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fuentio-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fuentio), read 4 November 2026 - [Fuentio website](https://fuentio.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FullEnrich MCP server | Agent MCP Directory" description: "FullEnrich: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/fullenrich-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FullEnrich MCP server | Agent MCP Directory > FullEnrich: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/fullenrich-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # FullEnrich: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for FullEnrich at mcp.fullenrich.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | FullEnrich | | --- | --- | | Domain | fullenrich.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 61, grade C; Ora scanned the domain on 14 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for fullenrich.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.fullenrich.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 458 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:33Z https://mcp.fullenrich.com/mcp sent initialize result auth-required (HTTP 401) 682 ms - 20:02:59Z https://mcp.fullenrich.com/mcp sent initialize result auth-required (HTTP 401) 458 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.fullenrich.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.fullenrich.com | | Authorization server metadata | mcp.fullenrich.com | | Registration endpoint | https://mcp.fullenrich.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.fullenrich.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.fullenrich.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.fullenrich.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FullEnrich. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fullenrich-com/index.md) ## Sources - [Ora score page for fullenrich.com](https://ora.ai/score/fullenrich.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 September 2026, read from GET /api/score) - [FullEnrich website](https://fullenrich.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Fund Momentum MCP server | Agent MCP Directory" description: "Fund Momentum has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fundmomentum-vc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Fund Momentum MCP server | Agent MCP Directory > Fund Momentum has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/fundmomentum-vc Site: Agent MCP Directory Last reviewed: 2026-11-05 # Fund Momentum: MCP server, CLI and agent surfaces Yes: Fund Momentum runs a public MCP server at fundmomentum.vc that listed 11 tools to a client with no credentials on 4 November 2026. Examples: search\_funds, get\_fund, get\_changes. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Fund Momentum | | --- | --- | | Domain | fundmomentum.vc | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for fundmomentum.vc when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://fundmomentum.vc/_api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Fund Momentum 1.11.0 | | Capabilities | tools | | Tools | 11 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,940 ms over 1 attempt | ### Tools listed 11 tools - search\_funds - get\_fund - get\_changes - get\_fund\_signals - get\_gp\_profile - match\_startup - check\_lp\_coverage - search\_lps - get\_usage - send\_feedback - request\_warm\_intro ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:36Z https://fundmomentum.vc/\_api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2642 ms - 20:03:01Z https://fundmomentum.vc/\_api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1940 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://fundmomentum.vc/_api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Fund Momentum. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: fundmomentum.vc (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fundmomentum-vc/index.md) ## Sources - [Fund Momentum website](https://fundmomentum.vc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "FusionAuth MCP server | Agent MCP Directory" description: "FusionAuth has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fusionauth-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # FusionAuth MCP server | Agent MCP Directory > FusionAuth has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/fusionauth-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # FusionAuth: MCP server, CLI and agent surfaces Yes: FusionAuth runs a public MCP server at ai.fusionauth.dev that listed 2 tools to a client with no credentials on 4 November 2026. Examples: ask\_fusionauth\_question, search\_fusionauth\_sources. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for fusionauth.io is 71, grade B, read on 5 November 2026. ## Fact sheet | Company | FusionAuth (registry title: fusionauth.io) | | --- | --- | | Domain | fusionauth.io | | Category | Identity & Auth (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 71, grade B; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for fusionauth.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.fusionauth.dev/mcp/docs | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | fusionauth-docs-mcp 1.0.0 | | Capabilities | tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,754 ms over 1 attempt | ### Tools listed 2 tools - ask\_fusionauth\_question - search\_fusionauth\_sources ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:35Z https://ai.fusionauth.dev/mcp/docs sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2031 ms - 20:03:01Z https://ai.fusionauth.dev/mcp/docs sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1754 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://ai.fusionauth.dev/mcp/docs` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for FusionAuth. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.fusionauth/mcp-docs | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fusionauth-io/index.md) ## Sources - [Ora score page for fusionauth.io](https://ora.ai/score/fusionauth.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/score) - [Where FusionAuth was found](https://registry.modelcontextprotocol.io/v0/servers?search=io.fusionauth%2Fmcp-docs), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fusionauth), read 4 November 2026 - [FusionAuth website](https://fusionauth.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "fynk MCP server | Agent MCP Directory" description: "fynk: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/fynk-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # fynk MCP server | Agent MCP Directory > fynk: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/fynk-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # fynk: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for fynk at app.fynk.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | fynk (registry title: fynk MCP Server) | | --- | --- | | Domain | fynk.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 45, grade D; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for fynk.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.fynk.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,282 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:35Z https://app.fynk.com/mcp sent initialize result auth-required (HTTP 401) 1448 ms - 20:03:01Z https://app.fynk.com/mcp sent initialize result auth-required (HTTP 401) 1282 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://app.fynk.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | app.fynk.com | | Authorization server metadata | app.fynk.com | | Registration endpoint | https://app.fynk.com/oauth/register/mcp | ### The sign-in route, step by step 1. Request `https://app.fynk.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.fynk.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.fynk.com/oauth/register/mcp` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for fynk. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.fynk.app/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/fynk-com/index.md) ## Sources - [Ora score page for fynk.com](https://ora.ai/score/fynk.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=fynk), read 4 November 2026 - [fynk website](https://fynk.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Gaipagents MCP server | Agent MCP Directory" description: "Gaipagents has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gaipagents-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gaipagents MCP server | Agent MCP Directory > Gaipagents has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gaipagents-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gaipagents: MCP server, CLI and agent surfaces Yes: Gaipagents runs a public MCP server at www.gaipagents.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: gaip\_check, gaip\_watch, gaip\_diagnose. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Gaipagents (registry title: GAIP: evidence on AI agents before and after you call them) | | --- | --- | | Domain | gaipagents.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for gaipagents.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.gaipagents.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | gaip-broker 1.8.0 | | Capabilities | prompts, resources, tools | | Tools | 5 | | Resources | 4 | | Prompts | 5 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,209 ms over 1 attempt | ### Tools listed 5 tools - gaip\_check - gaip\_watch - gaip\_diagnose - gaip\_verify - second\_look\_check ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:36Z https://www.gaipagents.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2942 ms - 20:03:02Z https://www.gaipagents.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2209 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.gaipagents.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Gaipagents. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: gaipagents.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gaipagents-com/index.md) ## Sources - [Gaipagents website](https://gaipagents.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Galileo AI MCP server | Agent MCP Directory" description: "Does Galileo AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/galileo-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Galileo AI MCP server | Agent MCP Directory > Does Galileo AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/galileo-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Galileo AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Galileo AI (galileo.ai), so the connector had nothing to connect to. Ora's cached score for galileo.ai is 78, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Galileo AI | | --- | --- | | Domain | galileo.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 78, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for galileo.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Galileo AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for galileo.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Galileo AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/galileo-ai/index.md) ## Sources - [Ora score page for galileo.ai](https://ora.ai/score/galileo.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/leaderboard) - [Where Galileo AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Galileo AI website](https://galileo.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GameAnalytics MCP server | Agent MCP Directory" description: "GameAnalytics has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gameanalytics-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GameAnalytics MCP server | Agent MCP Directory > GameAnalytics has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gameanalytics-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GameAnalytics: MCP server, CLI and agent surfaces Yes: GameAnalytics runs a public MCP server at mcp.docs.gameanalytics.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: docs\_search, docs\_fetch. It speaks streamable-http, protocol 2026-07-28. Ora's cached score for gameanalytics.com is 80, grade B, read on 5 November 2026. ## Fact sheet | Company | GameAnalytics (registry title: GameAnalytics Documentation) | | --- | --- | | Domain | gameanalytics.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 2,485 on the list of 4 November 2026 | | Ora score | 80, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for gameanalytics.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.docs.gameanalytics.com | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | gameanalytics-docs 1.0.0 | | Capabilities | tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 323 ms over 1 attempt | ### Tools listed 2 tools - docs\_search - docs\_fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:58Z https://mcp.docs.gameanalytics.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 314 ms - 20:01:34Z https://mcp.docs.gameanalytics.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 323 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.docs.gameanalytics.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GameAnalytics. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.gameanalytics/analytics-docs | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gameanalytics-com/index.md) ## Sources - [Ora score page for gameanalytics.com](https://ora.ai/score/gameanalytics.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Where GameAnalytics was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.gameanalytics%2Fanalytics-docs), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=gameanalytics), read 4 November 2026 - [GameAnalytics website](https://gameanalytics.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Gamedev MCP server | Agent MCP Directory" description: "Gamedev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/gamedev-pl site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gamedev MCP server | Agent MCP Directory > Gamedev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/gamedev-pl Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gamedev: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Gamedev at www.gamedev.pl answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Gamedev (registry title: gamedev.pl) | | --- | --- | | Domain | gamedev.pl | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for gamedev.pl when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.gamedev.pl/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 427 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:34Z https://www.gamedev.pl/api/mcp sent initialize result auth-required (HTTP 401) 800 ms - 20:03:01Z https://www.gamedev.pl/api/mcp sent initialize result auth-required (HTTP 401) 427 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.gamedev.pl/.well-known/oauth-protected-resource" | | Protected resource metadata | www.gamedev.pl | | Authorization server metadata | www.gamedev.pl | | Registration endpoint | https://www.gamedev.pl/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://www.gamedev.pl/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.gamedev.pl/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.gamedev.pl/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Gamedev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gamedev-pl/index.md) ## Sources - [Gamedev website](https://gamedev.pl), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Gamma MCP server | Agent MCP Directory" description: "Gamma: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gamma-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gamma MCP server | Agent MCP Directory > Gamma: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gamma-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gamma: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Gamma at mcp.gamma.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Gamma | | --- | --- | | Domain | gamma.app | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,923 on the list of 4 November 2026 | | Ora score | 53, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for gamma.app, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.gamma.app/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 487 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:03Z https://mcp.gamma.app/mcp sent initialize result auth-required (HTTP 401) 435 ms - 20:01:39Z https://mcp.gamma.app/mcp sent initialize result auth-required (HTTP 401) 487 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.gamma.app/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.gamma.app | | Authorization server metadata | auth.gamma.app | | Registration endpoint | https://auth.gamma.app/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.gamma.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.gamma.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.gamma.app/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Gamma. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gamma-app/index.md) ## Sources - [Ora score page for gamma.app](https://ora.ai/score/gamma.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/score) - [Where Gamma was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Google Gemini MCP server | Agent MCP Directory" description: "Does Google Gemini have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gemini-google-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Google Gemini MCP server | Agent MCP Directory > Does Google Gemini have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/gemini-google-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Google Gemini: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Google Gemini (gemini.google.com), so the connector had nothing to connect to. A CLI is on record: @google/gemini-cli on npm. Ora's cached score for gemini.google.com is 43, grade D, read on 5 November 2026. ## Fact sheet | Company | Google Gemini | | --- | --- | | Domain | gemini.google.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for gemini.google.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Google Gemini. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for gemini.google.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | @google/gemini-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 0.66.0 | | Last publish | 27 October 2026 | | Command names | gemini | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gemini-google-com/index.md) ## Sources - [Ora score page for gemini.google.com](https://ora.ai/score/gemini.google.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Google Gemini was found](https://github.com/google-gemini/gemini-cli), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GenMagic MCP server | Agent MCP Directory" description: "GenMagic has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/genmagic-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GenMagic MCP server | Agent MCP Directory > GenMagic has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/genmagic-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # GenMagic: MCP server, CLI and agent surfaces Yes: GenMagic runs a public MCP server at genmagic.co that listed 7 tools to a client with no credentials on 4 November 2026. Examples: list\_models, generate\_text, generate\_image. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | GenMagic | | --- | --- | | Domain | genmagic.co | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for genmagic.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://genmagic.co/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | GenMagic 1.1.1 | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,292 ms over 1 attempt | ### Tools listed 7 tools - list\_models - generate\_text - generate\_image - generate\_speech - generate\_music - create\_video - get\_video ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:35Z https://genmagic.co/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1227 ms - 20:03:02Z https://genmagic.co/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1292 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://genmagic.co/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GenMagic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: genmagic.co (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/genmagic-co/index.md) ## Sources - [GenMagic website](https://genmagic.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Alai MCP server | Agent MCP Directory" description: "Alai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getalai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Alai MCP server | Agent MCP Directory > Alai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getalai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Alai: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Alai at slides-api.getalai.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Alai (registry title: getalai.com) | | --- | --- | | Domain | getalai.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 77, grade B; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getalai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://slides-api.getalai.com/mcp/ | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,611 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:37Z https://slides-api.getalai.com/mcp/ sent initialize result auth-required (HTTP 401) 2401 ms - 20:03:02Z https://slides-api.getalai.com/mcp/ sent initialize result auth-required (HTTP 401) 1611 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://alai-standalone-backend.getalai.com/.well-known/oauth-protected-resource" | | Protected resource metadata | alai-standalone-backend.getalai.com | | Authorization server metadata | eschotthjgljbxjerczn.supabase.co | | Registration endpoint | https://eschotthjgljbxjerczn.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://slides-api.getalai.com/mcp/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://alai-standalone-backend.getalai.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://eschotthjgljbxjerczn.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Alai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getalai/presentations | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getalai-com/index.md) ## Sources - [Ora score page for getalai.com](https://ora.ai/score/getalai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where Alai was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.getalai%2Fpresentations), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getalai), read 4 November 2026 - [Alai website](https://getalai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Getappniche MCP server | Agent MCP Directory" description: "Getappniche has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getappniche-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Getappniche MCP server | Agent MCP Directory > Getappniche has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getappniche-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Getappniche: MCP server, CLI and agent surfaces Yes: Getappniche runs a public MCP server at api.getappniche.com that listed 9 tools to a client with no credentials on 4 November 2026. Examples: search\_apps, get\_app\_detail, get\_app\_historicals. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Getappniche | | --- | --- | | Domain | getappniche.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for getappniche.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.getappniche.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | getappniche 0.1.0 | | Capabilities | tools | | Tools | 9 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,633 ms over 1 attempt | ### Tools listed 9 tools - search\_apps - get\_app\_detail - get\_app\_historicals - get\_app\_timeline - get\_keyword\_difficulty - batch\_keyword\_difficulty - get\_app\_reviews - get\_app\_organic\_videos - get\_supported\_countries ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:36Z https://api.getappniche.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1611 ms - 20:03:03Z https://api.getappniche.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1633 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.getappniche.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Getappniche. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getappniche/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getappniche-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getappniche), read 4 November 2026 - [Getappniche website](https://getappniche.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Carbon MCP server | Agent MCP Directory" description: "Carbon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getcarbon-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Carbon MCP server | Agent MCP Directory > Carbon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getcarbon-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Carbon: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Carbon at mcp.carbonvoice.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Carbon (registry title: Carbon Voice) | | --- | --- | | Domain | getcarbon.app | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for getcarbon.app when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.carbonvoice.app | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,443 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:36Z https://mcp.carbonvoice.app sent initialize result auth-required (HTTP 401) 1604 ms - 20:03:03Z https://mcp.carbonvoice.app sent initialize result auth-required (HTTP 401) 1443 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.carbonvoice.app/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.carbonvoice.app | | Authorization server metadata | api.carbonvoice.app | | Registration endpoint | https://api.carbonvoice.app/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.carbonvoice.app` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.carbonvoice.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.carbonvoice.app/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Carbon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getcarbon-app/index.md) ## Sources - [Where Carbon was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Carbon website](https://getcarbon.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Clera MCP server | Agent MCP Directory" description: "Clera: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getclera-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Clera MCP server | Agent MCP Directory > Clera: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getclera-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clera: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Clera at mcp.getclera.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Clera | | --- | --- | | Domain | getclera.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 39, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for getclera.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.getclera.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 968 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:36Z https://mcp.getclera.com sent initialize result auth-required (HTTP 401) 798 ms - 20:03:02Z https://mcp.getclera.com sent initialize result auth-required (HTTP 401) 968 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.getclera.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.getclera.com | | Authorization server metadata | clerk.getclera.com | | Registration endpoint | https://clerk.getclera.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.getclera.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.getclera.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.getclera.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Clera. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getclera/clera | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getclera-com/index.md) ## Sources - [Ora score page for getclera.com](https://ora.ai/score/getclera.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getclera), read 4 November 2026 - [Clera website](https://getclera.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Convoy MCP server | Agent MCP Directory" description: "Does Convoy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getconvoy-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Convoy MCP server | Agent MCP Directory > Does Convoy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/getconvoy-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Convoy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Convoy (getconvoy.io), so the connector had nothing to connect to. Ora's cached score for getconvoy.io is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Convoy (registry title: getconvoy.io) | | --- | --- | | Domain | getconvoy.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getconvoy.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Convoy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for getconvoy.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Convoy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getconvoy-io/index.md) ## Sources - [Ora score page for getconvoy.io](https://ora.ai/score/getconvoy.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/leaderboard) - [Where Convoy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Convoy website](https://getconvoy.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "CORE MCP server | Agent MCP Directory" description: "CORE has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/getcore-me site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # CORE MCP server | Agent MCP Directory > CORE has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/getcore-me Site: Agent MCP Directory Last reviewed: 2026-11-05 # CORE: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for CORE; the connector tried mcp.getcore.me as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). ## Fact sheet | Company | CORE (registry title: getcore.me) | | --- | --- | | Domain | getcore.me | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 55, grade C; Ora scanned the domain on 11 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getcore.me, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.getcore.me/mcp | | --- | --- | | How it was found | mcp.getcore.me was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 645 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:37Z https://mcp.getcore.me/mcp sent initialize result no-answer (HTTP 404) 660 ms - 20:03:03Z https://mcp.getcore.me/mcp sent initialize result no-answer (HTTP 404) 645 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.getcore.me/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for CORE. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getcore-me/index.md) ## Sources - [Ora score page for getcore.me](https://ora.ai/score/getcore.me?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 September 2026, read from GET /api/leaderboard) - [Where CORE was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [CORE website](https://getcore.me), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Getdecipher MCP server | Agent MCP Directory" description: "Does Getdecipher have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getdecipher-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Getdecipher MCP server | Agent MCP Directory > Does Getdecipher have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/getdecipher-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Getdecipher: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Getdecipher (getdecipher.com), so the connector had nothing to connect to. Ora's cached score for getdecipher.com is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Getdecipher (registry title: getdecipher.com) | | --- | --- | | Domain | getdecipher.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 15 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getdecipher.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Getdecipher. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for getdecipher.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Getdecipher. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getdecipher-com/index.md) ## Sources - [Ora score page for getdecipher.com](https://ora.ai/score/getdecipher.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 August 2026, read from GET /api/leaderboard) - [Where Getdecipher was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Dialer MCP server | Agent MCP Directory" description: "Dialer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getdialer-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Dialer MCP server | Agent MCP Directory > Dialer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getdialer-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Dialer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Dialer at getdialer.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Dialer | | --- | --- | | Domain | getdialer.app | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for getdialer.app when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://getdialer.app/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,143 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:38Z https://getdialer.app/mcp sent initialize result auth-required (HTTP 401) 1965 ms - 20:03:03Z https://getdialer.app/mcp sent initialize result auth-required (HTTP 401) 1143 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token" | | Authorization server metadata | getdialer.app | | Registration endpoint | https://getdialer.app/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://getdialer.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://getdialer.app/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Dialer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.getdialer/dialer | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getdialer-app/index.md) ## Sources - [Where Dialer was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getdialer), read 4 November 2026 - [Dialer website](https://getdialer.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Firmament MCP server | Agent MCP Directory" description: "Firmament has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/getfirmament-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Firmament MCP server | Agent MCP Directory > Firmament has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/getfirmament-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Firmament: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Firmament (mcp.getfirmament.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: ERR\_TLS\_CERT\_ALTNAME\_INVALID. The row is kept so the claim is visible and can be re-checked next edition. ## Fact sheet | Company | Firmament | | --- | --- | | Domain | getfirmament.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for getfirmament.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.getfirmament.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 244 ms over 1 attempt | | Result | ERR_TLS_CERT_ALTNAME_INVALID | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:37Z https://mcp.getfirmament.com/mcp sent initialize result no-answer 377 ms - 20:03:03Z https://mcp.getfirmament.com/mcp sent initialize result no-answer 244 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.getfirmament.com/mcp`. The connector could not tell what it wants: ERR\_TLS\_CERT\_ALTNAME\_INVALID. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Firmament. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getfirmament/firmament | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getfirmament-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getfirmament), read 4 November 2026 - [Firmament website](https://getfirmament.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Footgun MCP server | Agent MCP Directory" description: "Footgun has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getfootgun-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Footgun MCP server | Agent MCP Directory > Footgun has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getfootgun-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Footgun: MCP server, CLI and agent surfaces Yes: Footgun runs a public MCP server at getfootgun.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: lookup\_traps, search\_traps, file\_trap. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Footgun | | --- | --- | | Domain | getfootgun.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for getfootgun.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://getfootgun.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | footgun 0.1.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 930 ms over 1 attempt | ### Tools listed 4 tools - lookup\_traps - search\_traps - file\_trap - confirm\_trap ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:38Z https://getfootgun.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1080 ms - 20:03:03Z https://getfootgun.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 930 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://getfootgun.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Footgun. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getfootgun/footgun | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getfootgun-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getfootgun), read 4 November 2026 - [Footgun website](https://getfootgun.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Grav MCP server | Agent MCP Directory" description: "Does Grav have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/getgrav-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Grav MCP server | Agent MCP Directory > Does Grav have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/getgrav-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Grav: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Grav (getgrav.org), so the connector had nothing to connect to. Ora's cached score for getgrav.org is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Grav (registry title: getgrav.org) | | --- | --- | | Domain | getgrav.org | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 1 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getgrav.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Grav. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for getgrav.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Grav. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getgrav-org/index.md) ## Sources - [Ora score page for getgrav.org](https://ora.ai/score/getgrav.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 October 2026, read from GET /api/leaderboard) - [Where Grav was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Grav website](https://getgrav.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Guru MCP server | Agent MCP Directory" description: "Guru: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getguru-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Guru MCP server | Agent MCP Directory > Guru: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getguru-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Guru: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Guru at mcp.api.getguru.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Guru (registry title: Guru Remote MCP Server) | | --- | --- | | Domain | getguru.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 70, grade B; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for getguru.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.api.getguru.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,625 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:39Z https://mcp.api.getguru.com/mcp sent initialize result auth-required (HTTP 401) 1595 ms - 20:03:04Z https://mcp.api.getguru.com/mcp sent initialize result auth-required (HTTP 401) 1625 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.api.getguru.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.api.getguru.com | | Authorization server metadata | mcp.api.getguru.com | | Registration endpoint | https://mcp.api.getguru.com/oauth/mcp/register | ### The sign-in route, step by step 1. Request `https://mcp.api.getguru.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.api.getguru.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.api.getguru.com/oauth/mcp/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Guru. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getguru/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getguru-com/index.md) ## Sources - [Ora score page for getguru.com](https://ora.ai/score/getguru.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getguru), read 4 November 2026 - [Guru website](https://getguru.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kashikoi MCP server | Agent MCP Directory" description: "Does Kashikoi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getkashikoi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kashikoi MCP server | Agent MCP Directory > Does Kashikoi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/getkashikoi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kashikoi: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Kashikoi (getkashikoi.com), so the connector had nothing to connect to. Ora's cached score for getkashikoi.com is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Kashikoi (registry title: getkashikoi.com) | | --- | --- | | Domain | getkashikoi.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getkashikoi.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Kashikoi. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for getkashikoi.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Kashikoi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getkashikoi-com/index.md) ## Sources - [Ora score page for getkashikoi.com](https://ora.ai/score/getkashikoi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Where Kashikoi was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Kashikoi website](https://getkashikoi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lark MCP server | Agent MCP Directory" description: "Does Lark have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/getlark-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lark MCP server | Agent MCP Directory > Does Lark have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/getlark-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lark: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Lark (getlark.ai), so the connector had nothing to connect to. Ora's cached score for getlark.ai is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Lark (registry title: getlark.ai) | | --- | --- | | Domain | getlark.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 12 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getlark.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Lark. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for getlark.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Lark. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getlark-ai/index.md) ## Sources - [Ora score page for getlark.ai](https://ora.ai/score/getlark.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 October 2026, read from GET /api/leaderboard) - [Where Lark was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Lark website](https://getlark.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lilac MCP server | Agent MCP Directory" description: "Does Lilac have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getlilac-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lilac MCP server | Agent MCP Directory > Does Lilac have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/getlilac-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lilac: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Lilac (getlilac.com), so the connector had nothing to connect to. Ora's cached score for getlilac.com is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Lilac (registry title: getlilac.com) | | --- | --- | | Domain | getlilac.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getlilac.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Lilac. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for getlilac.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Lilac. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getlilac-com/index.md) ## Sources - [Ora score page for getlilac.com](https://ora.ai/score/getlilac.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Lilac was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Lilac website](https://getlilac.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GetMattered MCP server | Agent MCP Directory" description: "GetMattered has an open MCP server with 40 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getmattered-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GetMattered MCP server | Agent MCP Directory > GetMattered has an open MCP server with 40 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getmattered-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GetMattered: MCP server, CLI and agent surfaces Yes: GetMattered runs a public MCP server at mcp.getmattered.com that listed 40 tools to a client with no credentials on 4 November 2026. Examples: getmattered\_get\_matches, getmattered\_apply, getmattered\_get\_applications. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | GetMattered | | --- | --- | | Domain | getmattered.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for getmattered.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.getmattered.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | GetMattered 1.13.0 | | Capabilities | tools, prompts, resources | | Tools | 40 | | Resources | 3 | | Prompts | 4 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 3,277 ms over 1 attempt | ### Tools listed 40 tools - getmattered\_get\_matches - getmattered\_apply - getmattered\_get\_applications - getmattered\_approve\_applications - getmattered\_get\_account - getmattered\_get\_profile - getmattered\_reject\_applications - getmattered\_cancel\_applications - getmattered\_refine\_application\_documents - getmattered\_reprepare\_applications - getmattered\_set\_application\_stage - getmattered\_set\_resume - getmattered\_save\_matches - getmattered\_skip\_matches - getmattered\_unsave\_matches - getmattered\_restore\_matches - getmattered\_get\_inbox - getmattered\_reply\_to\_email - getmattered\_score\_resume - getmattered\_analyze\_job\_description - getmattered\_optimize\_resume - getmattered\_generate\_interview\_questions - getmattered\_translate\_resume - getmattered\_update\_job\_preferences - getmattered\_generate\_cover\_letter - getmattered\_get\_resume\_pdf\_link - getmattered\_share\_resume\_pdf - getmattered\_create\_resume\_draft - getmattered\_update\_automatic\_apply\_settings - getmattered\_get\_application\_profile - getmattered\_update\_application\_profile - getmattered\_list\_due\_follow\_ups - getmattered\_list\_sent\_follow\_ups - getmattered\_draft\_follow\_up - getmattered\_send\_follow\_up - getmattered\_record\_follow\_up - getmattered\_list\_saved\_searches - getmattered\_create\_saved\_search - getmattered\_update\_saved\_search - getmattered\_delete\_saved\_search ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:41Z https://mcp.getmattered.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3472 ms - 20:03:06Z https://mcp.getmattered.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3277 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.getmattered.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GetMattered. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getmattered/getmattered | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getmattered-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getmattered), read 4 November 2026 - [GetMattered website](https://getmattered.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Minds MCP server | Agent MCP Directory" description: "Minds: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getminds-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Minds MCP server | Agent MCP Directory > Minds: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getminds-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Minds: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Minds at getminds.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Minds (registry title: Minds: Synthetic Market Research Panels) | | --- | --- | | Domain | getminds.ai | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for getminds.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://getminds.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 435 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:38Z https://getminds.ai/mcp sent initialize result auth-required (HTTP 401) 636 ms - 20:03:04Z https://getminds.ai/mcp sent initialize result auth-required (HTTP 401) 435 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://getminds.ai/.well-known/oauth-protected-resource/mcp", scope="sparks:read sparks:write sparks:chat flows:read flows:write" | | Protected resource metadata | getminds.ai | | Authorization server metadata | getminds.ai | | Registration endpoint | https://getminds.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://getminds.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://getminds.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://getminds.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Minds. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: getminds.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.getminds/minds | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getminds-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getminds), read 4 November 2026 - [Minds website](https://getminds.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Getmocha MCP server | Agent MCP Directory" description: "Does Getmocha have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getmocha-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Getmocha MCP server | Agent MCP Directory > Does Getmocha have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/getmocha-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Getmocha: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Getmocha (getmocha.com), so the connector had nothing to connect to. Ora's cached score for getmocha.com is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Getmocha (registry title: getmocha.com) | | --- | --- | | Domain | getmocha.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getmocha.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Getmocha. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for getmocha.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Getmocha. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getmocha-com/index.md) ## Sources - [Ora score page for getmocha.com](https://ora.ai/score/getmocha.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where Getmocha was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Perspective AI MCP server | Agent MCP Directory" description: "Perspective AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/getperspective-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Perspective AI MCP server | Agent MCP Directory > Perspective AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/getperspective-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Perspective AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Perspective AI at getperspective.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Perspective AI | | --- | --- | | Domain | getperspective.ai | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 11 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for getperspective.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://getperspective.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,029 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:39Z https://getperspective.ai/mcp sent initialize result auth-required (HTTP 401) 855 ms - 20:03:05Z https://getperspective.ai/mcp sent initialize result auth-required (HTTP 401) 1029 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", error="invalid_token", resource_metadata="https://getperspective.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | getperspective.ai | | Authorization server metadata | getperspective.ai | | Registration endpoint | https://getperspective.ai/api/oauth/register | ### The sign-in route, step by step 1. Request `https://getperspective.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://getperspective.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://getperspective.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Perspective AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.getperspective/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getperspective-ai/index.md) ## Sources - [Ora score page for getperspective.ai](https://ora.ai/score/getperspective.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getperspective), read 4 November 2026 - [Perspective AI website](https://getperspective.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Unblocked MCP server | Agent MCP Directory" description: "Unblocked: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/getunblocked-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Unblocked MCP server | Agent MCP Directory > Unblocked: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/getunblocked-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Unblocked: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Unblocked at getunblocked.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Unblocked | | --- | --- | | Domain | getunblocked.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 87, grade A; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for getunblocked.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://getunblocked.com/api/mcpsse | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 929 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:39Z https://getunblocked.com/api/mcpsse sent initialize result auth-required (HTTP 401) 760 ms - 20:03:05Z https://getunblocked.com/api/mcpsse sent initialize result auth-required (HTTP 401) 929 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://getunblocked.com/.well-known/oauth-protected-resource" | | Protected resource metadata | getunblocked.com | | Authorization server metadata | getunblocked.com | | Registration endpoint | https://getunblocked.com/api/auth/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://getunblocked.com/api/mcpsse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://getunblocked.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://getunblocked.com/api/auth/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Unblocked. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getunblocked/unblocked-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getunblocked-com/index.md) ## Sources - [Ora score page for getunblocked.com](https://ora.ai/score/getunblocked.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getunblocked), read 4 November 2026 - [Unblocked website](https://getunblocked.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Veles MCP server | Agent MCP Directory" description: "Veles: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/getveles-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Veles MCP server | Agent MCP Directory > Veles: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/getveles-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Veles: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Veles at app.getveles.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Veles (registry title: Veles CPQ) | | --- | --- | | Domain | getveles.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 51, grade C; Ora scanned the domain on 10 July 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getveles.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.getveles.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,081 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:40Z https://app.getveles.com/mcp sent initialize result auth-required (HTTP 401) 1217 ms - 20:03:05Z https://app.getveles.com/mcp sent initialize result auth-required (HTTP 401) 1081 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.getveles.com/.well-known/oauth-protected-resource" | | Protected resource metadata | app.getveles.com | | Authorization server metadata | app.getveles.com | | Registration endpoint | https://app.getveles.com/oauth/register | ### The sign-in route, step by step 1. Request `https://app.getveles.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.getveles.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.getveles.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Veles. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getveles/cpq | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getveles-com/index.md) ## Sources - [Ora score page for getveles.com](https://ora.ai/score/getveles.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 July 2026, read from GET /api/leaderboard) - [Where Veles was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.getveles%2Fcpq), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getveles), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Versive MCP server | Agent MCP Directory" description: "Versive: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/getversive-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Versive MCP server | Agent MCP Directory > Versive: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/getversive-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Versive: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Versive at mcp.getversive.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Versive | | --- | --- | | Domain | getversive.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 84, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for getversive.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.getversive.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 177 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:39Z https://mcp.getversive.com/mcp sent initialize result auth-required (HTTP 401) 490 ms - 20:03:04Z https://mcp.getversive.com/mcp sent initialize result auth-required (HTTP 401) 177 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.getversive.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.getversive.com | | Authorization server metadata | mcp.getversive.com | | Registration endpoint | https://mcp.getversive.com/register | ### The sign-in route, step by step 1. Request `https://mcp.getversive.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.getversive.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.getversive.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Versive. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getversive/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getversive-com/index.md) ## Sources - [Ora score page for getversive.com](https://ora.ai/score/getversive.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Versive was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.getversive%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getversive), read 4 November 2026 - [Versive website](https://getversive.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WP Agent MCP server | Agent MCP Directory" description: "WP Agent: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/getwpagent-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WP Agent MCP server | Agent MCP Directory > WP Agent: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/getwpagent-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WP Agent: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for WP Agent at mcp.getwpagent.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | WP Agent (registry title: WP Agent - WordPress publishing & management with Claude) | | --- | --- | | Domain | getwpagent.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for getwpagent.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.getwpagent.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 626 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:40Z https://mcp.getwpagent.com/mcp sent initialize result auth-required (HTTP 401) 694 ms - 20:03:05Z https://mcp.getwpagent.com/mcp sent initialize result auth-required (HTTP 401) 626 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.getwpagent.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.getwpagent.com | | Authorization server metadata | mcp.getwpagent.com | | Registration endpoint | https://mcp.getwpagent.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.getwpagent.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.getwpagent.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.getwpagent.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WP Agent. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.getwpagent/wordpress | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/getwpagent-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=getwpagent), read 4 November 2026 - [WP Agent website](https://getwpagent.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ghost MCP server | Agent MCP Directory" description: "Does Ghost have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ghost-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ghost MCP server | Agent MCP Directory > Does Ghost have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/ghost-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ghost: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ghost (ghost.org), so the connector had nothing to connect to. Ora's cached score for ghost.org is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ghost | | --- | --- | | Domain | ghost.org | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 4,363 on the list of 4 November 2026 | | Ora score | 70, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ghost.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ghost. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ghost.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ghost. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ghost-org/index.md) ## Sources - [Ora score page for ghost.org](https://ora.ai/score/ghost.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Ghost was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ghost website](https://ghost.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GitBook MCP server | Agent MCP Directory" description: "GitBook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/gitbook-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GitBook MCP server | Agent MCP Directory > GitBook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/gitbook-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GitBook: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for GitBook; the connector's guess at mcp.gitbook.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | GitBook | | --- | --- | | Domain | gitbook.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 7,432 on the list of 4 November 2026 | | Ora score | 86, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for gitbook.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.gitbook.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 511 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:12Z https://mcp.gitbook.com/mcp sent initialize result auth-required (HTTP 401) 318 ms - 20:01:51Z https://mcp.gitbook.com/mcp sent initialize result auth-required (HTTP 401) 511 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.gitbook.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.gitbook.com | | Authorization server metadata | oauth.gitbook.com | | Registration endpoint | https://oauth.gitbook.com/register | ### The sign-in route, step by step 1. Request `https://mcp.gitbook.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.gitbook.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://oauth.gitbook.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GitBook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: gitbook.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gitbook-com/index.md) ## Sources - [Ora score page for gitbook.com](https://ora.ai/score/gitbook.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where GitBook was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [GitBook website](https://gitbook.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Gitea MCP server | Agent MCP Directory" description: "Does Gitea have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gitea-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gitea MCP server | Agent MCP Directory > Does Gitea have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/gitea-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gitea: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Gitea (gitea.com), so the connector had nothing to connect to. Ora's cached score for gitea.com is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Gitea (registry title: gitea.com) | | --- | --- | | Domain | gitea.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 4,011 on the list of 4 November 2026 | | Ora score | 55, grade C; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for gitea.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Gitea. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for gitea.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Gitea. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gitea-com/index.md) ## Sources - [Ora score page for gitea.com](https://ora.ai/score/gitea.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/score) - [Where Gitea was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Gitea website](https://gitea.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GitHub MCP server | Agent MCP Directory" description: "GitHub: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/github-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GitHub MCP server | Agent MCP Directory > GitHub: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/github-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GitHub: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for GitHub at api.githubcopilot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | GitHub | | --- | --- | | Domain | github.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Tranco rank | 34 on the list of 4 November 2026 | | Ora score | 65, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for github.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.githubcopilot.com/mcp/ | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:06 UTC | | Handshake time | 1,544 ms over 1 attempt | | Documentation | github.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:55:52Z https://api.githubcopilot.com/mcp/ sent initialize result auth-required (HTTP 401) 1232 ms - 20:01:27Z https://api.githubcopilot.com/mcp/ sent initialize result auth-required (HTTP 401) 1664 ms - 20:06:07Z https://api.githubcopilot.com/mcp/ sent initialize result auth-required (HTTP 401) 1544 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="No access token was provided in this request", resource_metadata="https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp/" | | Protected resource metadata | api.githubcopilot.com | | Authorization server metadata | github.com | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.githubcopilot.com/mcp/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://github.com/.well-known/oauth-authorization-server/login/oauth`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GitHub. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: raw.githubusercontent.com (JSON, via vendor docs). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Yes: compoid/compoid-mcp | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/github-com/index.md) ## Sources - [GitHub MCP documentation](https://github.com/github/github-mcp-server), read 4 November 2026 - [Ora score page for github.com](https://ora.ai/score/github.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [GitHub website](https://github.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Githubcopilot MCP server | Agent MCP Directory" description: "Githubcopilot: sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/githubcopilot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Githubcopilot MCP server | Agent MCP Directory > Githubcopilot: sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/githubcopilot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Githubcopilot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Githubcopilot at api.githubcopilot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Githubcopilot (registry title: GitHub) | | --- | --- | | Domain | githubcopilot.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Tranco rank | 3,131 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for githubcopilot.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.githubcopilot.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,246 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:02Z https://api.githubcopilot.com/mcp sent initialize result auth-required (HTTP 401) 1320 ms - 20:01:37Z https://api.githubcopilot.com/mcp sent initialize result auth-required (HTTP 401) 1246 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="No access token was provided in this request", resource_metadata="https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.githubcopilot.com | | Authorization server metadata | github.com | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.githubcopilot.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://github.com/.well-known/oauth-authorization-server/login/oauth`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Githubcopilot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/githubcopilot-com/index.md) ## Sources - [Where Githubcopilot was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GitLab MCP server | Agent MCP Directory" description: "GitLab: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gitlab-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GitLab MCP server | Agent MCP Directory > GitLab: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gitlab-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GitLab: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for GitLab at gitlab.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | GitLab (registry title: gitlab.com) | | --- | --- | | Domain | gitlab.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 376 on the list of 4 November 2026 | | Ora score | 81, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for gitlab.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://gitlab.com/api/v4/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 356 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://gitlab.com/api/v4/mcp sent initialize result auth-required (HTTP 401) 289 ms - 20:01:29Z https://gitlab.com/api/v4/mcp sent initialize result auth-required (HTTP 401) 356 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="GitLab", scope="mcp", resource_metadata="https://gitlab.com/.well-known/oauth-protected-resource/api/v4/mcp" | | Protected resource metadata | gitlab.com | | Authorization server metadata | gitlab.com | | Registration endpoint | https://gitlab.com/oauth/register | ### The sign-in route, step by step 1. Request `https://gitlab.com/api/v4/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://gitlab.com/.well-known/oauth-protected-resource/api/v4/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://gitlab.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GitLab. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: gitlab.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.gitlab/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gitlab-com/index.md) ## Sources - [Ora score page for gitlab.com](https://ora.ai/score/gitlab.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where GitLab was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.gitlab%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=gitlab), read 4 November 2026 - [GitLab website](https://gitlab.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GitMCP MCP server | Agent MCP Directory" description: "GitMCP has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gitmcp-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GitMCP MCP server | Agent MCP Directory > GitMCP has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gitmcp-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # GitMCP: MCP server, CLI and agent surfaces Yes: GitMCP runs a public MCP server at gitmcp.io that listed 5 tools to a client with no credentials on 4 November 2026. Examples: match\_common\_libs\_owner\_repo\_mapping, fetch\_generic\_documentation, search\_generic\_documentation. It speaks streamable-http, protocol 2025-03-26. Ora's cached score for gitmcp.io is 37, grade D, read on 5 November 2026. ## Fact sheet | Company | GitMCP | | --- | --- | | Domain | gitmcp.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 37, grade D; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for gitmcp.io, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://gitmcp.io/docs | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | GitMCP 1.1.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,763 ms over 1 attempt | ### Tools listed 5 tools - match\_common\_libs\_owner\_repo\_mapping - fetch\_generic\_documentation - search\_generic\_documentation - search\_generic\_code - fetch\_generic\_url\_content ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:41Z https://gitmcp.io/docs sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1455 ms - 20:03:06Z https://gitmcp.io/docs sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1763 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://gitmcp.io/docs` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GitMCP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gitmcp-io/index.md) ## Sources - [Ora score page for gitmcp.io](https://ora.ai/score/gitmcp.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/score) - [Where GitMCP was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [GitMCP website](https://gitmcp.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GitOps MCP server | Agent MCP Directory" description: "Does GitOps have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gitops-tech site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GitOps MCP server | Agent MCP Directory > Does GitOps have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/gitops-tech Site: Agent MCP Directory Last reviewed: 2026-11-05 # GitOps: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for GitOps (gitops.tech), so the connector had nothing to connect to. Ora's cached score for gitops.tech is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | GitOps (registry title: gitops.tech) | | --- | --- | | Domain | gitops.tech | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for gitops.tech, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for GitOps. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for gitops.tech, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for GitOps. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gitops-tech/index.md) ## Sources - [Ora score page for gitops.tech](https://ora.ai/score/gitops.tech?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where GitOps was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [GitOps website](https://gitops.tech), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Gitpod MCP server | Agent MCP Directory" description: "Does Gitpod have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gitpod-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gitpod MCP server | Agent MCP Directory > Does Gitpod have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/gitpod-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gitpod: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Gitpod (gitpod.io), so the connector had nothing to connect to. Ora's cached score for gitpod.io is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Gitpod | | --- | --- | | Domain | gitpod.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 25 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for gitpod.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Gitpod. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for gitpod.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Gitpod. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gitpod-io/index.md) ## Sources - [Ora score page for gitpod.io](https://ora.ai/score/gitpod.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 September 2026, read from GET /api/leaderboard) - [Where Gitpod was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Gitpod website](https://gitpod.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GlanceAI MCP server | Agent MCP Directory" description: "GlanceAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/glance-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GlanceAI MCP server | Agent MCP Directory > GlanceAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/glance-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GlanceAI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for GlanceAI at glance.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | GlanceAI (registry title: GlanceAI Fashion MCP) | | --- | --- | | Domain | glance.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 5,803 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for glance.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://glance.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,744 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:10Z https://glance.com/mcp sent initialize result auth-required (HTTP 401) 1115 ms - 20:01:48Z https://glance.com/mcp sent initialize result auth-required (HTTP 401) 1744 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://ember.ailooks.glance.com/.well-known/oauth-protected-resource" | | Protected resource metadata | ember.ailooks.glance.com | | Authorization server metadata | ember.ailooks.glance.com | | Registration endpoint | https://ember.ailooks.glance.com/register | ### The sign-in route, step by step 1. Request `https://glance.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://ember.ailooks.glance.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://ember.ailooks.glance.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GlanceAI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: glance.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: glance.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Found: glance.com/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: glance.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.glance/glanceai-fashion | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/glance-com/index.md) ## Sources - [Where GlanceAI was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.glance%2Fglanceai-fashion), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=glance), read 4 November 2026 - [GlanceAI website](https://glance.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Glassflow MCP server | Agent MCP Directory" description: "Glassflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/glassflow-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Glassflow MCP server | Agent MCP Directory > Glassflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/glassflow-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Glassflow: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Glassflow at mcp.eu.console.rius-glassflow.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Glassflow (registry title: Rius) | | --- | --- | | Domain | glassflow.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for glassflow.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.eu.console.rius-glassflow.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 766 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:41Z https://mcp.eu.console.rius-glassflow.com/mcp sent initialize result auth-required (HTTP 401) 829 ms - 20:03:06Z https://mcp.eu.console.rius-glassflow.com/mcp sent initialize result auth-required (HTTP 401) 766 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.eu.console.rius-glassflow.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.eu.console.rius-glassflow.com | | Authorization server metadata | mcp.eu.console.rius-glassflow.com | | Registration endpoint | https://mcp.eu.console.rius-glassflow.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.eu.console.rius-glassflow.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.eu.console.rius-glassflow.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.eu.console.rius-glassflow.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Glassflow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.glassflow/rius | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/glassflow-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=glassflow), read 4 November 2026 - [Glassflow website](https://glassflow.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Glean MCP server | Agent MCP Directory" description: "Does Glean have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/glean-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Glean MCP server | Agent MCP Directory > Does Glean have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/glean-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Glean: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Glean (glean.com), so the connector had nothing to connect to. Ora's cached score for glean.com is 72, grade B, read on 5 November 2026. The company was added from the GitHub MCP Registry. ## Fact sheet | Company | Glean (registry title: Glean Remote MCP Server) | | --- | --- | | Domain | glean.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 24 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for glean.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Glean. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for glean.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (com.glean/mcp) | | GitHub MCP Registry | Listed | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Glean. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.glean/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/glean-com/index.md) ## Sources - [Ora score page for glean.com](https://ora.ai/score/glean.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 October 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=glean), read 4 November 2026 - [Glean website](https://glean.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Glide MCP server | Agent MCP Directory" description: "Does Glide have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/glide-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Glide MCP server | Agent MCP Directory > Does Glide have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/glide-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Glide: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Glide (glide.app), so the connector had nothing to connect to. Ora's cached score for glide.app is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Glide (registry title: glide.app) | | --- | --- | | Domain | glide.app | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for glide.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Glide. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for glide.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Glide. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/glide-app/index.md) ## Sources - [Ora score page for glide.app](https://ora.ai/score/glide.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Glide was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Glide website](https://glide.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Glideapps MCP server | Agent MCP Directory" description: "Glideapps has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/glideapps-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Glideapps MCP server | Agent MCP Directory > Glideapps has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/glideapps-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Glideapps: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Glideapps; the connector tried mcp.glideapps.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: ERR\_SSL\_SSL/TLS\_ALERT\_HANDSHAKE\_FAILURE. Ora's cached score for glideapps.com is 64, grade C, read on 5 November 2026. ## Fact sheet | Company | Glideapps (registry title: glideapps.com) | | --- | --- | | Domain | glideapps.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 64, grade C; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for glideapps.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.glideapps.com/mcp | | --- | --- | | How it was found | mcp.glideapps.com was tried as a guess and did not answer | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 241 ms over 1 attempt | | Result | ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:41Z https://mcp.glideapps.com/mcp sent initialize result no-answer 74 ms - 20:03:06Z https://mcp.glideapps.com/mcp sent initialize result no-answer 241 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.glideapps.com/mcp`. The connector could not tell what it wants: ERR\_SSL\_SSL/TLS\_ALERT\_HANDSHAKE\_FAILURE. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Glideapps. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/glideapps-com/index.md) ## Sources - [Ora score page for glideapps.com](https://ora.ai/score/glideapps.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/leaderboard) - [Where Glideapps was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Glideapps website](https://glideapps.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Glif MCP server | Agent MCP Directory" description: "Glif: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/glif-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Glif MCP server | Agent MCP Directory > Glif: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/glif-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Glif: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Glif at glif.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Glif | | --- | --- | | Domain | glif.app | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 76, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for glif.app, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://glif.app/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 841 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:42Z https://glif.app/api/mcp sent initialize result auth-required (HTTP 401) 1096 ms - 20:03:07Z https://glif.app/api/mcp sent initialize result auth-required (HTTP 401) 841 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="glif-mcp", resource_metadata="https://glif.app/api/mcp/.well-known/oauth-protected-resource" | | Protected resource metadata | glif.app | | Authorization server metadata | glif.app | | Registration endpoint | https://glif.app/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://glif.app/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://glif.app/api/mcp/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://glif.app/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Glif. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: glif.app (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: glif.app/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: glif.app/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.glif/glif | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/glif-app/index.md) ## Sources - [Ora score page for glif.app](https://ora.ai/score/glif.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=glif), read 4 November 2026 - [Glif website](https://glif.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Globalping MCP server | Agent MCP Directory" description: "Globalping: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/globalping-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Globalping MCP server | Agent MCP Directory > Globalping: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/globalping-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Globalping: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Globalping at mcp.globalping.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Globalping | | --- | --- | | Domain | globalping.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for globalping.io when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.globalping.dev/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 477 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:42Z https://mcp.globalping.dev/sse sent initialize result auth-required (HTTP 401) 1102 ms - 20:03:06Z https://mcp.globalping.dev/sse sent initialize result auth-required (HTTP 401) 477 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.globalping.dev/.well-known/oauth-protected-resource/sse", scope="measurements" | | Protected resource metadata | mcp.globalping.dev | | Authorization server metadata | mcp.globalping.dev | | Registration endpoint | https://mcp.globalping.dev/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.globalping.dev/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.globalping.dev/.well-known/oauth-protected-resource/sse` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.globalping.dev/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Globalping. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/globalping-io/index.md) ## Sources - [Where Globalping was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Globalping website](https://globalping.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GoCardless MCP server | Agent MCP Directory" description: "GoCardless: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/gocardless-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GoCardless MCP server | Agent MCP Directory > GoCardless: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/gocardless-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GoCardless: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for GoCardless at mcp.gocardless.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | GoCardless (registry title: GoCardless MCP Server) | | --- | --- | | Domain | gocardless.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 47, grade D; Ora scanned the domain on 19 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for gocardless.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.gocardless.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 379 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:42Z https://mcp.gocardless.com/mcp sent initialize result auth-required (HTTP 401) 808 ms - 20:03:07Z https://mcp.gocardless.com/mcp sent initialize result auth-required (HTTP 401) 379 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="GoCardless MCP", resource_metadata="https://mcp.gocardless.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.gocardless.com | | Authorization server metadata | mcp.gocardless.com | | Registration endpoint | https://mcp.gocardless.com/register | ### The sign-in route, step by step 1. Request `https://mcp.gocardless.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.gocardless.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.gocardless.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GoCardless. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.gocardless/gc-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gocardless-com/index.md) ## Sources - [Ora score page for gocardless.com](https://ora.ai/score/gocardless.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 August 2026, read from GET /api/leaderboard) - [Where GoCardless was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.gocardless%2Fgc-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=gocardless), read 4 November 2026 - [GoCardless website](https://gocardless.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Goldsky MCP server | Agent MCP Directory" description: "Goldsky has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/goldsky-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Goldsky MCP server | Agent MCP Directory > Goldsky has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/goldsky-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Goldsky: MCP server, CLI and agent surfaces Yes: Goldsky runs a public MCP server at docs.goldsky.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: search\_goldsky, query\_docs\_filesystem\_goldsky, submit\_feedback. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for goldsky.com is 81, grade B, read on 5 November 2026. ## Fact sheet | Company | Goldsky | | --- | --- | | Domain | goldsky.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 81, grade B; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for goldsky.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://docs.goldsky.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Goldsky 1.0.0 | | Capabilities | tools, resources | | Tools | 3 | | Resources | 21 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,651 ms over 1 attempt | ### Tools listed 3 tools - search\_goldsky - query\_docs\_filesystem\_goldsky - submit\_feedback ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:43Z https://docs.goldsky.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1714 ms - 20:03:08Z https://docs.goldsky.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1651 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://docs.goldsky.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Goldsky. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.goldsky/docs | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/goldsky-com/index.md) ## Sources - [Ora score page for goldsky.com](https://ora.ai/score/goldsky.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=goldsky), read 4 November 2026 - [Goldsky website](https://goldsky.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Gomdori MCP server | Agent MCP Directory" description: "Gomdori has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gomdori-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gomdori MCP server | Agent MCP Directory > Gomdori has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gomdori-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gomdori: MCP server, CLI and agent surfaces Yes: Gomdori runs a public MCP server at mcp.gomdori.app that listed 10 tools to a client with no credentials on 4 November 2026. Examples: search\_law, get\_law\_text, ordinance\_radar. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Gomdori (registry title: Korean Law MCP) | | --- | --- | | Domain | gomdori.app | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for gomdori.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.gomdori.app/law | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | korean-law 4.15.23 | | Capabilities | tools | | Tools | 10 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,692 ms over 1 attempt | ### Tools listed 10 tools - search\_law - get\_law\_text - ordinance\_radar - get\_annexes - legal\_research - legal\_analysis - discover\_tools - execute\_tool - search\_decisions - get\_decision\_text ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:44Z https://mcp.gomdori.app/law sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2217 ms - 20:03:08Z https://mcp.gomdori.app/law sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1692 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.gomdori.app/law` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Gomdori. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gomdori-app/index.md) ## Sources - [Where Gomdori was found](https://github.com/mcp/chrisryugj/korean-law-mcp), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Google MCP server | Agent MCP Directory" description: "Google has an open MCP server with 29 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/google-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Google MCP server | Agent MCP Directory > Google has an open MCP server with 29 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/google-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Google: MCP server, CLI and agent surfaces Yes: Google runs a public MCP server at compute.googleapis.com that listed 29 tools to a client with no credentials on 4 November 2026. Examples: create\_instance, delete\_instance, start\_instance. It speaks streamable-http, protocol 2026-07-28. Ora's cached score for google.com is 55, grade C, read on 5 November 2026. ## Fact sheet | Company | Google | | --- | --- | | Domain | google.com | | Category | Identity & Auth (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 1 on the list of 4 November 2026 | | Ora score | 55, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for google.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://compute.googleapis.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | StatelessServer ESF | | Capabilities | tools | | Tools | 29 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,750 ms over 1 attempt | ### Tools listed 29 tools - create\_instance - delete\_instance - start\_instance - stop\_instance - reset\_instance - get\_instance\_basic\_info - set\_instance\_machine\_type - list\_instance\_attached\_disks - list\_instances - get\_instance\_group\_manager\_basic\_info - list\_instance\_group\_managers - list\_managed\_instances - list\_instance\_templates - get\_instance\_template\_basic\_info - get\_instance\_template\_properties - get\_disk\_basic\_info - get\_disk\_performance\_config - list\_disks - list\_accelerator\_types - list\_machine\_types - list\_images - get\_zone\_operation - get\_reservation\_basic\_info - get\_reservation\_details - list\_reservations - list\_commitments - get\_commitment\_basic\_info - list\_commitment\_reservations - list\_snapshots ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://compute.googleapis.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2769 ms - 20:01:29Z https://compute.googleapis.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2750 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://compute.googleapis.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Google. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/google-com/index.md) ## Sources - [Ora score page for google.com](https://ora.ai/score/google.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Google was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Google website](https://google.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Keep(卡路里科技)-自律给我自由 MCP server | Agent MCP Directory" description: "Does Keep(卡路里科技)-自律给我自由 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/google-keep-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Keep(卡路里科技)-自律给我自由 MCP server | Agent MCP Directory > Does Keep(卡路里科技)-自律给我自由 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/google-keep-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Keep(卡路里科技)-自律给我自由: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Keep(卡路里科技)-自律给我自由 (google.keep.com), so the connector had nothing to connect to. Ora's cached score for google.keep.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Keep(卡路里科技)-自律给我自由 (registry title: google.keep.com) | | --- | --- | | Domain | google.keep.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for google.keep.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Keep(卡路里科技)-自律给我自由. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for google.keep.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Keep(卡路里科技)-自律给我自由. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/google-keep-com/index.md) ## Sources - [Ora score page for google.keep.com](https://ora.ai/score/google.keep.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Keep(卡路里科技)-自律给我自由 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Keep(卡路里科技)-自律给我自由 website](https://google.keep.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Google Cloud (googleapis.com) MCP server | Agent MCP Directory" description: "Google Cloud (googleapis.com) has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/googleapis-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Google Cloud (googleapis.com) MCP server | Agent MCP Directory > Google Cloud (googleapis.com) has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/googleapis-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Google Cloud: MCP server, CLI and agent surfaces Yes: Google Cloud runs a public MCP server at run.googleapis.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: get\_service, list\_services, deploy\_service\_from\_image. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Google Cloud | | --- | --- | | Domain | googleapis.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 8 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for googleapis.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://run.googleapis.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | StatelessServer ESF | | Capabilities | prompts, tools | | Tools | 5 | | Resources | 0 | | Prompts | 1 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,166 ms over 1 attempt | ### Tools listed 5 tools - get\_service - list\_services - deploy\_service\_from\_image - deploy\_service\_from\_archive - deploy\_service\_from\_file\_contents ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:52Z https://run.googleapis.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1093 ms - 20:01:27Z https://run.googleapis.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1166 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://run.googleapis.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Google Cloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.googleapis.androidmanagement/mcp, com.googleapis.bigtableadmin/mcp, com.googleapis.composer/mcp and 2 more | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/googleapis-com/index.md) ## Sources - [Where Google Cloud was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.googleapis.androidmanagement%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=googleapis), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GoSQLX MCP server | Agent MCP Directory" description: "GoSQLX has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gosqlx-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GoSQLX MCP server | Agent MCP Directory > GoSQLX has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gosqlx-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # GoSQLX: MCP server, CLI and agent surfaces Yes: GoSQLX runs a public MCP server at mcp.gosqlx.dev that listed 7 tools to a client with no credentials on 4 November 2026. Examples: analyze\_sql, extract\_metadata, format\_sql. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | GoSQLX | | --- | --- | | Domain | gosqlx.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for gosqlx.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.gosqlx.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | gosqlx-mcp 1.17.0 | | Capabilities | resources, tools | | Tools | 7 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,027 ms over 1 attempt | ### Tools listed 7 tools - analyze\_sql - extract\_metadata - format\_sql - lint\_sql - parse\_sql - security\_scan - validate\_sql ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:43Z https://mcp.gosqlx.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1338 ms - 20:03:08Z https://mcp.gosqlx.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1027 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.gosqlx.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GoSQLX. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gosqlx-dev/index.md) ## Sources - [Where GoSQLX was found](https://github.com/mcp/ajitpratap0/GoSQLX), read 4 November 2026 - [GoSQLX website](https://gosqlx.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Grafana MCP server | Agent MCP Directory" description: "Grafana: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/grafana-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Grafana MCP server | Agent MCP Directory > Grafana: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/grafana-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Grafana: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Grafana; the connector's guess at mcp.grafana.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Grafana | | --- | --- | | Domain | grafana.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,341 on the list of 4 November 2026 | | Ora score | 76, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for grafana.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.grafana.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,498 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:59Z https://mcp.grafana.com/mcp sent initialize result auth-required (HTTP 401) 1462 ms - 20:01:35Z https://mcp.grafana.com/mcp sent initialize result auth-required (HTTP 401) 1498 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.grafana.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.grafana.com | | Authorization server metadata | mcp.grafana.com | | Registration endpoint | https://mcp.grafana.com/mcp/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.grafana.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.grafana.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.grafana.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Grafana. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/grafana-com/index.md) ## Sources - [Ora score page for grafana.com](https://ora.ai/score/grafana.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Grafana was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Grafana website](https://grafana.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Grafbase MCP server | Agent MCP Directory" description: "Grafbase has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/grafbase-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Grafbase MCP server | Agent MCP Directory > Grafbase has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/grafbase-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Grafbase: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Grafbase (api.grafbase.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | Grafbase | | --- | --- | | Domain | grafbase.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Ora score | 45, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for grafbase.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.grafbase.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | HTTP status | 404 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 445 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:43Z https://api.grafbase.com/mcp sent initialize result no-answer (HTTP 404) 879 ms - 20:03:07Z https://api.grafbase.com/mcp sent initialize result no-answer (HTTP 404) 445 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | OAuth 2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.grafbase.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Grafbase. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/grafbase-com/index.md) ## Sources - [Ora score page for grafbase.com](https://ora.ai/score/grafbase.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Grafbase was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Grafbase website](https://grafbase.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Granola MCP server | Agent MCP Directory" description: "Granola: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/granola-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Granola MCP server | Agent MCP Directory > Granola: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/granola-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Granola: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Granola at mcp.granola.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Granola | | --- | --- | | Domain | granola.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 5,012 on the list of 4 November 2026 | | Ora score | 77, grade B; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for granola.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.granola.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 471 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:07Z https://mcp.granola.ai/mcp sent initialize result auth-required (HTTP 401) 740 ms - 20:01:44Z https://mcp.granola.ai/mcp sent initialize result auth-required (HTTP 401) 471 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authorization needed", resource_metadata="https://mcp.granola.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.granola.ai | | Authorization server metadata | mcp-auth.granola.ai | | Registration endpoint | https://mcp-auth.granola.ai/oauth2/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.granola.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.granola.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp-auth.granola.ai/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Granola. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: granola.ai/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/granola-ai/index.md) ## Sources - [Ora score page for granola.ai](https://ora.ai/score/granola.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/score) - [Where Granola was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Granola website](https://granola.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Graphcms MCP server | Agent MCP Directory" description: "Graphcms: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/graphcms-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Graphcms MCP server | Agent MCP Directory > Graphcms: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/graphcms-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Graphcms: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Graphcms; the connector's guess at mcp.graphcms.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Graphcms (registry title: graphcms.com) | | --- | --- | | Domain | graphcms.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 44, grade D; Ora scanned the domain on 21 July 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for graphcms.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.graphcms.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 964 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:43Z https://mcp.graphcms.com/mcp sent initialize result auth-required (HTTP 401) 1142 ms - 20:03:08Z https://mcp.graphcms.com/mcp sent initialize result auth-required (HTTP 401) 964 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.hygraph.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.hygraph.com | | Authorization server metadata | auth.hygraph.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.graphcms.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.hygraph.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Graphcms. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/graphcms-com/index.md) ## Sources - [Ora score page for graphcms.com](https://ora.ai/score/graphcms.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 July 2026, read from GET /api/leaderboard) - [Where Graphcms was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Graphcms website](https://graphcms.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Graphify MCP server | Agent MCP Directory" description: "Graphify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/graphify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Graphify MCP server | Agent MCP Directory > Graphify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/graphify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Graphify: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Graphify at api.graphify.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Graphify | | --- | --- | | Domain | graphify.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 78, grade B; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for graphify.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.graphify.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 780 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:43Z https://api.graphify.com/mcp sent initialize result auth-required (HTTP 401) 701 ms - 20:03:08Z https://api.graphify.com/mcp sent initialize result auth-required (HTTP 401) 780 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.graphify.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.graphify.com | | Authorization server metadata | api.graphify.com | | Registration endpoint | https://api.graphify.com/oauth/register | ### The sign-in route, step by step 1. Request `https://api.graphify.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.graphify.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.graphify.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Graphify. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/graphify-com/index.md) ## Sources - [Ora score page for graphify.com](https://ora.ai/score/graphify.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Graphify website](https://graphify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Graylog MCP server | Agent MCP Directory" description: "Does Graylog have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/graylog-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Graylog MCP server | Agent MCP Directory > Does Graylog have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/graylog-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Graylog: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Graylog (graylog.org), so the connector had nothing to connect to. Ora's cached score for graylog.org is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Graylog (registry title: graylog.org) | | --- | --- | | Domain | graylog.org | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for graylog.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Graylog. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for graylog.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Graylog. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/graylog-org/index.md) ## Sources - [Ora score page for graylog.org](https://ora.ai/score/graylog.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Graylog was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Graylog website](https://graylog.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Greca House MCP server | Agent MCP Directory" description: "Greca House has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/grecahouse-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Greca House MCP server | Agent MCP Directory > Greca House has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/grecahouse-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Greca House: MCP server, CLI and agent surfaces Yes: Greca House runs a public MCP server at grecahouse.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: search\_greece\_properties, get\_property\_details, compare\_budget\_by\_area. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Greca House (registry title: Greca House: Greek Property) | | --- | --- | | Domain | grecahouse.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for grecahouse.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://grecahouse.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | greca-house-greece-property 1.1.1 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 672 ms over 1 attempt | ### Tools listed 5 tools - search\_greece\_properties - get\_property\_details - compare\_budget\_by\_area - estimate\_greece\_buying\_costs - get\_greece\_market\_research ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:44Z https://grecahouse.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1003 ms - 20:03:08Z https://grecahouse.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 672 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://grecahouse.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Greca House. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.grecahouse/greek-property | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/grecahouse-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=grecahouse), read 4 November 2026 - [Greca House website](https://grecahouse.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Greptile MCP server | Agent MCP Directory" description: "Does Greptile have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/greptile-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Greptile MCP server | Agent MCP Directory > Does Greptile have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/greptile-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Greptile: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Greptile (greptile.com), so the connector had nothing to connect to. Ora's cached score for greptile.com is 77, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Greptile (registry title: greptile.com) | | --- | --- | | Domain | greptile.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for greptile.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Greptile. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for greptile.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Greptile. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/greptile-com/index.md) ## Sources - [Ora score page for greptile.com](https://ora.ai/score/greptile.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Greptile was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Greptile website](https://greptile.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GrowthBook MCP server | Agent MCP Directory" description: "GrowthBook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/growthbook-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GrowthBook MCP server | Agent MCP Directory > GrowthBook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/growthbook-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # GrowthBook: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for GrowthBook; the connector's guess at mcp.growthbook.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | GrowthBook (registry title: growthbook.io) | | --- | --- | | Domain | growthbook.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,251 on the list of 4 November 2026 | | Ora score | 80, grade B; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for growthbook.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.growthbook.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,528 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:05Z https://mcp.growthbook.io/mcp sent initialize result auth-required (HTTP 401) 1341 ms - 20:01:41Z https://mcp.growthbook.io/mcp sent initialize result auth-required (HTTP 401) 1528 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="GrowthBook MCP", resource_metadata="https://mcp.growthbook.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.growthbook.io | | Authorization server metadata | api.growthbook.io | | Registration endpoint | https://api.growthbook.io/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.growthbook.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.growthbook.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.growthbook.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GrowthBook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/growthbook-io/index.md) ## Sources - [Ora score page for growthbook.io](https://ora.ai/score/growthbook.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/score) - [Where GrowthBook was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [GrowthBook website](https://growthbook.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Gryz MCP server | Agent MCP Directory" description: "Gryz: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gryz-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gryz MCP server | Agent MCP Directory > Gryz: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/gryz-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gryz: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Gryz at www.gryz.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Gryz | | --- | --- | | Domain | gryz.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for gryz.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.gryz.ai/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 789 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:45Z https://www.gryz.ai/api/mcp sent initialize result auth-required (HTTP 401) 1546 ms - 20:03:09Z https://www.gryz.ai/api/mcp sent initialize result auth-required (HTTP 401) 789 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="www.gryz.ai", resource_metadata="https://www.gryz.ai/.well-known/oauth-protected-resource", scope="documents memory:read memory:write projects:read projects:write skills:read skills:write tasks:write broker:read broker:write" | | Protected resource metadata | www.gryz.ai | | Authorization server metadata | www.gryz.ai | | Registration endpoint | https://www.gryz.ai/api/oauth/register/ | ### The sign-in route, step by step 1. Request `https://www.gryz.ai/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.gryz.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.gryz.ai/api/oauth/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Gryz. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gryz-ai/index.md) ## Sources - [Gryz website](https://gryz.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Endpoints found by subdomain guess | Agent MCP Directory" description: "106 companies whose MCP endpoint was found by guessing an mcp subdomain, then checked by connecting on 4 November 2026. The label is on every entry." canonical: https://agentmcpdirectory.com/directory/guessed site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Endpoints found by subdomain guess | Agent MCP Directory > 106 companies whose MCP endpoint was found by guessing an mcp subdomain, then checked by connecting on 4 November 2026. The label is on every entry. Source: https://agentmcpdirectory.com/directory/guessed Site: Agent MCP Directory Last reviewed: 2026-11-05 # Endpoints found by subdomain guess 106 rows were found by guessing mcp.: 9 listed tools ("endpoint found by subdomain guess, verified by connecting"), 63 answered with a sign-in challenge and were not verified, and 34 did not answer or answered otherwise. This page lists rows 1 to 100, from Abstra to Waldium. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Abstra abstra.io | No answer | – | 55 C | – | no | 2026-11-04 | | Airweave airweave.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 78 B | – | no | 2026-11-04 | | Any.do any.do | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | yes | no | 2026-11-04 | | Apollo GraphQL apollographql.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 80 B | – | no | 2026-11-04 | | Artie artie.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Autosana autosana.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Avo avo.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Better Stack betterstack.com | No answer | – | 59 C | – | no | 2026-11-04 | | Bitrise bitrise.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Bolna AI bolna.ai | No answer | – | 63 C | – | no | 2026-11-04 | | Bubble bubble.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 40 D | – | no | 2026-11-04 | | Chonkie chonkie.ai | No answer | – | 43 D | – | no | 2026-11-04 | | Cloudchipr cloudchipr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Cloudglue cloudglue.dev | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Confident AI confident-ai.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 90 A | – | no | 2026-11-04 | | ConfigCat configcat.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 51 C | – | no | 2026-11-04 | | Contentful contentful.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | contentful-cli | 74 B | – | no | 2026-11-04 | | Contentstack contentstack.com | Credential wall API key | – | 67 C | – | no | 2026-11-04 | | Convex convex.dev | Verified no auth; endpoint found by subdomain guess, verified by connecting | convex | 71 B | – | not read | 2026-11-04 | | CORE getcore.me | No answer | – | 55 C | – | no | 2026-11-04 | | Courier courier.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 57 C | – | no | 2026-11-04 | | Coval coval.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 65 C | – | no | 2026-11-04 | | Dedalus Labs dedaluslabs.ai | No answer | – | 85 B | – | no | 2026-11-04 | | DeepSource deepsource.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Depot depot.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Devtron devtron.ai | Credential wall API key | – | 48 C | – | no | 2026-11-04 | | Didit One didit.me | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | – | no | 2026-11-04 | | DigitalOcean digitalocean.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 74 B | – | no | 2026-11-04 | | Docker docker.com | No answer | – | 69 C | – | no | 2026-11-04 | | Draftbit draftbit.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Elementary Data elementary-data.com | No answer | – | 56 C | – | no | 2026-11-04 | | Ellipsis ellipsis.dev | No answer | – | 69 C | – | no | 2026-11-04 | | Embrace embrace.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 38 D | – | no | 2026-11-04 | | Encord encord.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 69 C | – | no | 2026-11-04 | | Flagsmith flagsmith.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 47 D | – | no | 2026-11-04 | | Freestyle freestyle.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | yes | no | 2026-11-04 | | GitBook gitbook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 86 A | – | no | 2026-11-04 | | Glideapps glideapps.com | No answer | – | 64 C | – | no | 2026-11-04 | | Grafana grafana.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Graphcms graphcms.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | GrowthBook growthbook.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | Harness harness.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 75 B | – | no | 2026-11-04 | | HelixDB helix-db.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 82 B | yes | no | 2026-11-04 | | Heroku heroku.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | heroku | 73 B | – | no | 2026-11-04 | | Hexclave hexclave.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 85 B | yes | no | 2026-11-04 | | Honeycomb honeycomb.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | hotglue hotglue.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Hubstaff hubstaff.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | incident.io incident.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 64 C | – | no | 2026-11-04 | | Infracost infracost.io | No answer | – | 50 C | – | no | 2026-11-04 | | Inkeep inkeep.com | No answer | – | 71 B | – | no | 2026-11-04 | | InsForge insforge.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | – | no | 2026-11-04 | | Interfere interfere.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Kinsta® kinsta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Komodor komodor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | LaunchDarkly launchdarkly.com | No answer | – | 69 C | – | no | 2026-11-04 | | LogRocket logrocket.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | ManageEngine manageengine.com | No answer | – | 62 C | – | no | 2026-11-04 | | Manufact manufact.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | yes | no | 2026-11-04 | | Mem mem.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Mezmo mezmo.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | Minicor minicor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | Morph morphllm.com | No answer | – | 82 B | – | no | 2026-11-04 | | Morphik morphik.ai | No answer | – | 70 B | – | no | 2026-11-04 | | Nanonets nanonets.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Northflank northflank.com | Credential wall API key | – | 53 C | – | no | 2026-11-04 | | Onlook onlook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Oximy oximy.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Pantheon pantheon.io | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Plane plane.so | No answer | – | 78 B | yes | no | 2026-11-04 | | Poly poly.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | PropelAuth propelauth.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Redis redis.io | No answer | – | 62 C | – | no | 2026-11-04 | | Replit replit.com | No answer | – | 73 B | – | no | 2026-11-04 | | Runautomat runautomat.com | No answer | – | 65 C | – | no | 2026-11-04 | | Runcaptain runcaptain.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 57 C | – | no | 2026-11-04 | | Runpulse runpulse.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Sazabi sazabi.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Seam seam.co | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 53 C | – | no | 2026-11-04 | | Shortcut shortcut.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | yes | no | 2026-11-04 | | Signadot signadot.com | No answer | – | 68 C | – | no | 2026-11-04 | | Sixtyfour sixtyfour.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | Spike spike.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Stillwind stillwind.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Storyblok storyblok.com | No tools listed | – | 67 C | – | no | 2026-11-04 | | SuperAnnotate superannotate.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 54 C | – | no | 2026-11-04 | | Supernova.io supernova.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Svix svix.com | No answer | – | 69 C | – | no | 2026-11-04 | | Synth AI usesynth.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Tavus tavus.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Tempo tempo.new | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | The Context Company thecontext.company | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 58 C | – | no | 2026-11-04 | | Theneo theneo.io | No answer | – | 67 C | – | no | 2026-11-04 | | TickTick ticktick.com | No answer | – | 61 C | – | no | 2026-11-04 | | Unsiloed AI unsiloed.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Upsolve AI upsolve.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | Uptime.com :) uptime.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 59 C | – | no | 2026-11-04 | | Vanta vanta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Vultr vultr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | Waldium waldium.com | No answer | – | 37 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/guessed/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Found by guess, page 2 | Agent MCP Directory" description: "106 companies whose MCP endpoint was found by guessing an mcp subdomain, then checked by connecting on 4 November 2026. Page 2 of 2." canonical: https://agentmcpdirectory.com/directory/guessed/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Found by guess, page 2 | Agent MCP Directory > 106 companies whose MCP endpoint was found by guessing an mcp subdomain, then checked by connecting on 4 November 2026. Page 2 of 2. Source: https://agentmcpdirectory.com/directory/guessed/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Endpoints found by subdomain guess, page 2 106 rows were found by guessing mcp.: 9 listed tools ("endpoint found by subdomain guess, verified by connecting"), 63 answered with a sign-in challenge and were not verified, and 34 did not answer or answered otherwise. This page lists rows 101 to 106, from WarpBuild to ZeroEval. ## Rows 101 to 106 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | WarpBuild warpbuild.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Workamajig workamajig.com | No answer | – | 62 C | – | no | 2026-11-04 | | Workato workato.com | No answer | – | 64 C | – | no | 2026-11-04 | | Wrike wrike.com | No answer | – | 66 C | – | no | 2026-11-04 | | ZeroEntropy zeroentropy.dev | No answer | – | 73 B | – | no | 2026-11-04 | | ZeroEval zeroeval.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 65 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/guessed/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Gumroad MCP server | Agent MCP Directory" description: "Does Gumroad have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/gumroad-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Gumroad MCP server | Agent MCP Directory > Does Gumroad have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/gumroad-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gumroad: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Gumroad (gumroad.com), so the connector had nothing to connect to. Ora's cached score for gumroad.com is 69, grade C, read on 5 November 2026. The company was added from the shared crawl, which found /.well-known/mcp.json on the domain. ## Fact sheet | Company | Gumroad (registry title: gumroad.com) | | --- | --- | | Domain | gumroad.com | | Category | Commerce Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,924 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for gumroad.com, a vendor-published score) | | Company found through | the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Gumroad. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for gumroad.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Gumroad. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | OAuth authorization server metadata | Found: gumroad.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/gumroad-com/index.md) ## Sources - [Ora score page for gumroad.com](https://ora.ai/score/gumroad.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Where Gumroad was found](https://gumroad.com/.well-known/mcp.json), read 4 November 2026 - [Gumroad website](https://gumroad.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "GuruHotel MCP server | Agent MCP Directory" description: "GuruHotel has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/guruhotel-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # GuruHotel MCP server | Agent MCP Directory > GuruHotel has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/guruhotel-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # GuruHotel: MCP server, CLI and agent surfaces Yes: GuruHotel runs a public MCP server at guruhotel.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: search\_guruhotel\_knowledge, get\_product\_facts, get\_pricing. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for guruhotel.com is 71, grade B, read on 5 November 2026. ## Fact sheet | Company | GuruHotel (registry title: GuruHotel Manager) | | --- | --- | | Domain | guruhotel.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 71, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for guruhotel.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://guruhotel.com/api/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | guruhotel 1.1.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,022 ms over 1 attempt | ### Tools listed 6 tools - search\_guruhotel\_knowledge - get\_product\_facts - get\_pricing - get\_integrations - check\_pms\_compatibility - get\_page\_markdown ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:45Z https://guruhotel.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1857 ms - 20:03:09Z https://guruhotel.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1022 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://guruhotel.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for GuruHotel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.guruhotel/manager, com.guruhotel/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/guruhotel-com/index.md) ## Sources - [Ora score page for guruhotel.com](https://ora.ai/score/guruhotel.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where GuruHotel was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.guruhotel%2Fmanager), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=guruhotel), read 4 November 2026 - [GuruHotel website](https://guruhotel.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Habitica MCP server | Agent MCP Directory" description: "Does Habitica have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/habitica-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Habitica MCP server | Agent MCP Directory > Does Habitica have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/habitica-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Habitica: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Habitica (habitica.com), so the connector had nothing to connect to. Ora's cached score for habitica.com is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Habitica (registry title: habitica.com) | | --- | --- | | Domain | habitica.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 3 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for habitica.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Habitica. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for habitica.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Habitica. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/habitica-com/index.md) ## Sources - [Ora score page for habitica.com](https://ora.ai/score/habitica.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 October 2026, read from GET /api/leaderboard) - [Where Habitica was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Habitica website](https://habitica.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HackerRank MCP server | Agent MCP Directory" description: "Does HackerRank have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hackerrank-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HackerRank MCP server | Agent MCP Directory > Does HackerRank have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hackerrank-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HackerRank: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for HackerRank (hackerrank.com), so the connector had nothing to connect to. Ora's cached score for hackerrank.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | HackerRank (registry title: hackerrank.com) | | --- | --- | | Domain | hackerrank.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hackerrank.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for HackerRank. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hackerrank.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for HackerRank. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hackerrank-com/index.md) ## Sources - [Ora score page for hackerrank.com](https://ora.ai/score/hackerrank.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 October 2026, read from GET /api/leaderboard) - [Where HackerRank was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [HackerRank website](https://hackerrank.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hands for Agents MCP server | Agent MCP Directory" description: "Hands for Agents has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/handsforagents-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hands for Agents MCP server | Agent MCP Directory > Hands for Agents has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/handsforagents-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hands for Agents: MCP server, CLI and agent surfaces Yes: Hands for Agents runs a public MCP server at mcp.handsforagents.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: list\_services, request\_quote, create\_task. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Hands for Agents | | --- | --- | | Domain | handsforagents.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for handsforagents.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.handsforagents.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | handsforagents 1.30.0 | | Capabilities | experimental, tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 692 ms over 1 attempt | ### Tools listed 5 tools - list\_services - request\_quote - create\_task - get\_status - confirm\_delivery ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:46Z https://mcp.handsforagents.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1415 ms - 20:03:09Z https://mcp.handsforagents.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 692 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.handsforagents.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hands for Agents. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.handsforagents/hands | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/handsforagents-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=handsforagents), read 4 November 2026 - [Hands for Agents website](https://handsforagents.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "hardoz MCP server | Agent MCP Directory" description: "hardoz has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/hardoz-eu-cc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # hardoz MCP server | Agent MCP Directory > hardoz has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/hardoz-eu-cc Site: Agent MCP Directory Last reviewed: 2026-11-05 # hardoz: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for hardoz (hardoz.eu.cc), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). ## Fact sheet | Company | hardoz (registry title: hardoz x402 tools) | | --- | --- | | Domain | hardoz.eu.cc | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | No answer | | Tranco rank | 3,323 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for hardoz.eu.cc when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://hardoz.eu.cc/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | HTTP status | 404 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 414 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 no content-type) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:02Z https://hardoz.eu.cc/mcp sent initialize result no-answer (HTTP 404) 429 ms - 20:01:38Z https://hardoz.eu.cc/mcp sent initialize result no-answer (HTTP 404) 414 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://hardoz.eu.cc/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for hardoz. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: cc.eu.hardoz/x402 | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hardoz-eu-cc/index.md) ## Sources - [Where hardoz was found](https://registry.modelcontextprotocol.io/v0/servers?search=cc.eu.hardoz%2Fx402), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hardoz), read 4 November 2026 - [hardoz website](https://hardoz.eu.cc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Harness MCP server | Agent MCP Directory" description: "Harness: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/harness-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Harness MCP server | Agent MCP Directory > Harness: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/harness-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Harness: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Harness; the connector's guess at mcp.harness.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Harness (registry title: harness.io) | | --- | --- | | Domain | harness.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 8,533 on the list of 4 November 2026 | | Ora score | 75, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for harness.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.harness.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,270 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:15Z https://mcp.harness.io/mcp sent initialize result auth-required (HTTP 401) 1226 ms - 20:01:54Z https://mcp.harness.io/mcp sent initialize result auth-required (HTTP 401) 1270 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.harness.io | | Authorization server metadata | id.harness.io | | Registration endpoint | https://id.harness.io/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.harness.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.harness.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://id.harness.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Harness. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/harness-io/index.md) ## Sources - [Ora score page for harness.io](https://ora.ai/score/harness.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Harness was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Harness website](https://harness.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HARVEST.com MCP server | Agent MCP Directory" description: "Does HARVEST.com have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/harvest-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HARVEST.com MCP server | Agent MCP Directory > Does HARVEST.com have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/harvest-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HARVEST.com: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for HARVEST.com (harvest.com), so the connector had nothing to connect to. Ora's cached score for harvest.com is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | HARVEST.com | | --- | --- | | Domain | harvest.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for harvest.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for HARVEST.com. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for harvest.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for HARVEST.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/harvest-com/index.md) ## Sources - [Ora score page for harvest.com](https://ora.ai/score/harvest.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where HARVEST.com was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [HARVEST.com website](https://harvest.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HasData MCP server | Agent MCP Directory" description: "HasData has an open MCP server with 68 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hasdata-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HasData MCP server | Agent MCP Directory > HasData has an open MCP server with 68 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hasdata-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HasData: MCP server, CLI and agent surfaces Yes: HasData runs a public MCP server at mcp.hasdata.com that listed 68 tools to a client with no credentials on 4 November 2026. Examples: hasdata\_airbnb\_listing\_getAirbnbListings, hasdata\_airbnb\_property\_getAirbnbPropertyDetails, hasdata\_amazon\_product\_getProductDetails. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | HasData | | --- | --- | | Domain | hasdata.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for hasdata.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hasdata.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | hasdata-mcp-api-server 1.0.0 | | Capabilities | prompts, resources, tools | | Tools | 68 | | Resources | 151 | | Prompts | 20 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 4,250 ms over 1 attempt | ### Tools listed 68 tools; the first 40 names are recorded - hasdata\_airbnb\_listing\_getAirbnbListings - hasdata\_airbnb\_property\_getAirbnbPropertyDetails - hasdata\_amazon\_product\_getProductDetails - hasdata\_amazon\_reviews\_getProductReviews - hasdata\_amazon\_search\_getSearchResults - hasdata\_amazon\_seller\_getSellerDetails - hasdata\_amazon\_seller\_products\_getSellerProducts - hasdata\_bing\_serp\_getSearchResults - hasdata\_booking\_place\_getBookingPlaceDetails - hasdata\_booking\_search\_getBookingSearchResults - hasdata\_chatgpt\_chat\_getChatgptAnswer - hasdata\_duckduckgo\_serp\_getSearchResults - hasdata\_facebook\_profile\_getFacebookProfile - hasdata\_glassdoor\_job\_getJobDetails - hasdata\_glassdoor\_listing\_getJobListings - hasdata\_google\_images\_images\_getImageSearchResults - hasdata\_google\_maps\_contributor\_reviews\_getMapReviews - hasdata\_google\_maps\_photos\_getMapPhotos - hasdata\_google\_maps\_place\_getPlaceDetails - hasdata\_google\_maps\_posts\_getMapPosts - hasdata\_google\_maps\_reviews\_getMapReviews - hasdata\_google\_maps\_search\_performMapSearch - hasdata\_google\_scholar\_case\_law\_getScholarCaseLawOpinion - hasdata\_google\_scholar\_cite\_getScholarCitationFormats - hasdata\_google\_scholar\_scholar\_getScholarSearchResults - hasdata\_google\_serp\_ai\_mode\_getAiModeResponse - hasdata\_google\_serp\_ai\_overview\_getAiOverviewResponse - hasdata\_google\_serp\_events\_getEventInformation - hasdata\_google\_serp\_immersive\_product\_getImmersive\_e29f691177 - hasdata\_google\_serp\_news\_getGoogleNews - hasdata\_google\_serp\_product\_getProductInformation - hasdata\_google\_serp\_serp\_getSearchResults - hasdata\_google\_serp\_serp\_light\_getSearchResults - hasdata\_google\_serp\_shopping\_getSearchResults - hasdata\_google\_serp\_short\_videos\_getShortVideosSearchResults - hasdata\_google\_travel\_flights\_getGoogleFlights - hasdata\_google\_travel\_flights\_deals\_getGoogleFlightsDeals - hasdata\_google\_travel\_hotels\_getGoogleHotels - hasdata\_google\_trends\_search\_getTrendsData - hasdata\_indeed\_job\_getJobDetails ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:50Z https://mcp.hasdata.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 4483 ms - 20:03:13Z https://mcp.hasdata.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 4250 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.hasdata.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for HasData. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.hasdata/airbnb, com.hasdata/amazon, com.hasdata/bing and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hasdata-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hasdata), read 4 November 2026 - [HasData website](https://hasdata.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HashiCorp MCP server | Agent MCP Directory" description: "Does HashiCorp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hashicorp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HashiCorp MCP server | Agent MCP Directory > Does HashiCorp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hashicorp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HashiCorp: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for HashiCorp (hashicorp.com), so the connector had nothing to connect to. Ora's cached score for hashicorp.com is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | HashiCorp | | --- | --- | | Domain | hashicorp.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 4,671 on the list of 4 November 2026 | | Ora score | 60, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hashicorp.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for HashiCorp. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hashicorp.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for HashiCorp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hashicorp-com/index.md) ## Sources - [Ora score page for hashicorp.com](https://ora.ai/score/hashicorp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/score) - [Where HashiCorp was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hasura MCP server | Agent MCP Directory" description: "Does Hasura have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hasura-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hasura MCP server | Agent MCP Directory > Does Hasura have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hasura-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hasura: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hasura (hasura.io), so the connector had nothing to connect to. Ora's cached score for hasura.io is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hasura | | --- | --- | | Domain | hasura.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 19 July 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hasura.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hasura. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hasura.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hasura. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hasura-io/index.md) ## Sources - [Ora score page for hasura.io](https://ora.ai/score/hasura.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 July 2026, read from GET /api/leaderboard) - [Where Hasura was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hasura website](https://hasura.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hatchet MCP server | Agent MCP Directory" description: "Does Hatchet have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hatchet-run site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hatchet MCP server | Agent MCP Directory > Does Hatchet have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hatchet-run Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hatchet: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hatchet (hatchet.run), so the connector had nothing to connect to. Ora's cached score for hatchet.run is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hatchet (registry title: hatchet.run) | | --- | --- | | Domain | hatchet.run | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hatchet.run, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hatchet. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hatchet.run, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hatchet. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hatchet-run/index.md) ## Sources - [Ora score page for hatchet.run](https://ora.ai/score/hatchet.run?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where Hatchet was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hatchet website](https://hatchet.run), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Haystackeditor MCP server | Agent MCP Directory" description: "Does Haystackeditor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/haystackeditor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Haystackeditor MCP server | Agent MCP Directory > Does Haystackeditor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/haystackeditor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Haystackeditor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Haystackeditor (haystackeditor.com), so the connector had nothing to connect to. Ora's cached score for haystackeditor.com is 44, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Haystackeditor (registry title: haystackeditor.com) | | --- | --- | | Domain | haystackeditor.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 44, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for haystackeditor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Haystackeditor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for haystackeditor.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Haystackeditor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/haystackeditor-com/index.md) ## Sources - [Ora score page for haystackeditor.com](https://ora.ai/score/haystackeditor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Haystackeditor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Haystackeditor website](https://haystackeditor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hcti MCP server | Agent MCP Directory" description: "Hcti: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hcti-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hcti MCP server | Agent MCP Directory > Hcti: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hcti-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hcti: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Hcti at mcp.hcti.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hcti (registry title: HTML/CSS to Image API) | | --- | --- | | Domain | hcti.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for hcti.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hcti.io | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,491 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:48Z https://mcp.hcti.io sent initialize result auth-required (HTTP 401) 1819 ms - 20:03:11Z https://mcp.hcti.io sent initialize result auth-required (HTTP 401) 1491 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.hcti.io/.well-known/oauth-protected-resource/" | | Protected resource metadata | mcp.hcti.io | | Authorization server metadata | htmlcsstoimage.com | | Registration endpoint | https://htmlcsstoimage.com/account/mcp_register | ### The sign-in route, step by step 1. Request `https://mcp.hcti.io` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.hcti.io/.well-known/oauth-protected-resource/` to find the authorization server. 3. Register a client at the registration endpoint `https://htmlcsstoimage.com/account/mcp_register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hcti. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hcti-io/index.md) ## Sources - [Hcti website](https://hcti.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Healthline MCP server | Agent MCP Directory" description: "Does Healthline have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/healthline-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Healthline MCP server | Agent MCP Directory > Does Healthline have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/healthline-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Healthline: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Healthline (healthline.com), so the connector had nothing to connect to. Ora's cached score for healthline.com is 75, grade B, read on 5 November 2026. The company was added from the shared crawl, which found /.well-known/mcp.json on the domain. ## Fact sheet | Company | Healthline (registry title: healthline.com) | | --- | --- | | Domain | healthline.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | None found | | Tranco rank | 1,048 on the list of 4 November 2026 | | Ora score | 75, grade B; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for healthline.com, a vendor-published score) | | Company found through | the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Healthline. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for healthline.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Healthline. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card (older path) | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/healthline-com/index.md) ## Sources - [Ora score page for healthline.com](https://ora.ai/score/healthline.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/score) - [Where Healthline was found](https://healthline.com/.well-known/mcp.json), read 4 November 2026 - [Healthline website](https://healthline.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Helena MCP server | Agent MCP Directory" description: "Helena has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/helena-bio site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Helena MCP server | Agent MCP Directory > Helena has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/helena-bio Site: Agent MCP Directory Last reviewed: 2026-11-05 # Helena: MCP server, CLI and agent surfaces Yes: Helena runs a public MCP server at api.helena.bio that listed 7 tools to a client with no credentials on 4 November 2026. Examples: search\_biomedical\_literature, get\_publication\_details, get\_work\_details. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Helena (registry title: Folklore Clinical Variant Interpretation MCP) | | --- | --- | | Domain | helena.bio | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for helena.bio when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.helena.bio/noodle/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | noodle 0.2.1 | | Capabilities | experimental, prompts, resources, tools | | Tools | 7 | | Resources | 1 | | Prompts | 4 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,107 ms over 1 attempt | ### Tools listed 7 tools - search\_biomedical\_literature - get\_publication\_details - get\_work\_details - get\_publication\_neighborhood - get\_work\_neighborhood - get\_corpus\_summary - support\_helena ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:47Z https://api.helena.bio/noodle/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1248 ms - 20:03:11Z https://api.helena.bio/noodle/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1107 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.helena.bio/noodle/v1/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Helena. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/helena-bio/index.md) ## Sources - [Helena website](https://helena.bio), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HelixDB MCP server | Agent MCP Directory" description: "HelixDB: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/helix-db-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HelixDB MCP server | Agent MCP Directory > HelixDB: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/helix-db-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HelixDB: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for HelixDB; the connector's guess at mcp.helix-db.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | HelixDB (registry title: helix-db.com) | | --- | --- | | Domain | helix-db.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 82, grade B; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for helix-db.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.helix-db.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,736 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:48Z https://mcp.helix-db.com/mcp sent initialize result auth-required (HTTP 401) 1706 ms - 20:03:11Z https://mcp.helix-db.com/mcp sent initialize result auth-required (HTTP 401) 1736 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.helix-db.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.helix-db.com | | Authorization server metadata | enlightened-discussion-01.authkit.app | | Registration endpoint | https://enlightened-discussion-01.authkit.app/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.helix-db.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.helix-db.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://enlightened-discussion-01.authkit.app/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for HelixDB. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.helix-db.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/helix-db-com/index.md) ## Sources - [Ora score page for helix-db.com](https://ora.ai/score/helix-db.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where HelixDB was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [HelixDB website](https://helix-db.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HemmaBo MCP server | Agent MCP Directory" description: "HemmaBo has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hemmabo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HemmaBo MCP server | Agent MCP Directory > HemmaBo has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hemmabo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HemmaBo: MCP server, CLI and agent surfaces Yes: HemmaBo runs a public MCP server at www.hemmabo.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: hemmabo\_search\_properties, hemmabo\_check\_availability, hemmabo\_check\_host\_readiness. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | HemmaBo (registry title: HemmaBo Host Booking Engine) | | --- | --- | | Domain | hemmabo.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for hemmabo.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.hemmabo.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | hemmabo-mcp-server 7.0.12 | | Capabilities | tools, prompts, resources | | Tools | 6 | | Resources | 1 | | Prompts | 2 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,642 ms over 1 attempt | ### Tools listed 6 tools - hemmabo\_search\_properties - hemmabo\_check\_availability - hemmabo\_check\_host\_readiness - hemmabo\_get\_host\_onboarding\_link - vrp\_verify\_node - vrp\_get\_verified\_stay\_offer ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:48Z https://www.hemmabo.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1716 ms - 20:03:11Z https://www.hemmabo.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1642 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.hemmabo.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for HemmaBo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.hemmabo/hemmabo-mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hemmabo-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hemmabo), read 4 November 2026 - [HemmaBo website](https://hemmabo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hermoso MCP server | Agent MCP Directory" description: "Hermoso: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/hermoso-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hermoso MCP server | Agent MCP Directory > Hermoso: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/hermoso-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hermoso: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Hermoso at app.hermoso.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hermoso | | --- | --- | | Domain | hermoso.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 69, grade C; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hermoso.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.hermoso.ai/mcp?src=registry | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 809 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:47Z https://app.hermoso.ai/mcp?src=registry sent initialize result auth-required (HTTP 401) 822 ms - 20:03:11Z https://app.hermoso.ai/mcp?src=registry sent initialize result auth-required (HTTP 401) 809 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.hermoso.ai/.well-known/oauth-protected-resource", scope="hermoso.research hermoso.generate" | | Protected resource metadata | app.hermoso.ai | | Authorization server metadata | app.hermoso.ai | | Registration endpoint | https://app.hermoso.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://app.hermoso.ai/mcp?src=registry` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.hermoso.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.hermoso.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hermoso. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: hermoso.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hermoso-ai/index.md) ## Sources - [Ora score page for hermoso.ai](https://ora.ai/score/hermoso.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [Where Hermoso was found](https://github.com/mcp/hermoso-ai/hermoso), read 4 November 2026 - [Hermoso website](https://hermoso.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Heroku MCP server | Agent MCP Directory" description: "Heroku: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/heroku-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Heroku MCP server | Agent MCP Directory > Heroku: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/heroku-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Heroku: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Heroku; the connector's guess at mcp.heroku.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Heroku | | --- | --- | | Domain | heroku.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 5,541 on the list of 4 November 2026 | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for heroku.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.heroku.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,412 ms over 1 attempt | | Documentation | devcenter.heroku.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:08Z https://mcp.heroku.com/mcp sent initialize result auth-required (HTTP 401) 1241 ms - 20:01:46Z https://mcp.heroku.com/mcp sent initialize result auth-required (HTTP 401) 1412 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header" | | Protected resource metadata | mcp.heroku.com | | Authorization server metadata | mcp.heroku.com | | Registration endpoint | https://mcp.heroku.com/reg | ### The sign-in route, step by step 1. Request `https://mcp.heroku.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.heroku.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.heroku.com/reg` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | heroku on npm (page) | | --- | --- | | Exists | yes | | Latest version | 11.12.1 | | Last publish | 22 October 2026 | | Command names | heroku | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/heroku-com/index.md) ## Sources - [Heroku MCP documentation](https://devcenter.heroku.com/articles/heroku-mcp-server), read 4 November 2026 - [Ora score page for heroku.com](https://ora.ai/score/heroku.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Heroku website](https://heroku.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HeroUI MCP server | Agent MCP Directory" description: "Does HeroUI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/heroui-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HeroUI MCP server | Agent MCP Directory > Does HeroUI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/heroui-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HeroUI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for HeroUI (heroui.com), so the connector had nothing to connect to. Ora's cached score for heroui.com is 81, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | HeroUI (registry title: heroui.com) | | --- | --- | | Domain | heroui.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 81, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for heroui.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for HeroUI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for heroui.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for HeroUI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: heroui.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: heroui.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/heroui-com/index.md) ## Sources - [Ora score page for heroui.com](https://ora.ai/score/heroui.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where HeroUI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [HeroUI website](https://heroui.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HetrixTools MCP server | Agent MCP Directory" description: "Does HetrixTools have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hetrixtools-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HetrixTools MCP server | Agent MCP Directory > Does HetrixTools have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hetrixtools-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HetrixTools: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for HetrixTools (hetrixtools.com), so the connector had nothing to connect to. Ora's cached score for hetrixtools.com is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | HetrixTools (registry title: hetrixtools.com) | | --- | --- | | Domain | hetrixtools.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hetrixtools.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for HetrixTools. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hetrixtools.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for HetrixTools. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hetrixtools-com/index.md) ## Sources - [Ora score page for hetrixtools.com](https://ora.ai/score/hetrixtools.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 September 2026, read from GET /api/leaderboard) - [Where HetrixTools was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [HetrixTools website](https://hetrixtools.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hetzner MCP server | Agent MCP Directory" description: "Does Hetzner have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hetzner-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hetzner MCP server | Agent MCP Directory > Does Hetzner have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hetzner-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hetzner: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hetzner (hetzner.com), so the connector had nothing to connect to. Ora's cached score for hetzner.com is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hetzner | | --- | --- | | Domain | hetzner.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 1,913 on the list of 4 November 2026 | | Ora score | 50, grade C; Ora scanned the domain on 18 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hetzner.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hetzner. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hetzner.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hetzner. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hetzner-com/index.md) ## Sources - [Ora score page for hetzner.com](https://ora.ai/score/hetzner.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 September 2026, read from GET /api/score) - [Where Hetzner was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hetzner website](https://hetzner.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hexclave MCP server | Agent MCP Directory" description: "Hexclave has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hexclave-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hexclave MCP server | Agent MCP Directory > Hexclave has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hexclave-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hexclave: MCP server, CLI and agent surfaces Yes: Hexclave runs a public MCP server at mcp.hexclave.com, found by guessing the subdomain, and it listed 2 tools to a client with no credentials on 4 November 2026. Examples: ask\_hexclave, give\_feedback. It speaks streamable-http, protocol 2025-06-18. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | Hexclave | | --- | --- | | Domain | hexclave.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 85, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hexclave.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hexclave.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | hexclave-mcp 1.0.135 | | Capabilities | resources, completions, prompts, tools | | Tools | 2 | | Resources | 1 | | Prompts | 1 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,449 ms over 1 attempt | ### Tools listed 2 tools - ask\_hexclave - give\_feedback ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:49Z https://mcp.hexclave.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1365 ms - 20:03:12Z https://mcp.hexclave.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1449 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.hexclave.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hexclave. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.hexclave.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: hexclave.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hexclave-com/index.md) ## Sources - [Ora score page for hexclave.com](https://ora.ai/score/hexclave.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Where Hexclave was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hexclave website](https://hexclave.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hiro MCP server | Agent MCP Directory" description: "Does Hiro have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/hiro-so site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hiro MCP server | Agent MCP Directory > Does Hiro have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/hiro-so Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hiro: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hiro (hiro.so), so the connector had nothing to connect to. Ora's cached score for hiro.so is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hiro (registry title: hiro.so) | | --- | --- | | Domain | hiro.so | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hiro.so, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hiro. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hiro.so, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hiro. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hiro-so/index.md) ## Sources - [Ora score page for hiro.so](https://ora.ai/score/hiro.so?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/leaderboard) - [Where Hiro was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hiro website](https://hiro.so), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hitsteps MCP server | Agent MCP Directory" description: "Hitsteps: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/hitsteps-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hitsteps MCP server | Agent MCP Directory > Hitsteps: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/hitsteps-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hitsteps: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Hitsteps at www.hitsteps.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hitsteps (registry title: Hitsteps Analytics and Operations) | | --- | --- | | Domain | hitsteps.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for hitsteps.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.hitsteps.com/mcp/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 560 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:49Z https://www.hitsteps.com/mcp/ sent initialize result auth-required (HTTP 401) 702 ms - 20:03:11Z https://www.hitsteps.com/mcp/ sent initialize result auth-required (HTTP 401) 560 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Hitsteps MCP", resource_metadata="https://www.hitsteps.com/.well-known/oauth-protected-resource/mcp/", scope="analytics:read sites:write goals:write labels:write uptime:write alerts:read alerts:write chat:read chat:write mentions:read mentions:write" | | Protected resource metadata | www.hitsteps.com | | Authorization server metadata | www.hitsteps.com | | Registration endpoint | https://www.hitsteps.com/mcp/oauth/register.php | ### The sign-in route, step by step 1. Request `https://www.hitsteps.com/mcp/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.hitsteps.com/.well-known/oauth-protected-resource/mcp/` to find the authorization server. 3. Register a client at the registration endpoint `https://www.hitsteps.com/mcp/oauth/register.php` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hitsteps. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.hitsteps/analytics-operations | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hitsteps-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hitsteps), read 4 November 2026 - [Hitsteps website](https://hitsteps.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hive MCP server | Agent MCP Directory" description: "Does Hive have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/hive-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hive MCP server | Agent MCP Directory > Does Hive have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/hive-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hive: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hive (hive.com), so the connector had nothing to connect to. Ora's cached score for hive.com is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hive (registry title: hive.com) | | --- | --- | | Domain | hive.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 13 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hive.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hive. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hive.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hive. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hive-com/index.md) ## Sources - [Ora score page for hive.com](https://ora.ai/score/hive.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 13 October 2026, read from GET /api/leaderboard) - [Where Hive was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hive website](https://hive.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hive Intelligence MCP server | Agent MCP Directory" description: "Hive Intelligence has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hiveintelligence-xyz site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hive Intelligence MCP server | Agent MCP Directory > Hive Intelligence has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hiveintelligence-xyz Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hive Intelligence: MCP server, CLI and agent surfaces Yes: Hive Intelligence runs a public MCP server at hiveintelligence.xyz that listed 8 tools to a client with no credentials on 4 November 2026. Examples: get\_token\_price, check\_token\_safety, get\_wallet\_portfolio. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Hive Intelligence | | --- | --- | | Domain | hiveintelligence.xyz | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for hiveintelligence.xyz when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://hiveintelligence.xyz/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | hive-mcp-server 1.17.1 | | Capabilities | tools, resources, prompts, completions | | Tools | 8 | | Resources | 7 | | Prompts | 3 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 4,167 ms over 1 attempt | ### Tools listed 8 tools - get\_token\_price - check\_token\_safety - get\_wallet\_portfolio - search\_tools - get\_api\_endpoint\_schema - invoke\_api\_endpoint - invoke\_stateful\_endpoint - validate\_task\_result ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:53Z https://hiveintelligence.xyz/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 5128 ms - 20:03:16Z https://hiveintelligence.xyz/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 4167 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | OAuth 2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://hiveintelligence.xyz/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hive Intelligence. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hiveintelligence-xyz/index.md) ## Sources - [Where Hive Intelligence was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Hive Intelligence website](https://hiveintelligence.xyz), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Honeybadger MCP server | Agent MCP Directory" description: "Does Honeybadger have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/honeybadger-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Honeybadger MCP server | Agent MCP Directory > Does Honeybadger have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/honeybadger-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Honeybadger: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Honeybadger (honeybadger.io), so the connector had nothing to connect to. Ora's cached score for honeybadger.io is 72, grade B, read on 5 November 2026. The company was added from the GitHub MCP Registry. ## Fact sheet | Company | Honeybadger | | --- | --- | | Domain | honeybadger.io | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for honeybadger.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Honeybadger. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for honeybadger.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | Listed | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Honeybadger. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/honeybadger-io/index.md) ## Sources - [Ora score page for honeybadger.io](https://ora.ai/score/honeybadger.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Honeybadger website](https://honeybadger.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Honeycomb MCP server | Agent MCP Directory" description: "Honeycomb: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/honeycomb-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Honeycomb MCP server | Agent MCP Directory > Honeycomb: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/honeycomb-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Honeycomb: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Honeycomb; the connector's guess at mcp.honeycomb.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Honeycomb | | --- | --- | | Domain | honeycomb.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 79, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for honeycomb.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.honeycomb.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,761 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:50Z https://mcp.honeycomb.io/mcp sent initialize result auth-required (HTTP 401) 1847 ms - 20:03:14Z https://mcp.honeycomb.io/mcp sent initialize result auth-required (HTTP 401) 1761 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.honeycomb.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.honeycomb.io | | Authorization server metadata | ui.honeycomb.io | | Registration endpoint | https://ui.honeycomb.io/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.honeycomb.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.honeycomb.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://ui.honeycomb.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Honeycomb. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/honeycomb-io/index.md) ## Sources - [Ora score page for honeycomb.io](https://ora.ai/score/honeycomb.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Honeycomb was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Honeycomb website](https://honeycomb.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hookpulse MCP server | Agent MCP Directory" description: "Hookpulse has an open MCP server with 30 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hookpulse-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hookpulse MCP server | Agent MCP Directory > Hookpulse has an open MCP server with 30 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hookpulse-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hookpulse: MCP server, CLI and agent surfaces Yes: Hookpulse runs a public MCP server at hookpulse.net that listed 30 tools to a client with no credentials on 4 November 2026. Examples: list\_plans, buy\_plan, cancel\_plan. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Hookpulse | | --- | --- | | Domain | hookpulse.net | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for hookpulse.net when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://hookpulse.net/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | HookPulse fb0c5518 | | Capabilities | tools, prompts | | Tools | 30 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,037 ms over 1 attempt | ### Tools listed 30 tools - list\_plans - buy\_plan - cancel\_plan - api\_index - health - create\_guest - list\_endpoints - create\_endpoint - create\_site - check\_site - list\_sites - import\_crontab - get\_endpoint - delete\_endpoint - list\_events - ping\_ingest - signal\_start - signal\_fail - signal\_exit\_code - ingest\_key - ingest\_key\_rotate - ping\_slug - signal\_slug - billing - status\_feed\_url - status\_feed\_rotate - list\_templates - contact - pricing - get\_api\_x402\_check ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:51Z https://hookpulse.net/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2380 ms - 20:03:14Z https://hookpulse.net/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2037 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://hookpulse.net/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hookpulse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: hookpulse.net (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hookpulse-net/index.md) ## Sources - [Hookpulse website](https://hookpulse.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hookstep MCP server | Agent MCP Directory" description: "Hookstep: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/hookstep-in site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hookstep MCP server | Agent MCP Directory > Hookstep: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/hookstep-in Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hookstep: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Hookstep at hookpost.hookstep.in asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Hookstep (registry title: Hookpost) | | --- | --- | | Domain | hookstep.in | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for hookstep.in when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://hookpost.hookstep.in/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,781 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:51Z https://hookpost.hookstep.in/api/mcp sent initialize result auth-required-no-oauth (HTTP 401) 2044 ms - 20:03:14Z https://hookpost.hookstep.in/api/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1781 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://hookpost.hookstep.in/api/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hookstep. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: in.hookstep/hookpost | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hookstep-in/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hookstep), read 4 November 2026 - [Hookstep website](https://hookstep.in), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "hoop.dev MCP server | Agent MCP Directory" description: "Does hoop.dev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hoop-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # hoop.dev MCP server | Agent MCP Directory > Does hoop.dev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hoop-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # hoop.dev: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for hoop.dev, so the connector had nothing to connect to. Ora's cached score for hoop.dev is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | hoop.dev | | --- | --- | | Domain | hoop.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 8 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hoop.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for hoop.dev. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hoop.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for hoop.dev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hoop-dev/index.md) ## Sources - [Ora score page for hoop.dev](https://ora.ai/score/hoop.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 August 2026, read from GET /api/leaderboard) - [Where hoop.dev was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [hoop.dev website](https://hoop.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hostinger MCP server | Agent MCP Directory" description: "Hostinger: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/hostinger-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hostinger MCP server | Agent MCP Directory > Hostinger: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/hostinger-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hostinger: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Hostinger at mcp.hostinger.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hostinger | | --- | --- | | Domain | hostinger.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 1,845 on the list of 4 November 2026 | | Ora score | 96, grade A+; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hostinger.com, a vendor-published score) | | Company found through | the vendor's own documentation; the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hostinger.com | | --- | --- | | How it was found | listed in the vendor's own documentation; the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 320 ms over 1 attempt | | Documentation | github.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.hostinger.com sent initialize result auth-required (HTTP 401) 328 ms - 20:01:33Z https://mcp.hostinger.com sent initialize result auth-required (HTTP 401) 320 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.hostinger.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.hostinger.com | | Authorization server metadata | auth.hostinger.com | | Registration endpoint | https://auth.hostinger.com/api/external/v1/oauth-server/register | ### The sign-in route, step by step 1. Request `https://mcp.hostinger.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.hostinger.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.hostinger.com/api/external/v1/oauth-server/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hostinger. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: hostinger.com (JSON, via the shared crawl). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: hostinger.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hostinger-com/index.md) ## Sources - [Hostinger MCP documentation](https://github.com/hostinger/api-mcp-server), read 4 November 2026 - [Ora score page for hostinger.com](https://ora.ai/score/hostinger.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Hostinger website](https://hostinger.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "hotglue MCP server | Agent MCP Directory" description: "hotglue has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hotglue-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # hotglue MCP server | Agent MCP Directory > hotglue has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hotglue-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # hotglue: MCP server, CLI and agent surfaces Yes: hotglue runs a public MCP server at mcp.hotglue.com, found by guessing the subdomain, and it listed 2 tools to a client with no credentials on 4 November 2026. Examples: create\_v2\_job, get\_job\_status. It speaks streamable-http, protocol 2025-11-25. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | hotglue (registry title: hotglue.com) | | --- | --- | | Domain | hotglue.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 58, grade C; Ora scanned the domain on 10 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hotglue.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hotglue.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Hotglue Admin 2.14.7 | | Capabilities | experimental, prompts, resources, tools, tasks | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,037 ms over 1 attempt | ### Tools listed 2 tools - create\_v2\_job - get\_job\_status ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:58Z https://mcp.hotglue.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 8862 ms - 20:03:15Z https://mcp.hotglue.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2037 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.hotglue.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for hotglue. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hotglue-com/index.md) ## Sources - [Ora score page for hotglue.com](https://ora.ai/score/hotglue.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 September 2026, read from GET /api/score) - [Where hotglue was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [hotglue website](https://hotglue.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HubSpot MCP server | Agent MCP Directory" description: "HubSpot: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hubspot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HubSpot MCP server | Agent MCP Directory > HubSpot: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hubspot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # HubSpot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for HubSpot at mcp.hubspot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | HubSpot | | --- | --- | | Domain | hubspot.com | | Category | CRM (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Tranco rank | 259 on the list of 4 November 2026 | | Ora score | 72, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hubspot.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hubspot.com | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 742 ms over 1 attempt | | Documentation | developers.hubspot.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:53Z https://mcp.hubspot.com sent initialize result auth-required (HTTP 401) 632 ms - 20:01:28Z https://mcp.hubspot.com sent initialize result auth-required (HTTP 401) 742 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.hubspot.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.hubspot.com | | Authorization server metadata | mcp.hubspot.com | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.hubspot.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://mcp.hubspot.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @hubspot/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 8.18.0 | | Last publish | 27 October 2026 | | Command names | hs, hscms | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hubspot-com/index.md) ## Sources - [HubSpot MCP documentation](https://developers.hubspot.com/mcp), read 4 November 2026 - [Ora score page for hubspot.com](https://ora.ai/score/hubspot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [HubSpot website](https://hubspot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hubstaff MCP server | Agent MCP Directory" description: "Hubstaff: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/hubstaff-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hubstaff MCP server | Agent MCP Directory > Hubstaff: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/hubstaff-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hubstaff: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Hubstaff; the connector's guess at mcp.hubstaff.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hubstaff (registry title: hubstaff.com) | | --- | --- | | Domain | hubstaff.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 45, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hubstaff.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hubstaff.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 869 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:50Z https://mcp.hubstaff.com/mcp sent initialize result auth-required (HTTP 401) 1020 ms - 20:03:14Z https://mcp.hubstaff.com/mcp sent initialize result auth-required (HTTP 401) 869 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.hubstaff.com/.well-known/oauth-protected-resource", scope="hubstaff:read" | | Protected resource metadata | mcp.hubstaff.com | | Authorization server metadata | account.hubstaff.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.hubstaff.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.hubstaff.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hubstaff. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hubstaff-com/index.md) ## Sources - [Ora score page for hubstaff.com](https://ora.ai/score/hubstaff.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Hubstaff was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hubstaff website](https://hubstaff.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Huddo MCP server | Agent MCP Directory" description: "Huddo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/huddo-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Huddo MCP server | Agent MCP Directory > Huddo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/huddo-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Huddo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Huddo at mcp.huddo.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Huddo | | --- | --- | | Domain | huddo.ai | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for huddo.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.huddo.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,032 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:52Z https://mcp.huddo.ai/mcp sent initialize result auth-required (HTTP 401) 1465 ms - 20:03:15Z https://mcp.huddo.ai/mcp sent initialize result auth-required (HTTP 401) 1032 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.huddo.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.huddo.ai | | Authorization server metadata | mcp.huddo.ai | | Registration endpoint | https://mcp.huddo.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.huddo.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.huddo.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.huddo.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Huddo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.huddo/huddo | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/huddo-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=huddo), read 4 November 2026 - [Huddo website](https://huddo.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hugging Face MCP server | Agent MCP Directory" description: "Hugging Face has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/huggingface-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hugging Face MCP server | Agent MCP Directory > Hugging Face has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/huggingface-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hugging Face: MCP server, CLI and agent surfaces Yes: Hugging Face runs a public MCP server at huggingface.co that listed 4 tools to a client with no credentials on 4 November 2026. Examples: hf\_whoami, hub\_repo\_search, hub\_repo\_details. It speaks streamable-http, protocol 2025-11-25. A CLI is on record: huggingface\_hub on pypi. ## Fact sheet | Company | Hugging Face | | --- | --- | | Domain | huggingface.co | | Category | AI & ML (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 1,076 on the list of 4 November 2026 | | Ora score | 82, grade B; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for huggingface.co, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://huggingface.co/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | huggingface.co/mcp 0.4.33 | | Capabilities | tools, resources, extensions | | Tools | 4 | | Resources | 158 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 674 ms over 1 attempt | | Documentation | huggingface.co | ### Tools listed 4 tools - hf\_whoami - hub\_repo\_search - hub\_repo\_details - hf\_fs ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:56Z https://huggingface.co/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 680 ms - 20:01:32Z https://huggingface.co/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 674 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://huggingface.co/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | huggingface_hub on pypi (page) | | --- | --- | | Exists | yes | | Latest version | 2.4.0 | | Last publish | 29 October 2026 | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: huggingface.co/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.huggingface/hf-mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/huggingface-co/index.md) ## Sources - [Hugging Face MCP documentation](https://huggingface.co/docs/hub/en/hf-mcp-server), read 4 November 2026 - [huggingface\_hub on pypi](https://pypi.org/project/huggingface_hub/), read 4 November 2026 - [Ora score page for huggingface.co](https://ora.ai/score/huggingface.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=huggingface), read 4 November 2026 - [Hugging Face website](https://huggingface.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HVTracker MCP server | Agent MCP Directory" description: "HVTracker has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hvtracker-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HVTracker MCP server | Agent MCP Directory > HVTracker has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/hvtracker-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # HVTracker: MCP server, CLI and agent surfaces Yes: HVTracker runs a public MCP server at hvtracker.net that listed 8 tools to a client with no credentials on 4 November 2026. Examples: check\_agent\_trust, verify\_mcp\_server, compare\_agents. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | HVTracker (registry title: HVTracker MCP) | | --- | --- | | Domain | hvtracker.net | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for hvtracker.net when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://hvtracker.net/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | hvtracker 0.4.0 | | Capabilities | prompts, resources, tools | | Tools | 8 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,436 ms over 1 attempt | ### Tools listed 8 tools - check\_agent\_trust - verify\_mcp\_server - compare\_agents - search\_agents - scan\_stack - list\_categories - get\_leaderboard - get\_agent\_history ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:53Z https://hvtracker.net/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1892 ms - 20:03:15Z https://hvtracker.net/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1436 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://hvtracker.net/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for HVTracker. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hvtracker-net/index.md) ## Sources - [Where HVTracker was found](https://github.com/mcp/YugantM/hvtracker-mcp), read 4 November 2026 - [HVTracker website](https://hvtracker.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hydrant MCP server | Agent MCP Directory" description: "Hydrant: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/hydrant-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hydrant MCP server | Agent MCP Directory > Hydrant: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/hydrant-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hydrant: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Hydrant at hydrant.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hydrant | | --- | --- | | Domain | hydrant.dev | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for hydrant.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://hydrant.dev/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 861 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:52Z https://hydrant.dev/api/mcp sent initialize result auth-required (HTTP 401) 1072 ms - 20:03:16Z https://hydrant.dev/api/mcp sent initialize result auth-required (HTTP 401) 861 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://hydrant.dev/.well-known/oauth-protected-resource/api/mcp", scope="workspace.read workspace.write offline_access" | | Protected resource metadata | hydrant.dev | | Authorization server metadata | hydrant.dev | | Registration endpoint | https://hydrant.dev/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://hydrant.dev/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://hydrant.dev/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://hydrant.dev/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hydrant. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.hydrant/hydrant | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hydrant-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hydrant), read 4 November 2026 - [Hydrant website](https://hydrant.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hygraph MCP server | Agent MCP Directory" description: "Does Hygraph have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hygraph-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hygraph MCP server | Agent MCP Directory > Does Hygraph have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hygraph-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hygraph: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hygraph (hygraph.com), so the connector had nothing to connect to. Ora's cached score for hygraph.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hygraph (registry title: hygraph.com) | | --- | --- | | Domain | hygraph.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 1 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hygraph.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hygraph. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hygraph.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hygraph. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hygraph-com/index.md) ## Sources - [Ora score page for hygraph.com](https://ora.ai/score/hygraph.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 October 2026, read from GET /api/leaderboard) - [Where Hygraph was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hygraph website](https://hygraph.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HypAware MCP server | Agent MCP Directory" description: "HypAware: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/hypaware-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HypAware MCP server | Agent MCP Directory > HypAware: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/hypaware-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # HypAware: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for HypAware at api.hypaware.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | HypAware | | --- | --- | | Domain | hypaware.ai | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for hypaware.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.hypaware.ai/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,165 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:54Z https://api.hypaware.ai/v1/mcp sent initialize result auth-required (HTTP 401) 2343 ms - 20:03:17Z https://api.hypaware.ai/v1/mcp sent initialize result auth-required (HTTP 401) 2165 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.hypaware.ai/.well-known/oauth-protected-resource/v1/mcp", scope="read report-publish" | | Protected resource metadata | api.hypaware.ai | | Authorization server metadata | app.hypaware.ai | | Registration endpoint | https://app.hypaware.ai/v1/oauth/register | ### The sign-in route, step by step 1. Request `https://api.hypaware.ai/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.hypaware.ai/.well-known/oauth-protected-resource/v1/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.hypaware.ai/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for HypAware. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.hypaware/hypaware | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hypaware-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hypaware), read 4 November 2026 - [HypAware website](https://hypaware.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "HYPD AI MCP server | Agent MCP Directory" description: "HYPD AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/hypd-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # HYPD AI MCP server | Agent MCP Directory > HYPD AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/hypd-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # HYPD AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for HYPD AI at mcp.hypd.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | HYPD AI (registry title: HYPD AI - Paid Ads & Analytics) | | --- | --- | | Domain | hypd.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 78, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hypd.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hypd.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 243 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:53Z https://mcp.hypd.ai/mcp sent initialize result auth-required (HTTP 401) 853 ms - 20:03:15Z https://mcp.hypd.ai/mcp sent initialize result auth-required (HTTP 401) 243 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.hypd.ai/.well-known/oauth-protected-resource/mcp", scope="profile google_ads_accounts:read google_ads_queries:run" | | Protected resource metadata | mcp.hypd.ai | | Authorization server metadata | mcp.hypd.ai | | Registration endpoint | https://mcp.hypd.ai/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.hypd.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.hypd.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.hypd.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for HYPD AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hypd-ai/index.md) ## Sources - [Ora score page for hypd.ai](https://ora.ai/score/hypd.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [HYPD AI website](https://hypd.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hyperbeam MCP server | Agent MCP Directory" description: "Does Hyperbeam have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hyperbeam-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hyperbeam MCP server | Agent MCP Directory > Does Hyperbeam have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hyperbeam-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hyperbeam: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hyperbeam (hyperbeam.com), so the connector had nothing to connect to. Ora's cached score for hyperbeam.com is 57, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hyperbeam (registry title: hyperbeam.com) | | --- | --- | | Domain | hyperbeam.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 57, grade C; Ora scanned the domain on 31 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hyperbeam.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hyperbeam. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hyperbeam.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hyperbeam. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hyperbeam-com/index.md) ## Sources - [Ora score page for hyperbeam.com](https://ora.ai/score/hyperbeam.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 August 2026, read from GET /api/leaderboard) - [Where Hyperbeam was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hyperbeam website](https://hyperbeam.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hyperresearch MCP server | Agent MCP Directory" description: "Hyperresearch: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/hyperresearch-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hyperresearch MCP server | Agent MCP Directory > Hyperresearch: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/hyperresearch-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hyperresearch: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Hyperresearch at mcp.hyperresearch.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hyperresearch (registry title: Hyperresearch Answers) | | --- | --- | | Domain | hyperresearch.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 77, grade B; Ora scanned the domain on 7 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hyperresearch.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.hyperresearch.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 748 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:54Z https://mcp.hyperresearch.ai/mcp sent initialize result auth-required (HTTP 401) 1341 ms - 20:03:16Z https://mcp.hyperresearch.ai/mcp sent initialize result auth-required (HTTP 401) 748 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.hyperresearch.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.hyperresearch.ai | | Authorization server metadata | api.hyperresearch.ai | | Registration endpoint | https://api.hyperresearch.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.hyperresearch.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.hyperresearch.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.hyperresearch.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hyperresearch. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.hyperresearch/answers, ai.hyperresearch/hyperresearch | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hyperresearch-ai/index.md) ## Sources - [Ora score page for hyperresearch.ai](https://ora.ai/score/hyperresearch.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hyperresearch), read 4 November 2026 - [Hyperresearch website](https://hyperresearch.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hyperspell MCP server | Agent MCP Directory" description: "Does Hyperspell have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/hyperspell-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hyperspell MCP server | Agent MCP Directory > Does Hyperspell have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/hyperspell-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hyperspell: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Hyperspell (hyperspell.com), so the connector had nothing to connect to. Ora's cached score for hyperspell.com is 75, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Hyperspell (registry title: hyperspell.com) | | --- | --- | | Domain | hyperspell.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 75, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for hyperspell.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Hyperspell. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for hyperspell.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Hyperspell. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hyperspell-com/index.md) ## Sources - [Ora score page for hyperspell.com](https://ora.ai/score/hyperspell.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Hyperspell was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Hyperspell website](https://hyperspell.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Hypotize MCP server | Agent MCP Directory" description: "Hypotize: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/hypotize-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Hypotize MCP server | Agent MCP Directory > Hypotize: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/hypotize-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hypotize: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Hypotize at api.hypotize.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Hypotize | | --- | --- | | Domain | hypotize.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for hypotize.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.hypotize.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 802 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:54Z https://api.hypotize.ai/mcp sent initialize result auth-required (HTTP 401) 869 ms - 20:03:16Z https://api.hypotize.ai/mcp sent initialize result auth-required (HTTP 401) 802 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.hypotize.ai/.well-known/oauth-protected-resource", scope="hypotize:read hypotize:write hypotize:delete offline_access" | | Protected resource metadata | api.hypotize.ai | | Authorization server metadata | api.hypotize.ai | | Registration endpoint | https://api.hypotize.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.hypotize.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.hypotize.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.hypotize.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Hypotize. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.hypotize/hypotize | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/hypotize-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=hypotize), read 4 November 2026 - [Hypotize website](https://hypotize.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Icons8 MCP server | Agent MCP Directory" description: "Icons8: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/icons8-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Icons8 MCP server | Agent MCP Directory > Icons8: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/icons8-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Icons8: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Icons8 at mcp.icons8.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Icons8 | | --- | --- | | Domain | icons8.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 6,214 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for icons8.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.icons8.com/mcp/ | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,113 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:11Z https://mcp.icons8.com/mcp/ sent initialize result auth-required (HTTP 401) 1093 ms - 20:01:49Z https://mcp.icons8.com/mcp/ sent initialize result auth-required (HTTP 401) 1113 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="Authorization required", resource_metadata="https://mcp.icons8.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.icons8.com | | Authorization server metadata | mcp.icons8.com | | Registration endpoint | https://mcp.icons8.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.icons8.com/mcp/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.icons8.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.icons8.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Icons8. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.icons8/icons8 | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Yes: icons8community/icons8mpc | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/icons8-com/index.md) ## Sources - [Where Icons8 was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.icons8%2Ficons8), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=icons8), read 4 November 2026 - [Icons8 website](https://icons8.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "iDevice MCP server | Agent MCP Directory" description: "iDevice has an open MCP server with 31 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/idevice-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # iDevice MCP server | Agent MCP Directory > iDevice has an open MCP server with 31 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/idevice-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # iDevice: MCP server, CLI and agent surfaces Yes: iDevice runs a public MCP server at idevice.com that listed 31 tools to a client with no credentials on 4 November 2026. Examples: should\_i\_buy, check\_deal, pick\_between. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | iDevice (registry title: iDevice Buyer's Guide) | | --- | --- | | Domain | idevice.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for idevice.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://idevice.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | idevice-wearables 2.18.0 | | Capabilities | tools, resources | | Tools | 31 | | Resources | 4 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,073 ms over 1 attempt | ### Tools listed 31 tools - should\_i\_buy - check\_deal - pick\_between - find\_best\_device - whats\_coming - get\_product\_news - list\_products - get\_product - get\_product\_facts - compare\_products - get\_compatibility - get\_reports - search\_reports - get\_in\_the\_box - get\_release\_history - get\_reviews - get\_price\_history - get\_detailed\_facts - get\_release\_calendar - find\_products - get\_guide\_summary - get\_report\_card - get\_ownership\_facts - get\_best\_for - get\_variants\_and\_offers - get\_company\_profile - get\_guide\_extras - is\_good\_price - release\_odds - source\_track\_record - whats\_moved ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:55Z https://idevice.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1381 ms - 20:03:17Z https://idevice.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1073 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://idevice.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for iDevice. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.idevice/wearables | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/idevice-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=idevice), read 4 November 2026 - [iDevice website](https://idevice.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "IFTTT MCP server | Agent MCP Directory" description: "IFTTT: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ifttt-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # IFTTT MCP server | Agent MCP Directory > IFTTT: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ifttt-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # IFTTT: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for IFTTT at ifttt.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | IFTTT (registry title: IFTTT MCP server) | | --- | --- | | Domain | ifttt.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 77, grade B; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ifttt.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ifttt.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 238 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:54Z https://ifttt.com/mcp sent initialize result auth-required (HTTP 401) 341 ms - 20:03:16Z https://ifttt.com/mcp sent initialize result auth-required (HTTP 401) 238 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://ifttt.com/.well-known/oauth-protected-resource", scope="mcp" | | Protected resource metadata | ifttt.com | | Authorization server metadata | ifttt.com | | Registration endpoint | https://ifttt.com/oauth/register | ### The sign-in route, step by step 1. Request `https://ifttt.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://ifttt.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://ifttt.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for IFTTT. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | OAuth authorization server metadata | Found: ifttt.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.ifttt/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ifttt-com/index.md) ## Sources - [Ora score page for ifttt.com](https://ora.ai/score/ifttt.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where IFTTT was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.ifttt%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ifttt), read 4 November 2026 - [IFTTT website](https://ifttt.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "iHatePosting MCP server | Agent MCP Directory" description: "iHatePosting has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ihateposting-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # iHatePosting MCP server | Agent MCP Directory > iHatePosting has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ihateposting-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # iHatePosting: MCP server, CLI and agent surfaces Yes: iHatePosting runs a public MCP server at ihateposting.com that listed 17 tools to a client with no credentials on 4 November 2026. Examples: open\_upload\_widget, get\_upload\_ticket, whoami. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | iHatePosting | | --- | --- | | Domain | ihateposting.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for ihateposting.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ihateposting.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | ihateposting 0.12.8 | | Capabilities | resources, tools | | Tools | 17 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,177 ms over 1 attempt | ### Tools listed 17 tools - open\_upload\_widget - get\_upload\_ticket - whoami - get\_platform\_rules - validate\_post - create\_post - list\_posts - list\_accounts - list\_pinterest\_boards - get\_analytics - reschedule\_post - list\_media - upload\_media - get\_post - update\_post - retry\_post - delete\_post ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:55Z https://ihateposting.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1311 ms - 20:03:17Z https://ihateposting.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1177 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://ihateposting.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for iHatePosting. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.ihateposting/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ihateposting-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ihateposting), read 4 November 2026 - [iHatePosting website](https://ihateposting.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ImageKit MCP server | Agent MCP Directory" description: "ImageKit has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/imagekit-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ImageKit MCP server | Agent MCP Directory > ImageKit has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/imagekit-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # ImageKit: MCP server, CLI and agent surfaces Yes: ImageKit runs a public MCP server at devtools-mcp.imagekit.io that listed 2 tools to a client with no credentials on 4 November 2026. Examples: search\_docs, transformation\_builder. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for imagekit.io is 63, grade C, read on 5 November 2026. ## Fact sheet | Company | ImageKit (registry title: ImageKit Admin) | | --- | --- | | Domain | imagekit.io | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 63, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for imagekit.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://devtools-mcp.imagekit.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | ImageKit 3.3.1 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,353 ms over 1 attempt | ### Tools listed 2 tools - search\_docs - transformation\_builder ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:55Z https://devtools-mcp.imagekit.io/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1360 ms - 20:03:17Z https://devtools-mcp.imagekit.io/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1353 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://devtools-mcp.imagekit.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ImageKit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/imagekit-io/index.md) ## Sources - [Ora score page for imagekit.io](https://ora.ai/score/imagekit.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [ImageKit website](https://imagekit.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Imgix MCP server | Agent MCP Directory" description: "Does Imgix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/imgix-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Imgix MCP server | Agent MCP Directory > Does Imgix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/imgix-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Imgix: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Imgix (imgix.com), so the connector had nothing to connect to. Ora's cached score for imgix.com is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Imgix (registry title: imgix.com) | | --- | --- | | Domain | imgix.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for imgix.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Imgix. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for imgix.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Imgix. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/imgix-com/index.md) ## Sources - [Ora score page for imgix.com](https://ora.ai/score/imgix.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Imgix was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Imgix website](https://imgix.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "imzala.net MCP server | Agent MCP Directory" description: "imzala.net: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/imzala-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # imzala.net MCP server | Agent MCP Directory > imzala.net: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/imzala-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # imzala.net: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for imzala.net at mcp.imzala.net answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | imzala.net (registry title: imzala.net: Türk içtihat arşivi) | | --- | --- | | Domain | imzala.net | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for imzala.net when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.imzala.net/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 543 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:55Z https://mcp.imzala.net/mcp sent initialize result auth-required (HTTP 401) 694 ms - 20:03:17Z https://mcp.imzala.net/mcp sent initialize result auth-required (HTTP 401) 543 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.imzala.net/.well-known/oauth-protected-resource/mcp", scope="ictihat" | | Protected resource metadata | mcp.imzala.net | | Authorization server metadata | mcp.imzala.net | | Registration endpoint | https://mcp.imzala.net/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.imzala.net/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.imzala.net/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.imzala.net/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for imzala.net. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/imzala-net/index.md) ## Sources - [imzala.net website](https://imzala.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Inamprotocol MCP server | Agent MCP Directory" description: "Inamprotocol has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/inamprotocol-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Inamprotocol MCP server | Agent MCP Directory > Inamprotocol has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/inamprotocol-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Inamprotocol: MCP server, CLI and agent surfaces Yes: Inamprotocol runs a public MCP server at api.inamprotocol.org that listed 6 tools to a client with no credentials on 4 November 2026. Examples: inam\_check\_reputation, inam\_search\_agents, inam\_hash\_content. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Inamprotocol (registry title: Inamprotocol Inam) | | --- | --- | | Domain | inamprotocol.org | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for inamprotocol.org when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.inamprotocol.org/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | inam-mcp 0.6.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 473 ms over 1 attempt | ### Tools listed 6 tools - inam\_check\_reputation - inam\_search\_agents - inam\_hash\_content - inam\_get\_receipt - inam\_verify\_receipt - inam\_check ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:56Z https://api.inamprotocol.org/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 761 ms - 20:03:17Z https://api.inamprotocol.org/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 473 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.inamprotocol.org/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Inamprotocol. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/inamprotocol-org/index.md) ## Sources - [Inamprotocol website](https://inamprotocol.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "incident.io MCP server | Agent MCP Directory" description: "incident.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/incident-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # incident.io MCP server | Agent MCP Directory > incident.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/incident-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # incident.io: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for incident.io; the connector's guess at mcp.incident.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | incident.io | | --- | --- | | Domain | incident.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for incident.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.incident.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 323 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:56Z https://mcp.incident.io/mcp sent initialize result auth-required (HTTP 401) 335 ms - 20:03:17Z https://mcp.incident.io/mcp sent initialize result auth-required (HTTP 401) 323 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.incident.io/mcp/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.incident.io | | Authorization server metadata | mcp.incident.io | | Registration endpoint | https://mcp.incident.io/mcp/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.incident.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.incident.io/mcp/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.incident.io/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for incident.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/incident-io/index.md) ## Sources - [Ora score page for incident.io](https://ora.ai/score/incident.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where incident.io was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [incident.io website](https://incident.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "IncidentFox MCP server | Agent MCP Directory" description: "Does IncidentFox have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/incidentfox-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # IncidentFox MCP server | Agent MCP Directory > Does IncidentFox have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/incidentfox-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # IncidentFox: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for IncidentFox (incidentfox.ai), so the connector had nothing to connect to. Ora's cached score for incidentfox.ai is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | IncidentFox (registry title: incidentfox.ai) | | --- | --- | | Domain | incidentfox.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for incidentfox.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for IncidentFox. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for incidentfox.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for IncidentFox. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/incidentfox-ai/index.md) ## Sources - [Ora score page for incidentfox.ai](https://ora.ai/score/incidentfox.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where IncidentFox was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [IncidentFox website](https://incidentfox.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Inconvo MCP server | Agent MCP Directory" description: "Does Inconvo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/inconvo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Inconvo MCP server | Agent MCP Directory > Does Inconvo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/inconvo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Inconvo: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Inconvo (inconvo.com), so the connector had nothing to connect to. Ora's cached score for inconvo.com is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Inconvo (registry title: inconvo.com) | | --- | --- | | Domain | inconvo.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for inconvo.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Inconvo. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for inconvo.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Inconvo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/inconvo-com/index.md) ## Sources - [Ora score page for inconvo.com](https://ora.ai/score/inconvo.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/leaderboard) - [Where Inconvo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Inconvo website](https://inconvo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Indeed MCP server | Agent MCP Directory" description: "Indeed: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/indeed-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Indeed MCP server | Agent MCP Directory > Indeed: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/indeed-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Indeed: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Indeed at mcp.indeed.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Indeed | | --- | --- | | Domain | indeed.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 429 on the list of 4 November 2026 | | Ora score | 25, grade F; Ora scanned the domain on 23 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for indeed.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.indeed.com/claude/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 661 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://mcp.indeed.com/claude/mcp sent initialize result auth-required (HTTP 401) 1112 ms - 20:01:30Z https://mcp.indeed.com/claude/mcp sent initialize result auth-required (HTTP 401) 661 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.indeed.com/.well-known/oauth-protected-resource/claude/mcp" | | Protected resource metadata | mcp.indeed.com | | Authorization server metadata | secure.indeed.com | | Registration endpoint | https://secure.indeed.com/oauth/v2/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.indeed.com/claude/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.indeed.com/.well-known/oauth-protected-resource/claude/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://secure.indeed.com/oauth/v2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Indeed. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/indeed-com/index.md) ## Sources - [Ora score page for indeed.com](https://ora.ai/score/indeed.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 August 2026, read from GET /api/score) - [Where Indeed was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "IndustryLens MCP server | Agent MCP Directory" description: "IndustryLens has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/industry-lens-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # IndustryLens MCP server | Agent MCP Directory > IndustryLens has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/industry-lens-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # IndustryLens: MCP server, CLI and agent surfaces Yes: IndustryLens runs a public MCP server at api.industry-lens.com that listed 12 tools to a client with no credentials on 4 November 2026. Examples: get\_competitive\_profile, list\_competitor\_moves, find\_competitors. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | IndustryLens | | --- | --- | | Domain | industry-lens.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for industry-lens.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.industry-lens.com/mcp/public | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | industrylens-public 0.1.0 | | Capabilities | tools, resources, prompts | | Tools | 12 | | Resources | 1 | | Prompts | 5 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 821 ms over 1 attempt | ### Tools listed 12 tools - get\_competitive\_profile - list\_competitor\_moves - find\_competitors - list\_reports - get\_report - list\_comparisons - get\_comparison - subscribe\_to\_newsletter - get\_competitor\_moves\_diff - get\_pricing\_changes - list\_markets - get\_market\_landscape ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:57Z https://api.industry-lens.com/mcp/public sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 932 ms - 20:03:18Z https://api.industry-lens.com/mcp/public sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 821 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.industry-lens.com/mcp/public` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for IndustryLens. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.industry-lens/mcp-public | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Yes: industrylens/mcp | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/industry-lens-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=industry-lens), read 4 November 2026 - [IndustryLens website](https://industry-lens.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Infer MCP server | Agent MCP Directory" description: "Does Infer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/infer-so site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Infer MCP server | Agent MCP Directory > Does Infer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/infer-so Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infer: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Infer (infer.so), so the connector had nothing to connect to. Ora's cached score for infer.so is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Infer (registry title: infer.so) | | --- | --- | | Domain | infer.so | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for infer.so, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Infer. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for infer.so, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Infer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/infer-so/index.md) ## Sources - [Ora score page for infer.so](https://ora.ai/score/infer.so?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Infer was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Infer website](https://infer.so), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Infield MCP server | Agent MCP Directory" description: "Does Infield have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/infield-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Infield MCP server | Agent MCP Directory > Does Infield have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/infield-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infield: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Infield (infield.ai), so the connector had nothing to connect to. Ora's cached score for infield.ai is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Infield (registry title: infield.ai) | | --- | --- | | Domain | infield.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 5 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for infield.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Infield. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for infield.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Infield. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/infield-ai/index.md) ## Sources - [Ora score page for infield.ai](https://ora.ai/score/infield.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 September 2026, read from GET /api/leaderboard) - [Where Infield was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Infield website](https://infield.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Infobip MCP server | Agent MCP Directory" description: "Infobip: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/infobip-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Infobip MCP server | Agent MCP Directory > Infobip: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/infobip-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infobip: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Infobip at mcp.infobip.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Infobip (registry title: infobip.com) | | --- | --- | | Domain | infobip.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 5,097 on the list of 4 November 2026 | | Ora score | 77, grade B; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for infobip.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.infobip.com/sms | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,366 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:08Z https://mcp.infobip.com/sms sent initialize result auth-required (HTTP 401) 1388 ms - 20:01:45Z https://mcp.infobip.com/sms sent initialize result auth-required (HTTP 401) 1366 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.infobip.com/sms/.well-known/oauth-protected-resource", scope="sms:manage profile offline_access" | | Protected resource metadata | mcp.infobip.com | | Authorization server metadata | auth.infobip.com | | Registration endpoint | https://auth.infobip.com/realms/infobip/clients-registrations/openid-connect | ### The sign-in route, step by step 1. Request `https://mcp.infobip.com/sms` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.infobip.com/sms/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.infobip.com/realms/infobip/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Infobip. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.infobip/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/infobip-com/index.md) ## Sources - [Ora score page for infobip.com](https://ora.ai/score/infobip.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/score) - [Where Infobip was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.infobip%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=infobip), read 4 November 2026 - [Infobip website](https://infobip.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Infra MCP server | Agent MCP Directory" description: "Does Infra have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/infra-new site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Infra MCP server | Agent MCP Directory > Does Infra have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/infra-new Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infra: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Infra (infra.new), so the connector had nothing to connect to. Ora's cached score for infra.new is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Infra (registry title: infra.new) | | --- | --- | | Domain | infra.new | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for infra.new, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Infra. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for infra.new, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Infra. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/infra-new/index.md) ## Sources - [Ora score page for infra.new](https://ora.ai/score/infra.new?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/leaderboard) - [Where Infra was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Infra website](https://infra.new), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Infracost MCP server | Agent MCP Directory" description: "Infracost has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/infracost-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Infracost MCP server | Agent MCP Directory > Infracost has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/infracost-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Infracost: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Infracost; the connector tried mcp.infracost.io as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | Infracost (registry title: infracost.io) | | --- | --- | | Domain | infracost.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 50, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for infracost.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.infracost.io/mcp | | --- | --- | | How it was found | mcp.infracost.io was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 912 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:57Z https://mcp.infracost.io/mcp sent initialize result no-answer (HTTP 404) 941 ms - 20:03:19Z https://mcp.infracost.io/mcp sent initialize result no-answer (HTTP 404) 912 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.infracost.io/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Infracost. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/infracost-io/index.md) ## Sources - [Ora score page for infracost.io](https://ora.ai/score/infracost.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/leaderboard) - [Where Infracost was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Infracost website](https://infracost.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Inkeep MCP server | Agent MCP Directory" description: "Inkeep has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/inkeep-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Inkeep MCP server | Agent MCP Directory > Inkeep has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/inkeep-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Inkeep: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Inkeep; the connector tried mcp.inkeep.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 application/json). ## Fact sheet | Company | Inkeep (registry title: inkeep.com) | | --- | --- | | Domain | inkeep.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 71, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for inkeep.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.inkeep.com/mcp | | --- | --- | | How it was found | mcp.inkeep.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 604 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 application/json) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:57Z https://mcp.inkeep.com/mcp sent initialize result no-answer (HTTP 404) 620 ms - 20:03:18Z https://mcp.inkeep.com/mcp sent initialize result no-answer (HTTP 404) 604 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.inkeep.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 application/json). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Inkeep. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/inkeep-com/index.md) ## Sources - [Ora score page for inkeep.com](https://ora.ai/score/inkeep.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Inkeep was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Inkeep website](https://inkeep.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "InsForge MCP server | Agent MCP Directory" description: "InsForge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/insforge-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # InsForge MCP server | Agent MCP Directory > InsForge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/insforge-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # InsForge: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for InsForge; the connector's guess at mcp.insforge.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | InsForge (registry title: insforge.dev) | | --- | --- | | Domain | insforge.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 85, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for insforge.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.insforge.dev/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,935 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:58Z https://mcp.insforge.dev/mcp sent initialize result auth-required (HTTP 401) 1734 ms - 20:03:20Z https://mcp.insforge.dev/mcp sent initialize result auth-required (HTTP 401) 1935 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.insforge.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.insforge.dev | | Authorization server metadata | keen-pulse-fsjr9--br-fix-revoke-actually-revokes.run.mcp-use.com | | Registration endpoint | https://keen-pulse-fsjr9--br-fix-revoke-actually-revokes.run.mcp-use.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.insforge.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.insforge.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://keen-pulse-fsjr9--br-fix-revoke-actually-revokes.run.mcp-use.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for InsForge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/insforge-dev/index.md) ## Sources - [Ora score page for insforge.dev](https://ora.ai/score/insforge.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where InsForge was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [InsForge website](https://insforge.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Instant MCP server | Agent MCP Directory" description: "Instant: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/instantdb-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Instant MCP server | Agent MCP Directory > Instant: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/instantdb-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Instant: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Instant at mcp.instantdb.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Instant | | --- | --- | | Domain | instantdb.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 70, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for instantdb.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.instantdb.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,246 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:58Z https://mcp.instantdb.com/mcp sent initialize result auth-required (HTTP 401) 1506 ms - 20:03:19Z https://mcp.instantdb.com/mcp sent initialize result auth-required (HTTP 401) 1246 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.instantdb.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.instantdb.com | | Authorization server metadata | mcp.instantdb.com | | Registration endpoint | https://mcp.instantdb.com/register | | Auth as listed by a registry | OAuth (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.instantdb.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.instantdb.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.instantdb.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Instant. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/instantdb-com/index.md) ## Sources - [Ora score page for instantdb.com](https://ora.ai/score/instantdb.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Instant was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Instant website](https://instantdb.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Integuru MCP server | Agent MCP Directory" description: "Does Integuru have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/integuru-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Integuru MCP server | Agent MCP Directory > Does Integuru have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/integuru-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Integuru: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Integuru (integuru.ai), so the connector had nothing to connect to. Ora's cached score for integuru.ai is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Integuru (registry title: integuru.ai) | | --- | --- | | Domain | integuru.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 6 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for integuru.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Integuru. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for integuru.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Integuru. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/integuru-ai/index.md) ## Sources - [Ora score page for integuru.ai](https://ora.ai/score/integuru.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 August 2026, read from GET /api/leaderboard) - [Where Integuru was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Integuru website](https://integuru.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Intercom MCP server | Agent MCP Directory" description: "Intercom: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/intercom-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Intercom MCP server | Agent MCP Directory > Intercom: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/intercom-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Intercom: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Intercom at mcp.intercom.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Intercom | | --- | --- | | Domain | intercom.com | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 1,187 on the list of 4 November 2026 | | Ora score | 81, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for intercom.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.intercom.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 115 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:56Z https://mcp.intercom.com/mcp sent initialize result auth-required (HTTP 401) 133 ms - 20:01:32Z https://mcp.intercom.com/mcp sent initialize result auth-required (HTTP 401) 115 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token", resource_metadata="https://mcp.intercom.com/.well-known/oauth-protected-resource/mcp", scope="mcp operator" | | Protected resource metadata | mcp.intercom.com | | Authorization server metadata | mcp.intercom.com | | Registration endpoint | https://mcp.intercom.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.intercom.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.intercom.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.intercom.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Intercom. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/intercom-com/index.md) ## Sources - [Ora score page for intercom.com](https://ora.ai/score/intercom.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Where Intercom was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Intercom website](https://intercom.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Interfaze MCP server | Agent MCP Directory" description: "Does Interfaze have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/interfaze-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Interfaze MCP server | Agent MCP Directory > Does Interfaze have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/interfaze-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Interfaze: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Interfaze (interfaze.ai), so the connector had nothing to connect to. Ora's cached score for interfaze.ai is 66, grade C, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Interfaze (registry title: interfaze.ai) | | --- | --- | | Domain | interfaze.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for interfaze.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Interfaze. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for interfaze.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Interfaze. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: interfaze.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: interfaze.ai/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/interfaze-ai/index.md) ## Sources - [Ora score page for interfaze.ai](https://ora.ai/score/interfaze.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/leaderboard) - [Where Interfaze was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Interfaze website](https://interfaze.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Interfere MCP server | Agent MCP Directory" description: "Interfere: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/interfere-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Interfere MCP server | Agent MCP Directory > Interfere: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/interfere-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Interfere: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Interfere; the connector's guess at mcp.interfere.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Interfere (registry title: interfere.com) | | --- | --- | | Domain | interfere.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 39, grade D; Ora scanned the domain on 6 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for interfere.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.interfere.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 473 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:58Z https://mcp.interfere.com/mcp sent initialize result auth-required (HTTP 401) 828 ms - 20:03:19Z https://mcp.interfere.com/mcp sent initialize result auth-required (HTTP 401) 473 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.interfere.com/.well-known/oauth-protected-resource/mcp", scope="interfere:access user:org:read offline_access" | | Protected resource metadata | mcp.interfere.com | | Authorization server metadata | clerk.interfere.com | | Registration endpoint | https://clerk.interfere.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.interfere.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.interfere.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.interfere.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Interfere. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: interfere.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/interfere-com/index.md) ## Sources - [Ora score page for interfere.com](https://ora.ai/score/interfere.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 August 2026, read from GET /api/leaderboard) - [Where Interfere was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Interfere website](https://interfere.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Inttegro MCP server | Agent MCP Directory" description: "Inttegro: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/inttegro-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Inttegro MCP server | Agent MCP Directory > Inttegro: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/inttegro-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Inttegro: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Inttegro at mcp.inttegro.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Inttegro | | --- | --- | | Domain | inttegro.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | none: Ora returned no cached score for inttegro.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.inttegro.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 740 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:58Z https://mcp.inttegro.com/ sent initialize result auth-required (HTTP 401) 1157 ms - 20:03:19Z https://mcp.inttegro.com/ sent initialize result auth-required (HTTP 401) 740 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="commerce.mcp", resource_metadata="https://mcp.inttegro.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.inttegro.com | | Authorization server metadata | clerk.inttegro.com | ### The sign-in route, step by step 1. Request `https://mcp.inttegro.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://clerk.inttegro.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Inttegro. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.inttegro/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/inttegro-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=inttegro), read 4 November 2026 - [Inttegro website](https://inttegro.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Intuned MCP server | Agent MCP Directory" description: "Does Intuned have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/intunedhq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Intuned MCP server | Agent MCP Directory > Does Intuned have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/intunedhq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Intuned: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Intuned (intunedhq.com), so the connector had nothing to connect to. Ora's cached score for intunedhq.com is 63, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Intuned (registry title: intunedhq.com) | | --- | --- | | Domain | intunedhq.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 5 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for intunedhq.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Intuned. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for intunedhq.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Intuned. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/intunedhq-com/index.md) ## Sources - [Ora score page for intunedhq.com](https://ora.ai/score/intunedhq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 September 2026, read from GET /api/leaderboard) - [Where Intuned was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Intuned website](https://intunedhq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Invideo MCP server | Agent MCP Directory" description: "Invideo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/invideo-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Invideo MCP server | Agent MCP Directory > Invideo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/invideo-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Invideo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Invideo at mcp.invideo.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Invideo (registry title: Invidio) | | --- | --- | | Domain | invideo.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 54, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for invideo.io, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.invideo.io/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,257 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:57:59Z https://mcp.invideo.io/sse sent initialize result no-answer (HTTP 410) 977 ms - 20:03:20Z https://mcp.invideo.io/sse sent initialize result no-answer (HTTP 410) 954 ms - 20:03:21Z https://mcp.invideo.io/mcp sent initialize result auth-required (HTTP 401) 1257 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.invideo.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.invideo.io | | Authorization server metadata | pro-api-auth.invideo.io | | Registration endpoint | https://pro-api-auth.invideo.io/oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.invideo.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.invideo.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://pro-api-auth.invideo.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Invideo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/invideo-io/index.md) ## Sources - [Ora score page for invideo.io](https://ora.ai/score/invideo.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Where Invideo was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Invideo website](https://invideo.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Invokary MCP server | Agent MCP Directory" description: "Invokary has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/invokary-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Invokary MCP server | Agent MCP Directory > Invokary has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/invokary-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Invokary: MCP server, CLI and agent surfaces Yes: Invokary runs a public MCP server at mcp.invokary.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: list\_platforms, get\_platform\_requirements, get\_requirement. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Invokary (registry title: Invokary Platform Requirements) | | --- | --- | | Domain | invokary.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for invokary.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.invokary.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | platform-requirements 1.0.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 197 ms over 1 attempt | ### Tools listed 6 tools - list\_platforms - get\_platform\_requirements - get\_requirement - compare\_platforms - search\_requirements - list\_platform\_changes ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:57:59Z https://mcp.invokary.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 532 ms - 20:03:19Z https://mcp.invokary.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 197 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.invokary.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Invokary. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.invokary/platform-requirements | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/invokary-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=invokary), read 4 November 2026 - [Invokary website](https://invokary.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "IOMETE MCP server | Agent MCP Directory" description: "Does IOMETE have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/iomete-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # IOMETE MCP server | Agent MCP Directory > Does IOMETE have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/iomete-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # IOMETE: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for IOMETE (iomete.com), so the connector had nothing to connect to. Ora's cached score for iomete.com is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | IOMETE (registry title: iomete.com) | | --- | --- | | Domain | iomete.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for iomete.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for IOMETE. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for iomete.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for IOMETE. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/iomete-com/index.md) ## Sources - [Ora score page for iomete.com](https://ora.ai/score/iomete.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/leaderboard) - [Where IOMETE was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [IOMETE website](https://iomete.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ISMS Copilot MCP server | Agent MCP Directory" description: "ISMS Copilot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/ismscopilot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ISMS Copilot MCP server | Agent MCP Directory > ISMS Copilot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/ismscopilot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ISMS Copilot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ISMS Copilot at account.ismscopilot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ISMS Copilot | | --- | --- | | Domain | ismscopilot.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 73, grade B; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ismscopilot.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://account.ismscopilot.com/v1/account/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 634 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:00Z https://account.ismscopilot.com/v1/account/mcp sent initialize result auth-required (HTTP 401) 949 ms - 20:03:20Z https://account.ismscopilot.com/v1/account/mcp sent initialize result auth-required (HTTP 401) 634 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://account.ismscopilot.com/.well-known/oauth-protected-resource" | | Protected resource metadata | account.ismscopilot.com | | Authorization server metadata | pfwmuzyoeyqcvodfsisn.supabase.co | | Registration endpoint | https://pfwmuzyoeyqcvodfsisn.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://account.ismscopilot.com/v1/account/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://account.ismscopilot.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://pfwmuzyoeyqcvodfsisn.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ISMS Copilot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.ismscopilot.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ismscopilot-com/index.md) ## Sources - [Ora score page for ismscopilot.com](https://ora.ai/score/ismscopilot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [ISMS Copilot website](https://ismscopilot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Isonavigator MCP server | Agent MCP Directory" description: "Isonavigator has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/isonavigator-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Isonavigator MCP server | Agent MCP Directory > Isonavigator has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/isonavigator-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Isonavigator: MCP server, CLI and agent surfaces Yes: Isonavigator runs a public MCP server at mcp.isonavigator.io that listed 4 tools to a client with no credentials on 4 November 2026. Examples: iso20022\_bank\_transaction\_codes, iso20022\_message\_details, iso20022\_legacy\_and\_scheme\_mappings. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Isonavigator (registry title: ISO 20022 Navigator) | | --- | --- | | Domain | isonavigator.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for isonavigator.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.isonavigator.io/iso20022 | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | iso20022-navigator 0.2.0 | | Capabilities | experimental, prompts, resources, tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,755 ms over 1 attempt | ### Tools listed 4 tools - iso20022\_bank\_transaction\_codes - iso20022\_message\_details - iso20022\_legacy\_and\_scheme\_mappings - iso20022\_code\_sets ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:01Z https://mcp.isonavigator.io/iso20022 sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1796 ms - 20:03:21Z https://mcp.isonavigator.io/iso20022 sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1755 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.isonavigator.io/iso20022` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Isonavigator. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/isonavigator-io/index.md) ## Sources - [Isonavigator website](https://isonavigator.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Isto Intents MCP server | Agent MCP Directory" description: "Isto Intents has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/istointents-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Isto Intents MCP server | Agent MCP Directory > Isto Intents has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/istointents-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Isto Intents: MCP server, CLI and agent surfaces Yes: Isto Intents runs a public MCP server at istointents.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: intent\_publish\_intent, intent\_get\_intent, intent\_list\_matches. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Isto Intents | | --- | --- | | Domain | istointents.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for istointents.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://istointents.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | istointents-forwarder 0.2.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 174 ms over 1 attempt | ### Tools listed 4 tools - intent\_publish\_intent - intent\_get\_intent - intent\_list\_matches - intent\_withdraw\_intent ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:00Z https://istointents.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 610 ms - 20:03:19Z https://istointents.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 174 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://istointents.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Isto Intents. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.istointents/intents | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/istointents-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=istointents), read 4 November 2026 - [Isto Intents website](https://istointents.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Easy MCP server | Agent MCP Directory" description: "Easy has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/itseasy-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Easy MCP server | Agent MCP Directory > Easy has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/itseasy-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Easy: MCP server, CLI and agent surfaces Yes: Easy runs a public MCP server at www.itseasy.co that listed 3 tools to a client with no credentials on 4 November 2026. Examples: list\_pages, get\_page, get\_pricing\_rates. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for itseasy.co is 87, grade A, read on 5 November 2026. ## Fact sheet | Company | Easy (registry title: Easy Labs MCP Server) | | --- | --- | | Domain | itseasy.co | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 87, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for itseasy.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.itseasy.co/api/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | easy-marketing-mcp 1.0.0 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 917 ms over 1 attempt | ### Tools listed 3 tools - list\_pages - get\_page - get\_pricing\_rates ### Connector log 4 connections on 4 November 2026, read-only methods only - 19:58:00Z https://mcp.itseasy.co/mcp sent initialize result no-answer (HTTP 503) 975 ms - 19:58:01Z https://www.itseasy.co/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 963 ms - 20:03:21Z https://mcp.itseasy.co/mcp sent initialize result no-answer (HTTP 503) 973 ms - 20:03:21Z https://www.itseasy.co/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 917 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.itseasy.co/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Easy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: itseasy.co/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: itseasy.co/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.itseasy/easy-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/itseasy-co/index.md) ## Sources - [Ora score page for itseasy.co](https://ora.ai/score/itseasy.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Easy was found](https://registry.modelcontextprotocol.io/v0/servers?search=co.itseasy%2Feasy-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=itseasy), read 4 November 2026 - [Easy website](https://itseasy.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "NUM MCP server | Agent MCP Directory" description: "NUM has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/itsnum-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # NUM MCP server | Agent MCP Directory > NUM has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/itsnum-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # NUM: MCP server, CLI and agent surfaces Yes: NUM runs a public MCP server at itsnum.com that listed 10 tools to a client with no credentials on 4 November 2026. Examples: num\_search\_places, num\_list\_destinations, num\_get\_place. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | NUM | | --- | --- | | Domain | itsnum.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for itsnum.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://itsnum.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | num 1.3.0 | | Capabilities | tools | | Tools | 10 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 192 ms over 1 attempt | ### Tools listed 10 tools - num\_search\_places - num\_list\_destinations - num\_get\_place - num\_submit\_business - num\_submit\_promo - num\_list\_submissions - num\_search\_photos - num\_quote\_photo - num\_license\_photo - num\_photo\_wallet ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:00Z https://itsnum.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 477 ms - 20:03:20Z https://itsnum.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 192 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://itsnum.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for NUM. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: itsnum.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.itsnum/esim, com.itsnum/num, com.itsnum/places | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/itsnum-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=itsnum), read 4 November 2026 - [NUM website](https://itsnum.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ix MCP server | Agent MCP Directory" description: "Does ix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/ix-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ix MCP server | Agent MCP Directory > Does ix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/ix-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # ix: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for ix (ix.dev), so the connector had nothing to connect to. Ora's cached score for ix.dev is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | ix (registry title: ix.dev) | | --- | --- | | Domain | ix.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ix.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for ix. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ix.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for ix. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: ix.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ix-dev/index.md) ## Sources - [Ora score page for ix.dev](https://ora.ai/score/ix.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/leaderboard) - [Where ix was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ix website](https://ix.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Jam.dev MCP server | Agent MCP Directory" description: "Jam.dev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/jam-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Jam.dev MCP server | Agent MCP Directory > Jam.dev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/jam-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Jam.dev: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Jam.dev at mcp.jam.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Jam.dev | | --- | --- | | Domain | jam.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for jam.dev, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.jam.dev/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,354 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:00Z https://mcp.jam.dev/mcp sent initialize result auth-required (HTTP 401) 1130 ms - 20:03:21Z https://mcp.jam.dev/mcp sent initialize result auth-required (HTTP 401) 1354 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.jam.dev/.well-known/oauth-protected-resource", scope="mcp:read mcp:write" | | Protected resource metadata | mcp.jam.dev | | Authorization server metadata | api.jam.dev | | Registration endpoint | https://api.jam.dev/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.jam.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.jam.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.jam.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Jam.dev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.jam/jam | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jam-dev/index.md) ## Sources - [Ora score page for jam.dev](https://ora.ai/score/jam.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/score) - [Where Jam.dev was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=jam), read 4 November 2026 - [Jam.dev website](https://jam.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "JANCTION MCP server | Agent MCP Directory" description: "JANCTION: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/janction-jp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # JANCTION MCP server | Agent MCP Directory > JANCTION: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/janction-jp Site: Agent MCP Directory Last reviewed: 2026-11-05 # JANCTION: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for JANCTION at render.janction.jp answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | JANCTION (registry title: JANCTION Render) | | --- | --- | | Domain | janction.jp | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for janction.jp when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://render.janction.jp/mcp?src=registry | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,597 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:02Z https://render.janction.jp/mcp?src=registry sent initialize result auth-required (HTTP 401) 2371 ms - 20:03:22Z https://render.janction.jp/mcp?src=registry sent initialize result auth-required (HTTP 401) 1597 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://render.janction.jp/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | render.janction.jp | | Authorization server metadata | render.janction.jp | | Registration endpoint | https://render.janction.jp/register | ### The sign-in route, step by step 1. Request `https://render.janction.jp/mcp?src=registry` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://render.janction.jp/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://render.janction.jp/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for JANCTION. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: render.janction.jp (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/janction-jp/index.md) ## Sources - [Where JANCTION was found](https://github.com/mcp/JasmyLab-JANCTION/janction-render), read 4 November 2026 - [JANCTION website](https://janction.jp), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Javadocs.dev MCP server | Agent MCP Directory" description: "Javadocs.dev has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/javadocs-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Javadocs.dev MCP server | Agent MCP Directory > Javadocs.dev has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/javadocs-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Javadocs.dev: MCP server, CLI and agent surfaces Yes: Javadocs.dev runs a public MCP server at www.javadocs.dev that listed 8 tools to a client with no credentials on 4 November 2026. Examples: get\_latest\_version, get\_javadoc\_index, list\_javadoc\_symbols. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for javadocs.dev is 47, grade D, read on 5 November 2026. ## Fact sheet | Company | Javadocs.dev | | --- | --- | | Domain | javadocs.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 47, grade D; Ora scanned the domain on 16 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for javadocs.dev, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.javadocs.dev/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | javadocs.dev 0.0.2 | | Capabilities | tools, logging, completions | | Tools | 8 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,258 ms over 1 attempt | ### Tools listed 8 tools - get\_latest\_version - get\_javadoc\_index - list\_javadoc\_symbols - get\_javadoc\_symbol - get\_source\_file - list\_source\_files - search\_artifacts - symbol\_to\_artifact ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:01Z https://www.javadocs.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1176 ms - 20:03:21Z https://www.javadocs.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1258 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://www.javadocs.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Javadocs.dev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.javadocs.dev (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/javadocs-dev/index.md) ## Sources - [Ora score page for javadocs.dev](https://ora.ai/score/javadocs.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 September 2026, read from GET /api/score) - [Where Javadocs.dev was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Javadocs.dev website](https://javadocs.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Jet Admin MCP server | Agent MCP Directory" description: "Does Jet Admin have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/jetadmin-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Jet Admin MCP server | Agent MCP Directory > Does Jet Admin have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/jetadmin-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Jet Admin: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Jet Admin (jetadmin.io), so the connector had nothing to connect to. Ora's cached score for jetadmin.io is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Jet Admin (registry title: jetadmin.io) | | --- | --- | | Domain | jetadmin.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for jetadmin.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Jet Admin. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for jetadmin.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Jet Admin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jetadmin-io/index.md) ## Sources - [Ora score page for jetadmin.io](https://ora.ai/score/jetadmin.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Jet Admin was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Jet Admin website](https://jetadmin.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "JetBrains MCP server | Agent MCP Directory" description: "Does JetBrains have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/jetbrains-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # JetBrains MCP server | Agent MCP Directory > Does JetBrains have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/jetbrains-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # JetBrains: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for JetBrains (jetbrains.com), so the connector had nothing to connect to. Ora's cached score for jetbrains.com is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | JetBrains | | --- | --- | | Domain | jetbrains.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 958 on the list of 4 November 2026 | | Ora score | 62, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for jetbrains.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for JetBrains. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for jetbrains.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for JetBrains. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jetbrains-com/index.md) ## Sources - [Ora score page for jetbrains.com](https://ora.ai/score/jetbrains.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/score) - [Where JetBrains was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [JetBrains website](https://jetbrains.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "JFrog MCP server | Agent MCP Directory" description: "Does JFrog have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/jfrog-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # JFrog MCP server | Agent MCP Directory > Does JFrog have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/jfrog-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # JFrog: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for JFrog (jfrog.com), so the connector had nothing to connect to. Ora's cached score for jfrog.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | JFrog | | --- | --- | | Domain | jfrog.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for jfrog.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for JFrog. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for jfrog.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for JFrog. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jfrog-com/index.md) ## Sources - [Ora score page for jfrog.com](https://ora.ai/score/jfrog.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where JFrog was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [JFrog website](https://jfrog.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Jitsu MCP server | Agent MCP Directory" description: "Jitsu: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/jitsu-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Jitsu MCP server | Agent MCP Directory > Jitsu: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/jitsu-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Jitsu: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Jitsu at use.jitsu.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Jitsu | | --- | --- | | Domain | jitsu.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 63, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for jitsu.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://use.jitsu.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,145 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:01Z https://use.jitsu.com/mcp sent initialize result auth-required (HTTP 401) 1200 ms - 20:03:22Z https://use.jitsu.com/mcp sent initialize result auth-required (HTTP 401) 1145 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="jitsu-mcp", error="missing_token", error_description="Authorization header either missing or malformed", resource_metadata="https://use.jitsu.com/.well-known/oauth-protected-resource" | | Protected resource metadata | use.jitsu.com | | Authorization server metadata | use.jitsu.com | | Registration endpoint | https://use.jitsu.com/oauth/register | ### The sign-in route, step by step 1. Request `https://use.jitsu.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://use.jitsu.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://use.jitsu.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Jitsu. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.jitsu/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jitsu-com/index.md) ## Sources - [Ora score page for jitsu.com](https://ora.ai/score/jitsu.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where Jitsu was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.jitsu%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=jitsu), read 4 November 2026 - [Jitsu website](https://jitsu.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "JobsPipe MCP server | Agent MCP Directory" description: "JobsPipe has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/jobspipe-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # JobsPipe MCP server | Agent MCP Directory > JobsPipe has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/jobspipe-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # JobsPipe: MCP server, CLI and agent surfaces Yes: JobsPipe runs a public MCP server at jobspipe.dev that listed 3 tools to a client with no credentials on 4 November 2026. Examples: search\_jobs, list\_job\_sources, list\_pricing\_plans. It speaks streamable-http, protocol 2026-07-28. Ora's cached score for jobspipe.dev is 96, grade A+, read on 5 November 2026. ## Fact sheet | Company | JobsPipe | | --- | --- | | Domain | jobspipe.dev | | Category | Security (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 96, grade A+; Ora scanned the domain on 24 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for jobspipe.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://jobspipe.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | jobspipe 1.0.0 | | Capabilities | tools, resources | | Tools | 3 | | Resources | 3 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,003 ms over 1 attempt | ### Tools listed 3 tools - search\_jobs - list\_job\_sources - list\_pricing\_plans ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:06Z https://jobspipe.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 5727 ms - 20:03:22Z https://jobspipe.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1003 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://jobspipe.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for JobsPipe. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: jobspipe.dev (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.jobspipe/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jobspipe-dev/index.md) ## Sources - [Ora score page for jobspipe.dev](https://ora.ai/score/jobspipe.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=jobspipe), read 4 November 2026 - [JobsPipe website](https://jobspipe.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Jotform MCP server | Agent MCP Directory" description: "Jotform: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/jotform-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Jotform MCP server | Agent MCP Directory > Jotform: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/jotform-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Jotform: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Jotform at mcp.jotform.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Jotform (registry title: jotform.com) | | --- | --- | | Domain | jotform.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 655 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for jotform.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.jotform.com/ | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,195 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:56Z https://mcp.jotform.com/ sent initialize result auth-required (HTTP 401) 1057 ms - 20:01:31Z https://mcp.jotform.com/ sent initialize result auth-required (HTTP 401) 1195 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.jotform.com | | Authorization server metadata | oauth2.jotform.com | | Registration endpoint | https://oauth2.jotform.com/register-public-client | ### The sign-in route, step by step 1. Request `https://mcp.jotform.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.jotform.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://oauth2.jotform.com/register-public-client` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Jotform. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.jotform/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jotform-com/index.md) ## Sources - [Ora score page for jotform.com](https://ora.ai/score/jotform.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Where Jotform was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.jotform%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=jotform), read 4 November 2026 - [Jotform website](https://jotform.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "JumpCloud MCP server | Agent MCP Directory" description: "JumpCloud: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Identity & Auth." canonical: https://agentmcpdirectory.com/directory/jumpcloud-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # JumpCloud MCP server | Agent MCP Directory > JumpCloud: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Identity & Auth. Source: https://agentmcpdirectory.com/directory/jumpcloud-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # JumpCloud: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for JumpCloud at mcp.jumpcloud.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | JumpCloud (registry title: jumpcloud.com) | | --- | --- | | Domain | jumpcloud.com | | Category | Identity & Auth (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,709 on the list of 4 November 2026 | | Ora score | 60, grade C; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for jumpcloud.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.jumpcloud.com/v1 | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 926 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:59Z https://mcp.jumpcloud.com/v1 sent initialize result auth-required (HTTP 401) 539 ms - 20:01:35Z https://mcp.jumpcloud.com/v1 sent initialize result auth-required (HTTP 401) 926 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.jumpcloud.com/.well-known/oauth-protected-resource/v1" | | Protected resource metadata | mcp.jumpcloud.com | | Authorization server metadata | mcp.jumpcloud.com | | Registration endpoint | https://mcp.jumpcloud.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.jumpcloud.com/v1` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.jumpcloud.com/.well-known/oauth-protected-resource/v1` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.jumpcloud.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for JumpCloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: jumpcloud.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.jumpcloud/jumpcloud-genai | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/jumpcloud-com/index.md) ## Sources - [Ora score page for jumpcloud.com](https://ora.ai/score/jumpcloud.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/score) - [Where JumpCloud was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.jumpcloud%2Fjumpcloud-genai), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=jumpcloud), read 4 November 2026 - [JumpCloud website](https://jumpcloud.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "JustCall MCP server | Agent MCP Directory" description: "JustCall: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/justcall-host site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # JustCall MCP server | Agent MCP Directory > JustCall: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/justcall-host Site: Agent MCP Directory Last reviewed: 2026-11-05 # JustCall: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for JustCall at mcp.justcall.host answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | JustCall (registry title: JustCall MCP Server) | | --- | --- | | Domain | justcall.host | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for justcall.host when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.justcall.host/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 234 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:01Z https://mcp.justcall.host/mcp sent initialize result auth-required (HTTP 401) 437 ms - 20:03:22Z https://mcp.justcall.host/mcp sent initialize result auth-required (HTTP 401) 234 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Authorization server metadata | mcp.justcall.host | | Registration endpoint | https://api.justcall.io/v2.1/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.justcall.host/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://api.justcall.io/v2.1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for JustCall. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: host.justcall.mcp/justcall-mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/justcall-host/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=justcall), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "JustClaw-It MCP server | Agent MCP Directory" description: "JustClaw-It has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/justclaw-it-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # JustClaw-It MCP server | Agent MCP Directory > JustClaw-It has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/justclaw-it-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # JustClaw-It: MCP server, CLI and agent surfaces Yes: JustClaw-It runs a public MCP server at justclaw.it.com that listed 9 tools to a client with no credentials on 4 November 2026. Examples: search\_components, find\_similar, list\_categories. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | JustClaw-It | | --- | --- | | Domain | justclaw.it.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 1,016 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for justclaw.it.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://justclaw.it.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | justclaw-it 1.30.0 | | Capabilities | experimental, prompts, resources, tools | | Tools | 9 | | Resources | 8 | | Prompts | 4 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 956 ms over 1 attempt | ### Tools listed 9 tools - search\_components - find\_similar - list\_categories - get\_component - check\_component\_security - library\_stats - list\_licenses - get\_component\_bundle - compose\_starter ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:56Z https://justclaw.it.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 645 ms - 20:01:32Z https://justclaw.it.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 956 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://justclaw.it.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for JustClaw-It. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not found in the directory run's own probe. | | A2A agent card | Not found in the directory run's own probe. | | A2A agent card (older path) | Not found in the directory run's own probe. | | agents.json | Not found in the directory run's own probe. | | OAuth authorization server metadata | Not found in the directory run's own probe. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.it.justclaw/justclaw-it, com.it.scorptech/x402, io.github.AshutoshRaj97/agentready-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/justclaw-it-com/index.md) ## Sources - [Where JustClaw-It was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.it.justclaw%2Fjustclaw-it), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=justclaw), read 4 November 2026 - [JustClaw-It website](https://justclaw.it.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "K9s MCP server | Agent MCP Directory" description: "Does K9s have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/k9scli-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # K9s MCP server | Agent MCP Directory > Does K9s have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/k9scli-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # K9s: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for K9s (k9scli.io), so the connector had nothing to connect to. Ora's cached score for k9scli.io is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | K9s (registry title: k9scli.io) | | --- | --- | | Domain | k9scli.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for k9scli.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for K9s. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for k9scli.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for K9s. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/k9scli-io/index.md) ## Sources - [Ora score page for k9scli.io](https://ora.ai/score/k9scli.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/leaderboard) - [Where K9s was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [K9s website](https://k9scli.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kaiv MCP server | Agent MCP Directory" description: "Kaiv has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kaiv-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kaiv MCP server | Agent MCP Directory > Kaiv has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kaiv-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kaiv: MCP server, CLI and agent surfaces Yes: Kaiv runs a public MCP server at api.kaiv.ai that listed 3 tools to a client with no credentials on 4 November 2026. Examples: check\_feature\_support, get\_feature\_by\_id, search\_features. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Kaiv (registry title: Kaiva Bridge) | | --- | --- | | Domain | kaiv.ai | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for kaiv.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Can I Use 1.0.0 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 407 ms over 1 attempt | ### Tools listed 3 tools - check\_feature\_support - get\_feature\_by\_id - search\_features ### Connector log 4 connections on 4 November 2026, read-only methods only - 19:58:02Z https://api.kaiv.ai/api/bridge/manage/mcp sent initialize, notifications/initialized, tools/list result initialized-no-tools (HTTP 200) 617 ms - 19:58:02Z https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 375 ms - 20:03:22Z https://api.kaiv.ai/api/bridge/manage/mcp sent initialize, notifications/initialized, tools/list result initialized-no-tools (HTTP 200) 462 ms - 20:03:23Z https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 407 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kaiv. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.kaiv/bridge, ai.kaiv/can-i-use, ai.kaiv/dependency-trust and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kaiv-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=kaiv), read 4 November 2026 - [Kaiv website](https://kaiv.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kajabi MCP server | Agent MCP Directory" description: "Kajabi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kajabi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kajabi MCP server | Agent MCP Directory > Kajabi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kajabi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kajabi: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Kajabi at mcp.kajabi.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Kajabi | | --- | --- | | Domain | kajabi.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 65, grade C; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kajabi.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.kajabi.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,063 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:03Z https://mcp.kajabi.com/mcp sent initialize result auth-required (HTTP 401) 1044 ms - 20:03:23Z https://mcp.kajabi.com/mcp sent initialize result auth-required (HTTP 401) 1063 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Doorkeeper", error="invalid_token", error_description="The access token is invalid", resource_metadata="https://mcp.kajabi.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.kajabi.com | | Authorization server metadata | mcp.kajabi.com | | Registration endpoint | https://mcp.kajabi.com/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.kajabi.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.kajabi.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.kajabi.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kajabi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.kajabi/kajabi | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kajabi-com/index.md) ## Sources - [Ora score page for kajabi.com](https://ora.ai/score/kajabi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/leaderboard) - [Where Kajabi was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.kajabi%2Fkajabi), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=kajabi), read 4 November 2026 - [Kajabi website](https://kajabi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kanbanize MCP server | Agent MCP Directory" description: "Does Kanbanize have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kanbanize-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kanbanize MCP server | Agent MCP Directory > Does Kanbanize have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/kanbanize-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kanbanize: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Kanbanize (kanbanize.com), so the connector had nothing to connect to. Ora's cached score for kanbanize.com is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Kanbanize (registry title: kanbanize.com) | | --- | --- | | Domain | kanbanize.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kanbanize.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Kanbanize. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for kanbanize.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Kanbanize. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kanbanize-com/index.md) ## Sources - [Ora score page for kanbanize.com](https://ora.ai/score/kanbanize.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Where Kanbanize was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Kanbanize website](https://kanbanize.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Karate Labs MCP server | Agent MCP Directory" description: "Does Karate Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/karatelabs-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Karate Labs MCP server | Agent MCP Directory > Does Karate Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/karatelabs-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Karate Labs: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Karate Labs (karatelabs.io), so the connector had nothing to connect to. Ora's cached score for karatelabs.io is 63, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Karate Labs (registry title: karatelabs.io) | | --- | --- | | Domain | karatelabs.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for karatelabs.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Karate Labs. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for karatelabs.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Karate Labs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/karatelabs-io/index.md) ## Sources - [Ora score page for karatelabs.io](https://ora.ai/score/karatelabs.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where Karate Labs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Karate Labs website](https://karatelabs.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "kari MCP server | Agent MCP Directory" description: "kari has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kari-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # kari MCP server | Agent MCP Directory > kari has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kari-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # kari: MCP server, CLI and agent surfaces Yes: kari runs a public MCP server at mcp.kari.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: find\_city, find\_stores, search\_products. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | kari (registry title: kari catalog) | | --- | --- | | Domain | kari.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for kari.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.kari.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | kari-catalog 1.0.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 890 ms over 1 attempt | ### Tools listed 5 tools - find\_city - find\_stores - search\_products - get\_product - check\_availability ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:05Z https://mcp.kari.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 3072 ms - 20:03:23Z https://mcp.kari.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 890 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.kari.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for kari. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.kari/catalog | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kari-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=kari), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Keenable MCP server | Agent MCP Directory" description: "Keenable has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/keenable-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Keenable MCP server | Agent MCP Directory > Keenable has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/keenable-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Keenable: MCP server, CLI and agent surfaces Yes: Keenable runs a public MCP server at api.keenable.ai that listed 2 tools to a client with no credentials on 4 November 2026. Examples: search\_web\_pages, fetch\_page\_content. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for keenable.ai is 68, grade C, read on 5 November 2026. ## Fact sheet | Company | Keenable (registry title: Keenable Web Search) | | --- | --- | | Domain | keenable.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 68, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for keenable.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.keenable.ai/mcp?keenable_title=mcp-registry | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | keenable-mcp-server 0.2.1 | | Capabilities | tools, resources, prompts | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 953 ms over 1 attempt | ### Tools listed 2 tools - search\_web\_pages - fetch\_page\_content ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:03Z https://api.keenable.ai/mcp?keenable\_title=mcp-registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1230 ms - 20:03:23Z https://api.keenable.ai/mcp?keenable\_title=mcp-registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 953 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.keenable.ai/mcp?keenable_title=mcp-registry` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Keenable. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: docs.keenable.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.keenable/web-search | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/keenable-ai/index.md) ## Sources - [Ora score page for keenable.ai](https://ora.ai/score/keenable.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=keenable), read 4 November 2026 - [Keenable website](https://keenable.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kema MCP server | Agent MCP Directory" description: "Kema: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kema-studio-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kema MCP server | Agent MCP Directory > Kema: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kema-studio-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kema: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Kema at mcp.kema-studio.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Kema (registry title: Kema Invoice) | | --- | --- | | Domain | kema-studio.com | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for kema-studio.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.kema-studio.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 820 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:04Z https://mcp.kema-studio.com/api/mcp sent initialize result auth-required (HTTP 401) 1290 ms - 20:03:24Z https://mcp.kema-studio.com/api/mcp sent initialize result auth-required (HTTP 401) 820 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.kema-studio.com/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | mcp.kema-studio.com | | Authorization server metadata | mamhezkdaqxdhfcwcgew.supabase.co | | Registration endpoint | https://mamhezkdaqxdhfcwcgew.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://mcp.kema-studio.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.kema-studio.com/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mamhezkdaqxdhfcwcgew.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kema. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.kema-studio/invoice, com.kema-studio/olia | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kema-studio-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=kema-studio), read 4 November 2026 - [Kema website](https://kema-studio.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "KERNEL MCP server | Agent MCP Directory" description: "Does KERNEL have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kernel-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # KERNEL MCP server | Agent MCP Directory > Does KERNEL have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/kernel-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # KERNEL: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for KERNEL (kernel.sh), so the connector had nothing to connect to. Ora's cached score for kernel.sh is 86, grade A, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | KERNEL (registry title: kernel.sh) | | --- | --- | | Domain | kernel.sh | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 86, grade A; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kernel.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for KERNEL. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for kernel.sh, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for KERNEL. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: kernel.sh/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kernel-sh/index.md) ## Sources - [Ora score page for kernel.sh](https://ora.ai/score/kernel.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Where KERNEL was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [KERNEL website](https://kernel.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Keyframe Labs MCP server | Agent MCP Directory" description: "Does Keyframe Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/keyframelabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Keyframe Labs MCP server | Agent MCP Directory > Does Keyframe Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/keyframelabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Keyframe Labs: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Keyframe Labs (keyframelabs.com), so the connector had nothing to connect to. Ora's cached score for keyframelabs.com is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Keyframe Labs (registry title: keyframelabs.com) | | --- | --- | | Domain | keyframelabs.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for keyframelabs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Keyframe Labs. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for keyframelabs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Keyframe Labs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/keyframelabs-com/index.md) ## Sources - [Ora score page for keyframelabs.com](https://ora.ai/score/keyframelabs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 October 2026, read from GET /api/leaderboard) - [Where Keyframe Labs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Keyframe Labs website](https://keyframelabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "KeystoneJS MCP server | Agent MCP Directory" description: "Does KeystoneJS have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/keystonejs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # KeystoneJS MCP server | Agent MCP Directory > Does KeystoneJS have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/keystonejs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # KeystoneJS: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for KeystoneJS (keystonejs.com), so the connector had nothing to connect to. Ora's cached score for keystonejs.com is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | KeystoneJS (registry title: keystonejs.com) | | --- | --- | | Domain | keystonejs.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for keystonejs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for KeystoneJS. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for keystonejs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for KeystoneJS. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/keystonejs-com/index.md) ## Sources - [Ora score page for keystonejs.com](https://ora.ai/score/keystonejs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/leaderboard) - [Where KeystoneJS was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [KeystoneJS website](https://keystonejs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kili Technology MCP server | Agent MCP Directory" description: "Does Kili Technology have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kili-technology-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kili Technology MCP server | Agent MCP Directory > Does Kili Technology have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/kili-technology-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kili Technology: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Kili Technology (kili-technology.com), so the connector had nothing to connect to. Ora's cached score for kili-technology.com is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Kili Technology (registry title: kili-technology.com) | | --- | --- | | Domain | kili-technology.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 8 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kili-technology.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Kili Technology. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for kili-technology.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Kili Technology. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kili-technology-com/index.md) ## Sources - [Ora score page for kili-technology.com](https://ora.ai/score/kili-technology.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 September 2026, read from GET /api/leaderboard) - [Where Kili Technology was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Kili Technology website](https://kili-technology.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kiln MCP server | Agent MCP Directory" description: "Kiln: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kiln3d-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kiln MCP server | Agent MCP Directory > Kiln: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kiln3d-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kiln: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Kiln at api.kiln3d.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Kiln | | --- | --- | | Domain | kiln3d.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for kiln3d.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.kiln3d.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 675 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:05Z https://api.kiln3d.com/mcp sent initialize result auth-required (HTTP 401) 1228 ms - 20:03:24Z https://api.kiln3d.com/mcp sent initialize result auth-required (HTTP 401) 675 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.kiln3d.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.kiln3d.com | | Authorization server metadata | api.kiln3d.com | | Registration endpoint | https://api.kiln3d.com/register | ### The sign-in route, step by step 1. Request `https://api.kiln3d.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.kiln3d.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.kiln3d.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kiln. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kiln3d-com/index.md) ## Sources - [Where Kiln was found](https://github.com/mcp/codeofaxel/Kiln), read 4 November 2026 - [Kiln website](https://kiln3d.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kin MCP server | Agent MCP Directory" description: "Kin: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kinlab-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kin MCP server | Agent MCP Directory > Kin: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kinlab-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kin: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Kin at app.kinlab.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Kin | | --- | --- | | Domain | kinlab.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for kinlab.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.kinlab.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,060 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:05Z https://app.kinlab.ai/mcp sent initialize result auth-required (HTTP 401) 1320 ms - 20:03:25Z https://app.kinlab.ai/mcp sent initialize result auth-required (HTTP 401) 1060 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.kinlab.ai/.well-known/oauth-protected-resource/mcp", scope="mcp offline_access" | | Protected resource metadata | app.kinlab.ai | | Authorization server metadata | app.kinlab.ai | | Registration endpoint | https://app.kinlab.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://app.kinlab.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.kinlab.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.kinlab.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.kinlab/kin | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kinlab-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=kinlab), read 4 November 2026 - [Kin website](https://kinlab.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kinsta® MCP server | Agent MCP Directory" description: "Kinsta®: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/kinsta-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kinsta® MCP server | Agent MCP Directory > Kinsta®: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/kinsta-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kinsta®: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Kinsta®; the connector's guess at mcp.kinsta.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Kinsta® (registry title: kinsta.com) | | --- | --- | | Domain | kinsta.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kinsta.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.kinsta.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 785 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:05Z https://mcp.kinsta.com/mcp sent initialize result auth-required (HTTP 401) 851 ms - 20:03:25Z https://mcp.kinsta.com/mcp sent initialize result auth-required (HTTP 401) 785 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.kinsta.com/.well-known/oauth-protected-resource/mcp", scope="mcp:tools" | | Protected resource metadata | mcp.kinsta.com | | Authorization server metadata | mcp.kinsta.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.kinsta.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.kinsta.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kinsta®. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kinsta-com/index.md) ## Sources - [Ora score page for kinsta.com](https://ora.ai/score/kinsta.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Kinsta® was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Kinsta® website](https://kinsta.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kissflow MCP server | Agent MCP Directory" description: "Does Kissflow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kissflow-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kissflow MCP server | Agent MCP Directory > Does Kissflow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/kissflow-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kissflow: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Kissflow (kissflow.com), so the connector had nothing to connect to. Ora's cached score for kissflow.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Kissflow (registry title: kissflow.com) | | --- | --- | | Domain | kissflow.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kissflow.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Kissflow. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for kissflow.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Kissflow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kissflow-com/index.md) ## Sources - [Ora score page for kissflow.com](https://ora.ai/score/kissflow.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where Kissflow was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Kissflow website](https://kissflow.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kitemaker MCP server | Agent MCP Directory" description: "Does Kitemaker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kitemaker-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kitemaker MCP server | Agent MCP Directory > Does Kitemaker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/kitemaker-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kitemaker: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Kitemaker (kitemaker.co), so the connector had nothing to connect to. Ora's cached score for kitemaker.co is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Kitemaker (registry title: kitemaker.co) | | --- | --- | | Domain | kitemaker.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kitemaker.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Kitemaker. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for kitemaker.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Kitemaker. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kitemaker-co/index.md) ## Sources - [Ora score page for kitemaker.co](https://ora.ai/score/kitemaker.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Kitemaker was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Kitemaker website](https://kitemaker.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Klavis MCP server | Agent MCP Directory" description: "Klavis: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/klavis-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Klavis MCP server | Agent MCP Directory > Klavis: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/klavis-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Klavis: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Klavis at strata.klavis.ai asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Klavis (registry title: klavis.ai) | | --- | --- | | Domain | klavis.ai | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 71, grade B; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for klavis.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://strata.klavis.ai/mcp/ | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 880 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:06Z https://strata.klavis.ai/mcp/ sent initialize result auth-required-no-oauth (HTTP 401) 1180 ms - 20:03:25Z https://strata.klavis.ai/mcp/ sent initialize result auth-required-no-oauth (HTTP 401) 880 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://strata.klavis.ai/mcp/` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Klavis. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.klavis/strata | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/klavis-ai/index.md) ## Sources - [Ora score page for klavis.ai](https://ora.ai/score/klavis.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where Klavis was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.klavis%2Fstrata), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=klavis), read 4 November 2026 - [Klavis website](https://klavis.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kodza MCP server | Agent MCP Directory" description: "Kodza has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kodza-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kodza MCP server | Agent MCP Directory > Kodza has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kodza-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kodza: MCP server, CLI and agent surfaces Yes: Kodza runs a public MCP server at kodza.dev that listed 2 tools to a client with no credentials on 4 November 2026. Examples: search\_components, get\_component. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Kodza | | --- | --- | | Domain | kodza.dev | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for kodza.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://kodza.dev/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | kodza 0.1.6 | | Capabilities | tools, prompts | | Tools | 2 | | Resources | 0 | | Prompts | 3 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,313 ms over 1 attempt | ### Tools listed 2 tools - search\_components - get\_component ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:07Z https://kodza.dev/api/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1413 ms - 20:03:26Z https://kodza.dev/api/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1313 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://kodza.dev/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kodza. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.kodza/kodza | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kodza-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=kodza), read 4 November 2026 - [Kodza website](https://kodza.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Komodor MCP server | Agent MCP Directory" description: "Komodor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/komodor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Komodor MCP server | Agent MCP Directory > Komodor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/komodor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Komodor: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Komodor; the connector's guess at mcp.komodor.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Komodor (registry title: komodor.com) | | --- | --- | | Domain | komodor.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 44, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for komodor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.komodor.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,172 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:06Z https://mcp.komodor.com/mcp sent initialize result auth-required (HTTP 401) 1101 ms - 20:03:26Z https://mcp.komodor.com/mcp sent initialize result auth-required (HTTP 401) 1172 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://mcp.komodor.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.komodor.com | | Authorization server metadata | mcp.komodor.com | | Registration endpoint | https://mcp.komodor.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.komodor.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.komodor.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.komodor.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Komodor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/komodor-com/index.md) ## Sources - [Ora score page for komodor.com](https://ora.ai/score/komodor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Komodor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Komodor website](https://komodor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kong MCP server | Agent MCP Directory" description: "Kong: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/konghq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kong MCP server | Agent MCP Directory > Kong: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/konghq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kong: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Kong at global.mcp.konghq.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Kong (registry title: Kong Konnect) | | --- | --- | | Domain | konghq.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 5,997 on the list of 4 November 2026 | | Ora score | 71, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for konghq.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://global.mcp.konghq.com/ | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,881 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:11Z https://global.mcp.konghq.com/ sent initialize result auth-required (HTTP 401) 1682 ms - 20:01:49Z https://global.mcp.konghq.com/ sent initialize result auth-required (HTTP 401) 1881 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://global.mcp.konghq.com/.well-known/oauth-protected-resource" | | Protected resource metadata | global.mcp.konghq.com | | Authorization server metadata | konnect-global.us.identity.konghq.com | | Registration endpoint | https://konnect-global.us.identity.konghq.com/oauth2/v1/clients | ### The sign-in route, step by step 1. Request `https://global.mcp.konghq.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://global.mcp.konghq.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://konnect-global.us.identity.konghq.com/oauth2/v1/clients` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kong. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.konghq/konnect | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/konghq-com/index.md) ## Sources - [Ora score page for konghq.com](https://ora.ai/score/konghq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Kong was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.konghq%2Fkonnect), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=konghq), read 4 November 2026 - [Kong website](https://konghq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Koyeb MCP server | Agent MCP Directory" description: "Does Koyeb have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/koyeb-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Koyeb MCP server | Agent MCP Directory > Does Koyeb have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/koyeb-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Koyeb: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Koyeb (koyeb.com), so the connector had nothing to connect to. Ora's cached score for koyeb.com is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Koyeb | | --- | --- | | Domain | koyeb.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for koyeb.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Koyeb. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for koyeb.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Koyeb. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/koyeb-com/index.md) ## Sources - [Ora score page for koyeb.com](https://ora.ai/score/koyeb.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Koyeb was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Koyeb website](https://koyeb.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kragos MCP server | Agent MCP Directory" description: "Kragos: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kragos-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kragos MCP server | Agent MCP Directory > Kragos: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kragos-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kragos: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Kragos at stempa.kragos.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Kragos (registry title: STEMPA) | | --- | --- | | Domain | kragos.app | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for kragos.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://stempa.kragos.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,582 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:07Z https://stempa.kragos.app/mcp sent initialize result auth-required (HTTP 401) 1730 ms - 20:03:27Z https://stempa.kragos.app/mcp sent initialize result auth-required (HTTP 401) 1582 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://stempa.kragos.app/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | stempa.kragos.app | | Authorization server metadata | stempa.kragos.app | | Registration endpoint | https://stempa.kragos.app/register | ### The sign-in route, step by step 1. Request `https://stempa.kragos.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://stempa.kragos.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://stempa.kragos.app/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kragos. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.kragos/stempa | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kragos-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=kragos), read 4 November 2026 - [Kragos website](https://kragos.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kraken MCP server | Agent MCP Directory" description: "Kraken has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kraken-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kraken MCP server | Agent MCP Directory > Kraken has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kraken-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kraken: MCP server, CLI and agent surfaces Yes: Kraken runs a public MCP server at docs.kraken.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: search\_kraken\_developers, query\_docs\_filesystem\_kraken\_developers, submit\_feedback. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for kraken.com is 82, grade B, read on 5 November 2026. ## Fact sheet | Company | Kraken (registry title: kraken.com) | | --- | --- | | Domain | kraken.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 1,961 on the list of 4 November 2026 | | Ora score | 82, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for kraken.com, a vendor-published score) | | Company found through | the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://docs.kraken.com/mcp | | --- | --- | | How it was found | listed in the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Kraken Developers 1.0.0 | | Capabilities | tools, resources | | Tools | 3 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,175 ms over 1 attempt | ### Tools listed 3 tools - search\_kraken\_developers - query\_docs\_filesystem\_kraken\_developers - submit\_feedback ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:58Z https://docs.kraken.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1178 ms - 20:01:34Z https://docs.kraken.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1175 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://docs.kraken.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kraken. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.kraken.com (JSON, via the shared crawl). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: kraken.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: kraken.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kraken-com/index.md) ## Sources - [Ora score page for kraken.com](https://ora.ai/score/kraken.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Kraken was found](https://kraken.com/.well-known/mcp.json), read 4 November 2026 - [Kraken website](https://kraken.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kubecost MCP server | Agent MCP Directory" description: "Does Kubecost have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kubecost-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kubecost MCP server | Agent MCP Directory > Does Kubecost have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/kubecost-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kubecost: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Kubecost (kubecost.com), so the connector had nothing to connect to. Ora's cached score for kubecost.com is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Kubecost (registry title: kubecost.com) | | --- | --- | | Domain | kubecost.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for kubecost.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Kubecost. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for kubecost.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Kubecost. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kubecost-com/index.md) ## Sources - [Ora score page for kubecost.com](https://ora.ai/score/kubecost.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Kubecost was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Kubecost website](https://kubecost.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kujolang.ai MCP server | Agent MCP Directory" description: "Kujolang.ai has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/kujolang-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kujolang.ai MCP server | Agent MCP Directory > Kujolang.ai has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/kujolang-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kujolang.ai: MCP server, CLI and agent surfaces Yes: Kujolang.ai runs a public MCP server at mcp.kujolang.ai that listed 7 tools to a client with no credentials on 4 November 2026. Examples: get\_kujo\_overview, list\_ecosystem, search\_kujo\_catalog. It speaks streamable-http, protocol 2026-07-28. Ora's cached score for kujolang.ai is 55, grade C, read on 5 November 2026. ## Fact sheet | Company | Kujolang.ai (registry title: Kujolang.ai MCP) | | --- | --- | | Domain | kujolang.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 55, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for kujolang.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.kujolang.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | kujolang-mcp 0.2.0 | | Capabilities | prompts, resources, tools | | Tools | 7 | | Resources | 6 | | Prompts | 3 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 275 ms over 1 attempt | ### Tools listed 7 tools - get\_kujo\_overview - list\_ecosystem - search\_kujo\_catalog - get\_catalog\_item - recommend\_kujo\_stack - get\_installation - list\_webops\_capabilities ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:07Z https://mcp.kujolang.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result initialized-no-tools (HTTP 200) 511 ms - 20:03:26Z https://mcp.kujolang.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 275 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.kujolang.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kujolang.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/kujolang-ai/index.md) ## Sources - [Ora score page for kujolang.ai](https://ora.ai/score/kujolang.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/score) - [Where Kujolang.ai was found](https://github.com/mcp/kujolang/kujolang-mcp), read 4 November 2026 - [Kujolang.ai website](https://kujolang.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lambda MCP server | Agent MCP Directory" description: "Does Lambda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lambdalabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lambda MCP server | Agent MCP Directory > Does Lambda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/lambdalabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lambda: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Lambda (lambdalabs.com), so the connector had nothing to connect to. Ora's cached score for lambdalabs.com is 44, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Lambda | | --- | --- | | Domain | lambdalabs.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 44, grade D; Ora scanned the domain on 13 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for lambdalabs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Lambda. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for lambdalabs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Lambda. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lambdalabs-com/index.md) ## Sources - [Ora score page for lambdalabs.com](https://ora.ai/score/lambdalabs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 13 August 2026, read from GET /api/leaderboard) - [Where Lambda was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Lambda website](https://lambdalabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lambdatest MCP server | Agent MCP Directory" description: "Lambdatest has an open MCP server with 88 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lambdatest-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lambdatest MCP server | Agent MCP Directory > Lambdatest has an open MCP server with 88 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lambdatest-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lambdatest: MCP server, CLI and agent surfaces Yes: Lambdatest runs a public MCP server at mcp.lambdatest.com that listed 88 tools to a client with no credentials on 4 November 2026. Examples: upload\_app, generateHyperExecuteYAML, answerHyperExecuteQuery. It speaks streamable-http, protocol 2025-03-26. Ora's cached score for lambdatest.com is 68, grade C, read on 5 November 2026. ## Fact sheet | Company | Lambdatest (registry title: TestMu AI (formerly LambdaTest)) | | --- | --- | | Domain | lambdatest.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 68, grade C; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for lambdatest.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.lambdatest.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | TestMu AI MCP 1.0.7 | | Capabilities | tools, resources | | Tools | 88 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,645 ms over 1 attempt | ### Tools listed 88 tools; the first 40 names are recorded - upload\_app - generateHyperExecuteYAML - answerHyperExecuteQuery - getHyperExecuteJobInfo - getHyperExecuteJobSessions - getAccessibilityReport - analyzeAppViaTunnel - buildLocalAppForAnalysis - getAutomationTestDetails - getAutomationTestCommandLogs - getAutomationTestNetworkLogs - getAutomationTestBrowserConsoleLogs - getAutomationTestSeleniumLogs - automationQuery - updateBuild - stopBuild - deleteBuild - triggerSuiteRun - getSuiteOverview - getSupportedPlatforms - listTunnels - stopTunnel - deleteSession - updateSession - stopSession - getSessionScreenshots - getSessionVideo - getSessionV2CommandLogs - getSessionV2SeleniumLogs - postSessionExceptions - postTestExceptions - getLiveSessionLogs - getOrgConcurrency - getAnalyticsData - getFlakyTests - getTestTrends - getAnalyticsErrors - deletePrerunFile - deleteUserFile - listUploadedApps ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:08Z https://mcp.lambdatest.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1695 ms - 20:03:28Z https://mcp.lambdatest.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1645 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.lambdatest.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lambdatest. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lambdatest-com/index.md) ## Sources - [Ora score page for lambdatest.com](https://ora.ai/score/lambdatest.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/score) - [Lambdatest website](https://lambdatest.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Laminar MCP server | Agent MCP Directory" description: "Does Laminar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/laminar-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Laminar MCP server | Agent MCP Directory > Does Laminar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/laminar-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Laminar: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Laminar (laminar.sh), so the connector had nothing to connect to. Ora's cached score for laminar.sh is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Laminar (registry title: laminar.sh) | | --- | --- | | Domain | laminar.sh | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for laminar.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Laminar. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for laminar.sh, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Laminar. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/laminar-sh/index.md) ## Sources - [Ora score page for laminar.sh](https://ora.ai/score/laminar.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Laminar was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Laminar website](https://laminar.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lanesurf MCP server | Agent MCP Directory" description: "Lanesurf: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Logistics & Supply Chain." canonical: https://agentmcpdirectory.com/directory/lanesurf-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lanesurf MCP server | Agent MCP Directory > Lanesurf: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Logistics & Supply Chain. Source: https://agentmcpdirectory.com/directory/lanesurf-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lanesurf: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Lanesurf at agent.lanesurf.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Lanesurf | | --- | --- | | Domain | lanesurf.com | | Category | Logistics & Supply Chain (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 56, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for lanesurf.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agent.lanesurf.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,017 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:08Z https://agent.lanesurf.com/mcp sent initialize result auth-required (HTTP 401) 1213 ms - 20:03:27Z https://agent.lanesurf.com/mcp sent initialize result auth-required (HTTP 401) 1017 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://agent.lanesurf.com/.well-known/oauth-protected-resource/mcp", scope="lanesurf" | | Protected resource metadata | agent.lanesurf.com | | Authorization server metadata | agent.lanesurf.com | | Registration endpoint | https://agent.lanesurf.com/oauth/register | ### The sign-in route, step by step 1. Request `https://agent.lanesurf.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://agent.lanesurf.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://agent.lanesurf.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lanesurf. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: docs.lanesurf.com (YAML, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.lanesurf/agent | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lanesurf-com/index.md) ## Sources - [Ora score page for lanesurf.com](https://ora.ai/score/lanesurf.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Lanesurf was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.lanesurf%2Fagent), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lanesurf), read 4 November 2026 - [Lanesurf website](https://lanesurf.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Last9 MCP server | Agent MCP Directory" description: "Does Last9 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/last9-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Last9 MCP server | Agent MCP Directory > Does Last9 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/last9-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Last9: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Last9 (last9.io), so the connector had nothing to connect to. Ora's cached score for last9.io is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Last9 (registry title: last9.io) | | --- | --- | | Domain | last9.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for last9.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Last9. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for last9.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Last9. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/last9-io/index.md) ## Sources - [Ora score page for last9.io](https://ora.ai/score/last9.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Last9 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Last9 website](https://last9.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LaunchDarkly MCP server | Agent MCP Directory" description: "LaunchDarkly has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/launchdarkly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LaunchDarkly MCP server | Agent MCP Directory > LaunchDarkly has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/launchdarkly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # LaunchDarkly: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for LaunchDarkly; the connector tried mcp.launchdarkly.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | LaunchDarkly | | --- | --- | | Domain | launchdarkly.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Tranco rank | 300 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for launchdarkly.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.launchdarkly.com/mcp | | --- | --- | | How it was found | mcp.launchdarkly.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,188 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://mcp.launchdarkly.com/mcp sent initialize result no-answer (HTTP 404) 1298 ms - 20:01:30Z https://mcp.launchdarkly.com/mcp sent initialize result no-answer (HTTP 404) 1188 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.launchdarkly.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for LaunchDarkly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/launchdarkly-com/index.md) ## Sources - [Ora score page for launchdarkly.com](https://ora.ai/score/launchdarkly.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where LaunchDarkly was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [LaunchDarkly website](https://launchdarkly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Layrcake MCP server | Agent MCP Directory" description: "Layrcake: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM." canonical: https://agentmcpdirectory.com/directory/layrcake-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Layrcake MCP server | Agent MCP Directory > Layrcake: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM. Source: https://agentmcpdirectory.com/directory/layrcake-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Layrcake: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Layrcake at mcp.layrcake.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Layrcake | | --- | --- | | Domain | layrcake.dev | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for layrcake.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.layrcake.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,414 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:09Z https://mcp.layrcake.dev/mcp sent initialize result auth-required (HTTP 401) 1370 ms - 20:03:28Z https://mcp.layrcake.dev/mcp sent initialize result auth-required (HTTP 401) 1414 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.layrcake.dev/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.layrcake.dev | | Authorization server metadata | api.layrcake.dev | | Registration endpoint | https://api.layrcake.dev/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.layrcake.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.layrcake.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.layrcake.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Layrcake. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.layrcake/layrcake | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/layrcake-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=layrcake), read 4 November 2026 - [Layrcake website](https://layrcake.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lazaretto MCP server | Agent MCP Directory" description: "Lazaretto has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lazaretto-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lazaretto MCP server | Agent MCP Directory > Lazaretto has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lazaretto-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lazaretto: MCP server, CLI and agent surfaces Yes: Lazaretto runs a public MCP server at lazaretto.dev that listed 10 tools to a client with no credentials on 4 November 2026. Examples: known\_bad\_lookup, check\_lockfile, scan\_artifact. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Lazaretto | | --- | --- | | Domain | lazaretto.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for lazaretto.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://lazaretto.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | lazaretto 1.0.0 | | Capabilities | tools | | Tools | 10 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 4,254 ms over 1 attempt | ### Tools listed 10 tools - known\_bad\_lookup - check\_lockfile - scan\_artifact - scan\_lockfile\_deep - scan\_mcp\_server - check\_mcp\_tools - find\_mcp\_servers - find\_attestation - verify\_attestation - get\_free\_key ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:09Z https://lazaretto.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1083 ms - 20:03:31Z https://lazaretto.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 4254 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://lazaretto.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lazaretto. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: lazaretto.dev (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lazaretto-dev/index.md) ## Sources - [Lazaretto website](https://lazaretto.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lazybird MCP server | Agent MCP Directory" description: "Lazybird: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/lazybird-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lazybird MCP server | Agent MCP Directory > Lazybird: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/lazybird-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lazybird: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Lazybird at api.lazybird.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Lazybird | | --- | --- | | Domain | lazybird.app | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for lazybird.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.lazybird.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,142 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:09Z https://api.lazybird.app/mcp sent initialize result auth-required (HTTP 401) 1241 ms - 20:03:28Z https://api.lazybird.app/mcp sent initialize result auth-required (HTTP 401) 1142 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.lazybird.app/.well-known/oauth-protected-resource/mcp", scope="lazybird" | | Protected resource metadata | api.lazybird.app | | Authorization server metadata | api.lazybird.app | | Registration endpoint | https://api.lazybird.app/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.lazybird.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.lazybird.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.lazybird.app/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lazybird. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.lazybird.app (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lazybird-app/index.md) ## Sources - [Lazybird website](https://lazybird.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Leash MCP server | Agent MCP Directory" description: "Leash: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lea-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Leash MCP server | Agent MCP Directory > Leash: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lea-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Leash: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Leash at secure.lea.sh answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Leash | | --- | --- | | Domain | lea.sh | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for lea.sh when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://secure.lea.sh/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,084 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:09Z https://secure.lea.sh/mcp sent initialize result auth-required (HTTP 401) 996 ms - 20:03:29Z https://secure.lea.sh/mcp sent initialize result auth-required (HTTP 401) 1084 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Leash", resource_metadata="https://secure.lea.sh/.well-known/oauth-protected-resource", scope="leash" | | Protected resource metadata | secure.lea.sh | | Authorization server metadata | secure.lea.sh | | Registration endpoint | https://secure.lea.sh/oauth/register | ### The sign-in route, step by step 1. Request `https://secure.lea.sh/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://secure.lea.sh/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://secure.lea.sh/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Leash. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lea-sh/index.md) ## Sources - [Leash website](https://lea.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Leadbase MCP server | Agent MCP Directory" description: "Leadbase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM." canonical: https://agentmcpdirectory.com/directory/leadbase-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Leadbase MCP server | Agent MCP Directory > Leadbase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM. Source: https://agentmcpdirectory.com/directory/leadbase-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Leadbase: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Leadbase at www.leadbase.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Leadbase (registry title: Leadbase \| AI B2B Lead Generation) | | --- | --- | | Domain | leadbase.io | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for leadbase.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.leadbase.io/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 546 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:09Z https://www.leadbase.io/api/mcp sent initialize result auth-required (HTTP 401) 816 ms - 20:03:29Z https://www.leadbase.io/api/mcp sent initialize result auth-required (HTTP 401) 546 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.leadbase.io/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | www.leadbase.io | | Authorization server metadata | www.leadbase.io | | Registration endpoint | https://www.leadbase.io/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://www.leadbase.io/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.leadbase.io/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://www.leadbase.io/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Leadbase. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/leadbase-io/index.md) ## Sources - [Leadbase website](https://leadbase.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Leadpages MCP server | Agent MCP Directory" description: "Leadpages: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/leadpages-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Leadpages MCP server | Agent MCP Directory > Leadpages: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/leadpages-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Leadpages: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Leadpages at mcp.leadpages.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Leadpages (registry title: leadpages.com) | | --- | --- | | Domain | leadpages.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 80, grade B; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for leadpages.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.leadpages.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,214 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:10Z https://mcp.leadpages.com/mcp sent initialize result auth-required (HTTP 401) 1255 ms - 20:03:30Z https://mcp.leadpages.com/mcp sent initialize result auth-required (HTTP 401) 1214 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.leadpages.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.leadpages.com | | Authorization server metadata | mcp.leadpages.com | | Registration endpoint | https://mcp.leadpages.com/api/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.leadpages.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.leadpages.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.leadpages.com/api/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Leadpages. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: leadpages.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: leadpages.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: leadpages.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.leadpages/leadpages-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/leadpages-com/index.md) ## Sources - [Ora score page for leadpages.com](https://ora.ai/score/leadpages.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/leaderboard) - [Where Leadpages was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.leadpages%2Fleadpages-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=leadpages), read 4 November 2026 - [Leadpages website](https://leadpages.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Leantime MCP server | Agent MCP Directory" description: "Does Leantime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/leantime-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Leantime MCP server | Agent MCP Directory > Does Leantime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/leantime-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Leantime: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Leantime (leantime.io), so the connector had nothing to connect to. Ora's cached score for leantime.io is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Leantime (registry title: leantime.io) | | --- | --- | | Domain | leantime.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for leantime.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Leantime. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for leantime.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Leantime. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: leantime.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/leantime-io/index.md) ## Sources - [Ora score page for leantime.io](https://ora.ai/score/leantime.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Leantime was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Leantime website](https://leantime.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Microsoft Learn MCP server | Agent MCP Directory" description: "Microsoft Learn has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/learn-microsoft-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Microsoft Learn MCP server | Agent MCP Directory > Microsoft Learn has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/learn-microsoft-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Microsoft Learn: MCP server, CLI and agent surfaces Yes: Microsoft Learn runs a public MCP server at learn.microsoft.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: microsoft\_docs\_search, microsoft\_code\_sample\_search, microsoft\_docs\_fetch. It speaks streamable-http, protocol 2025-06-18. A CLI is on record: azure-cli on pypi. ## Fact sheet | Company | Microsoft Learn | | --- | --- | | Domain | learn.microsoft.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 24, grade F; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for learn.microsoft.com, a vendor-published score) | | Company found through | the vendor's own documentation | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://learn.microsoft.com/api/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Microsoft Learn MCP Server 1.0.0 | | Capabilities | logging, prompts, resources, tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,027 ms over 1 attempt | | Documentation | learn.microsoft.com | ### Tools listed 3 tools - microsoft\_docs\_search - microsoft\_code\_sample\_search - microsoft\_docs\_fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:11Z https://learn.microsoft.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1088 ms - 20:03:30Z https://learn.microsoft.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1027 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://learn.microsoft.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | azure-cli on pypi (page) | | --- | --- | | Exists | yes | | Latest version | 2.92.0 | | Last publish | 3 November 2026 | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/learn-microsoft-com/index.md) ## Sources - [Microsoft Learn MCP documentation](https://learn.microsoft.com/en-us/training/support/mcp), read 4 November 2026 - [azure-cli on pypi](https://pypi.org/project/azure-cli/), read 4 November 2026 - [Ora score page for learn.microsoft.com](https://ora.ai/score/learn.microsoft.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/score) - [Microsoft Learn website](https://learn.microsoft.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with a digit | Agent MCP Directory" description: "4 companies starting with a digit: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/0 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with a digit | Agent MCP Directory > 4 companies starting with a digit: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/0 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with a digit 4 companies in the directory start with a digit: 2 listed tools to a client with no credentials, 2 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from 0xArchive to 3Dsellers. Each name links to its endpoint, auth type, tool list and sources. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 0xArchive 0xarchive.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 94 A | yes | not read | 2026-11-04 | | 1102tools 1102tools.com | Verified no auth | – | | – | not read | 2026-11-04 | | 2extract 2extract.com | Verified no auth | – | | – | not read | 2026-11-04 | | 3Dsellers 3dsellers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/0/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with A | Agent MCP Directory" description: "109 companies starting with A: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/a site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with A | Agent MCP Directory > 109 companies starting with A: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/a Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with A 109 companies in the directory start with the letter A: 22 listed tools to a client with no credentials, 49 answered with a sign-in challenge (not counted), and 3 have a CLI on record. This page lists rows 1 to 100, from a0.dev to Auvik. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | a0.dev a0.dev | None found | – | 51 C | – | no | 2026-11-04 | | Aaly aaly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Abstra abstra.io | No answer | – | 55 C | – | no | 2026-11-04 | | Account Executive Jobs accountexecutivejobs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Acquia acquia.com | None found | – | 69 C | – | no | 2026-11-04 | | Activeloop activeloop.ai | None found | – | 47 D | – | no | 2026-11-04 | | Actual AI actual.ai | None found | – | 81 B | yes | no | 2026-11-04 | | Adalo adalo.com | None found | – | 69 C | – | no | 2026-11-04 | | Aden adenhq.com | None found | – | 70 B | – | no | 2026-11-04 | | Adkit adkit.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | Adlicio tryadlicio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | yes | not read | 2026-11-04 | | Ads Uploader adsuploader.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AfterQuery afterquery.com | None found | – | 55 C | – | no | 2026-11-04 | | Agent Ready agent-ready.dev | Verified no auth | – | 94 A | yes | yes | 2026-11-04 | | Agentalog agentalog.com | Verified no auth | – | | yes | not read | 2026-11-04 | | AgentBIT agentbit.app | Verified no auth | – | | yes | not read | 2026-11-04 | | AgentData agentdata.run | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AgentHub agenthublabs.com | None found | – | 40 D | – | no | 2026-11-04 | | AgenticWebScore agenticwebscore.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Agilitycms agilitycms.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ahrefs ahrefs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | AI Mail MCP aimailmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | aictrl aictrl.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Aider aider.chat | None found | – | 41 D | – | no | 2026-11-04 | | aikstockdata aikstockdata.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Airbrake airbrake.io | None found | – | 49 C | – | not read | 2026-11-04 | | Airbyte airbyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Airport Lounge List airportloungelist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Airtable airtable.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Airweave airweave.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 78 B | – | no | 2026-11-04 | | AIS Trail aistrail.com | Verified no auth | – | | – | not read | 2026-11-04 | | Aiven aiven.io | None found | – | 76 B | – | no | 2026-11-04 | | Akiflow akiflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Alai getalai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Alchemy alchemy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | AlfaNest alfanestlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Alidns alidns.com | None found | – | | – | no | 2026-11-04 | | Allbirds allbirds.com | Verified no auth | – | 65 C | – | yes | 2026-11-04 | | Almxpp almxpp.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Alterlab alterlab.io | Verified no auth | – | | – | not read | 2026-11-04 | | AltoRank altorank.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Amazon Web Services aws.amazon.com | Verified no auth | awscli | 60 C | – | no | 2026-11-04 | | amCharts amcharts.com | Verified no auth | – | | – | not read | 2026-11-04 | | Amika amika.dev | None found | – | 55 C | – | no | 2026-11-04 | | Amplify amplify.is | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Amplitude amplitude.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | yes | no | 2026-11-04 | | Anchore anchore.com | None found | – | 46 D | – | no | 2026-11-04 | | Andi andiai.com | Sign-in required OAuth; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Anima animaapp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | AnomalyArmor anomalyarmor.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | yes | no | 2026-11-04 | | Ansvar ansvar.eu | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Antevo antevo.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Anthropic anthropic.com | None found | @anthropic-ai/claude-code | 71 B | – | no | 2026-11-04 | | Antwork antwork.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | yes | not read | 2026-11-04 | | Anurag anuragd.me | Verified no auth | – | 54 C | – | not read | 2026-11-04 | | Any.do any.do | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | yes | no | 2026-11-04 | | Anytype anytype.io | None found | – | 40 D | – | no | 2026-11-04 | | Apex AI Academy apexai.academy | Verified no auth | – | | – | not read | 2026-11-04 | | Apify apify.com | Sign-in required OAuth DCR; tools not seen, not counted | apify-cli | 96 A+ | yes | no | 2026-11-04 | | APITube apitube.io | Verified no auth | – | | – | not read | 2026-11-04 | | APIVerve apiverve.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Apollo GraphQL apollographql.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 80 B | – | no | 2026-11-04 | | Apollo.io apollo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Apoxy apoxy.dev | None found | – | 37 D | – | no | 2026-11-04 | | App Store Tracker appstoretracker.com | Verified no auth | – | 43 D | – | not read | 2026-11-04 | | Appcircle appcircle.io | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Appian appian.com | None found | – | 51 C | – | no | 2026-11-04 | | Appllama appllama.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 44 D | – | not read | 2026-11-04 | | AppmanAi appmanai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AppsFlyer appsflyer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | AppSignal appsignal.com | None found | – | 69 C | – | no | 2026-11-04 | | AppVeyor appveyor.com | None found | – | 40 D | – | no | 2026-11-04 | | Apricot apricot.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Aptible aptible.com | None found | – | 63 C | – | no | 2026-11-04 | | Ara ara.so | None found | – | 53 C | – | no | 2026-11-04 | | Archbee archbee.com | None found | – | 63 C | – | no | 2026-11-04 | | Archil archil.com | None found | – | 62 C | – | no | 2026-11-04 | | Arcmira arcmira.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ardent tryardent.com | None found | – | 71 B | – | no | 2026-11-04 | | Arga Labs argalabs.com | None found | – | 65 C | – | no | 2026-11-04 | | Arkm arkm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Arrumou arrumou.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Arthur arthur.ai | None found | – | 60 C | – | no | 2026-11-04 | | Artie artie.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Artillery artillery.io | None found | – | 55 C | – | no | 2026-11-04 | | Asana asana.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | ASO Atlas asoatlas.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Assembla assembla.com | None found | – | 52 C | – | no | 2026-11-04 | | AssemblyAI assemblyai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | yes | no | 2026-11-04 | | assistant-ui assistant-ui.com | None found | – | 79 B | – | no | 2026-11-04 | | Astro astro.build | Verified no auth | – | 52 C | – | no | 2026-11-04 | | AthenaHQ athenahq.ai | Verified no auth | – | 67 C | – | no | 2026-11-04 | | Atlassian atlassian.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Atom.com atom.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Attio attio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Audioscrape audioscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Autodesk autodesk.com | Verified no auth | – | 36 D | – | no | 2026-11-04 | | Automattic automattic.com | None found | – | 53 C | – | no | 2026-11-04 | | Autosana autosana.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Auvik auvik.com | None found | – | 54 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/a/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Letter A, page 2 | Agent MCP Directory" description: "109 companies starting with A: MCP server, CLI and OpenAPI status, checked 4 November 2026. Page 2 of 2. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/a/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Letter A, page 2 | Agent MCP Directory > 109 companies starting with A: MCP server, CLI and OpenAPI status, checked 4 November 2026. Page 2 of 2. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/a/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with A, page 2 109 companies in the directory start with the letter A: 22 listed tools to a client with no credentials, 49 answered with a sign-in challenge (not counted), and 3 have a CLI on record. This page lists rows 101 to 109, from Avalara to Azure. ## Rows 101 to 109 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Avalara avalara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | not read | 2026-11-04 | | aVenture aventure.vc | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | not read | 2026-11-04 | | Aviator aviator.co | None found | – | 55 C | – | no | 2026-11-04 | | Avo avo.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Award Travel Finder awardtravelfinder.com | No tools listed | – | | – | not read | 2026-11-04 | | AWS api.aws | Verified no auth | – | | – | not read | 2026-11-04 | | Axiom axiom.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | Axolo axolo.co | None found | – | 41 D | – | no | 2026-11-04 | | Azure azure.com | None found | – | 58 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/a/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with B | Agent MCP Directory" description: "62 companies starting with B: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/b site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with B | Agent MCP Directory > 62 companies starting with B: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/b Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with B 62 companies in the directory start with the letter B: 11 listed tools to a client with no credentials, 21 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from Backendless to BuyWhere. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Backendless backendless.com | None found | – | 48 C | – | no | 2026-11-04 | | Ball Ranks ballranks.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Barevalue barevalue.com | Verified no auth | – | | – | not read | 2026-11-04 | | Base44 base44.com | None found | – | 86 A | – | no | 2026-11-04 | | Basecamp basecamp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Basedash basedash.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Baserow baserow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Beam beam.cloud | None found | – | 74 B | – | no | 2026-11-04 | | Beancount.io beancount.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | Bear bear.app | None found | – | 40 D | – | no | 2026-11-04 | | beehiiv beehiiv.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | Beglaubigt beglaubigt.de | Verified no auth | – | 49 C | – | no | 2026-11-04 | | BeliefState beliefstate.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Benchspan benchspan.com | None found | – | 61 C | – | no | 2026-11-04 | | Bento bentoml.com | None found | – | 41 D | – | no | 2026-11-04 | | BestPrice bestprice.gr | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | Better Stack betterstack.com | No answer | – | 59 C | – | no | 2026-11-04 | | Betteruptime betteruptime.com | None found | – | 48 C | – | no | 2026-11-04 | | BGPT bgpt.pro | Verified no auth | – | | – | not read | 2026-11-04 | | Bibooks bibooks.org | Verified no auth | – | | – | not read | 2026-11-04 | | Bigdata.com bigdata.com | Sign-in required OAuth; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | BigPanda bigpanda.io | None found | – | 54 C | – | no | 2026-11-04 | | BigTime bigtime.net | None found | – | 41 D | – | no | 2026-11-04 | | Bird bird.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | no | 2026-11-04 | | Bitbucket bitbucket.org | None found | – | 34 D | – | no | 2026-11-04 | | Bitculator bitculator.com | Credential wall API key | – | | – | not read | 2026-11-04 | | Bitly bitly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Bitmovin bitmovin.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | Bitrise bitrise.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | BittleBits bittlebits.ai | No answer | – | | – | not read | 2026-11-04 | | Blacksmith blacksmith.sh | None found | – | 42 D | – | no | 2026-11-04 | | Bland bland.com | None found | – | 60 C | yes | no | 2026-11-04 | | Blaxel blaxel.ai | None found | – | 80 B | – | no | 2026-11-04 | | BlindPay blindpay.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | BlogSEO blogseo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Blueprism blueprism.com | None found | – | 59 C | – | no | 2026-11-04 | | Bolna AI bolna.ai | No answer | – | 63 C | – | no | 2026-11-04 | | Bolt bolt.new | None found | – | 65 C | – | no | 2026-11-04 | | Botcity botcity.dev | None found | – | 65 C | – | not read | 2026-11-04 | | Bowmark bowmark.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Box box.com | Sign-in required OAuth; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | brainattic brainattic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Brainboard brainboard.co | None found | – | 65 C | – | no | 2026-11-04 | | BreckenWander breckenwander.com | Verified no auth | – | | – | not read | 2026-11-04 | | briq briq.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Browser Use browser-use.com | Verified no auth | – | 91 A | yes | no | 2026-11-04 | | Browserbase browserbase.com | None found | – | 84 B | – | no | 2026-11-04 | | Browserbook browserbook.com | None found | – | 40 D | – | no | 2026-11-04 | | Browserless browserless.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | yes | 2026-11-04 | | Browserstack browserstack.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Bubble bubble.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 40 D | – | no | 2026-11-04 | | Bucket bucket.co | None found | – | 50 C | – | no | 2026-11-04 | | Bugasura bugasura.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | not read | 2026-11-04 | | BugSnag bugsnag.com | None found | – | 52 C | – | no | 2026-11-04 | | BuildBuddy buildbuddy.io | None found | – | 44 D | – | no | 2026-11-04 | | Builder.io builder.io | None found | – | 45 D | – | no | 2026-11-04 | | BuildJet buildjet.com | None found | – | 45 D | – | no | 2026-11-04 | | Buildkite buildkite.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Buildwithglide buildwithglide.com | None found | – | 45 D | – | no | 2026-11-04 | | BulkPublish bulkpublish.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | Bun bun.sh | None found | – | 49 C | – | no | 2026-11-04 | | BuyWhere buywhere.ai | Verified no auth | – | | yes | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/b/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with C | Agent MCP Directory" description: "119 companies starting with C: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/c site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with C | Agent MCP Directory > 119 companies starting with C: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/c Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with C 119 companies in the directory start with the letter C: 19 listed tools to a client with no credentials, 48 answered with a sign-in challenge (not counted), and 5 have a CLI on record. This page lists rows 1 to 100, from Calendly to Cortex. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Calendly calendly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | call4me call4.me | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Canva canva.com | Sign-in required OAuth DCR; tools not seen, not counted | @canva/cli | 42 D | – | no | 2026-11-04 | | Capacities capacities.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Carbon getcarbon.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Carrd carrd.co | None found | – | 42 D | – | no | 2026-11-04 | | Carrick carrick.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Casco casco.com | Verified no auth | – | 41 D | – | no | 2026-11-04 | | Castari castari.com | None found | – | 61 C | – | no | 2026-11-04 | | Catalystproject catalystproject.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Causely causely.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Cavyro cavyro.com | Credential wall API key | – | 73 B | yes | not read | 2026-11-04 | | Cedana cedana.ai | None found | – | 34 D | – | no | 2026-11-04 | | Cekura cekura.ai | None found | – | 82 B | – | no | 2026-11-04 | | Celigo celigo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | not read | 2026-11-04 | | Cerebrium cerebrium.ai | Verified no auth | – | 86 A | – | no | 2026-11-04 | | CertScore.ai certscore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Chainstack chainstack.com | Verified no auth | – | 71 B | – | not read | 2026-11-04 | | Chamber usechamber.io | None found | – | 68 C | – | no | 2026-11-04 | | Channel3 trychannel3.com | Verified no auth | – | 92 A | – | no | 2026-11-04 | | Charming charm.ing | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | yes | not read | 2026-11-04 | | Chatfuel chatfuel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | no | 2026-11-04 | | Chatway chatway.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Checkmarx checkmarx.com | None found | – | 61 C | – | no | 2026-11-04 | | Checkout.com checkout.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Chili Piper chilipiper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | Chonkie chonkie.ai | No answer | – | 43 D | – | no | 2026-11-04 | | Chronosphere chronosphere.io | None found | – | 67 C | – | no | 2026-11-04 | | Ciphyr ciphyr.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Circleback circleback.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | CircleCI circleci.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | yes | 2026-11-04 | | Cisco cisco.com | None found | – | 33 D | – | no | 2026-11-04 | | Clarm clarm.com | None found | – | 69 C | yes | no | 2026-11-04 | | Claude claude.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Clean Notes cleannotes.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Cleanlab cleanlab.ai | None found | – | 34 D | – | no | 2026-11-04 | | Clera getclera.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | ClickUp clickup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Clicon clicon.app | No answer | – | | – | not read | 2026-11-04 | | Clidey clidey.com | None found | – | 38 D | – | no | 2026-11-04 | | Cline cline.bot | None found | – | 77 B | – | no | 2026-11-04 | | Clino clino.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Clockify™ clockify.me | None found | – | 64 C | – | no | 2026-11-04 | | Close close.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | CloudBees cloudbees.com | None found | – | 68 C | – | no | 2026-11-04 | | Cloudchipr cloudchipr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Cloudflare cloudflare.com | Verified no auth | wrangler | 82 B | yes | yes | 2026-11-04 | | Cloudglue cloudglue.dev | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Cloudinary cloudinary.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Cloudthread cloudthread.io | None found | – | 41 D | – | not read | 2026-11-04 | | Clubhouse clubhouse.io | None found | – | 62 C | yes | no | 2026-11-04 | | Clueso clueso.io | Verified no auth | – | 78 B | – | no | 2026-11-04 | | Clutch.co clutch.co | Verified no auth | – | 21 F | – | no | 2026-11-04 | | cmux cmux.com | None found | – | 43 D | – | no | 2026-11-04 | | Coasts coasts.dev | None found | – | 40 D | – | no | 2026-11-04 | | CockroachDB cockroachlabs.com | None found | – | 69 C | – | no | 2026-11-04 | | Code Climate codeclimate.com | None found | – | 50 C | – | no | 2026-11-04 | | Codeanywhere codeanywhere.com | None found | – | 40 D | – | no | 2026-11-04 | | Codeberg.org codeberg.org | None found | – | 54 C | – | no | 2026-11-04 | | Codecov codecov.io | None found | – | 68 C | – | not read | 2026-11-04 | | Codefresh codefresh.io | None found | – | 50 C | – | no | 2026-11-04 | | Codeium codeium.com | None found | – | 49 C | – | no | 2026-11-04 | | Codemagic codemagic.io | None found | – | 58 C | – | no | 2026-11-04 | | Coder coder.com | None found | – | 70 B | – | no | 2026-11-04 | | CodeSandbox codesandbox.io | None found | – | 44 D | – | no | 2026-11-04 | | Codev co.dev | None found | – | 50 C | – | no | 2026-11-04 | | Codex Reset codex-reset.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Cogram cogram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | CoinMarketCap coinmarketcap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | COLA Cloud colacloud.us | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | CometChat cometchat.com | Verified no auth | – | 56 C | – | not read | 2026-11-04 | | Common Paper commonpaper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | Commsharbor commsharbor.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Composio composio.dev | None found | composio | 83 B | – | no | 2026-11-04 | | Compresr compresr.ai | None found | – | 49 C | yes | no | 2026-11-04 | | Compyle compyle.ai | None found | – | 55 C | – | no | 2026-11-04 | | Concourse CI concourse-ci.org | None found | – | 41 D | – | no | 2026-11-04 | | Conductor conductor.build | None found | – | 72 B | – | no | 2026-11-04 | | Confident AI confident-ai.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 90 A | – | no | 2026-11-04 | | ConfigCat configcat.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 51 C | – | no | 2026-11-04 | | Confluent confluent.io | None found | – | 78 B | – | no | 2026-11-04 | | ConnectMachine connectmachine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Connie connie.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Contentful contentful.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | contentful-cli | 74 B | – | no | 2026-11-04 | | Contentstack contentstack.com | Credential wall API key | – | 67 C | – | no | 2026-11-04 | | Context Awesome context-awesome.com | Verified no auth | – | | – | not read | 2026-11-04 | | Context7 context7.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | | Continue continue.dev | No answer | – | 54 C | – | no | 2026-11-04 | | Conveo conveo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Convex convex.dev | Verified no auth; endpoint found by subdomain guess, verified by connecting | convex | 71 B | – | not read | 2026-11-04 | | Convoy getconvoy.io | None found | – | 59 C | – | no | 2026-11-04 | | CookieYes cookieyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Coralogix coralogix.com | None found | – | 79 B | yes | no | 2026-11-04 | | CORE getcore.me | No answer | – | 55 C | – | no | 2026-11-04 | | CoreMedia coremedia.com | None found | – | 57 C | – | no | 2026-11-04 | | CoreNexis API corenexis.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | CoreWeave coreweave.com | None found | – | 68 C | – | no | 2026-11-04 | | COROS coros.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | | Corsair corsair.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Cortex cortex.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/c/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Letter C, page 2 | Agent MCP Directory" description: "119 companies starting with C: MCP server, CLI and OpenAPI status, checked 4 November 2026. Page 2 of 2. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/c/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Letter C, page 2 | Agent MCP Directory > 119 companies starting with C: MCP server, CLI and OpenAPI status, checked 4 November 2026. Page 2 of 2. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/c/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with C, page 2 119 companies in the directory start with the letter C: 19 listed tools to a client with no credentials, 48 answered with a sign-in challenge (not counted), and 5 have a CLI on record. This page lists rows 101 to 119, from Cosine to Cypress Cloud. ## Rows 101 to 119 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Cosine cosine.sh | None found | – | 37 D | – | no | 2026-11-04 | | Cosmic cosmicjs.com | None found | – | 75 B | yes | no | 2026-11-04 | | Costory costory.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Courier courier.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 57 C | – | no | 2026-11-04 | | Coval coval.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 65 C | – | no | 2026-11-04 | | Cpln cpln.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Craft craft.do | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Craft CMS craftcms.com | None found | – | 44 D | – | no | 2026-11-04 | | Crakseo crakseo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Cronitor cronitor.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | CryptoAPIs IO cryptoapis.io | Verified no auth | – | | – | not read | 2026-11-04 | | CTGT ctgt.ai | None found | – | 46 D | – | no | 2026-11-04 | | cubic cubic.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | Cursor cursor.com | None found | – | 74 B | – | no | 2026-11-04 | | CustomDomain™ customdomain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | CustomGPT.ai customgpt.ai | No answer | – | | – | not read | 2026-11-04 | | Cyberdesk cyberdesk.io | None found | – | 74 B | – | no | 2026-11-04 | | cyon cyon.ch | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Cypress Cloud cypress.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/c/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with D | Agent MCP Directory" description: "55 companies starting with D: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/d site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with D | Agent MCP Directory > 55 companies starting with D: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/d Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with D 55 companies in the directory start with the letter D: 12 listed tools to a client with no credentials, 18 answered with a sign-in challenge (not counted), and 2 have a CLI on record. Rows run from Dabloons to Dynatrace. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Dabloons dabloons.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Daft daft.ai | None found | – | 45 D | – | no | 2026-11-04 | | Dagger dagger.io | None found | – | 48 C | – | no | 2026-11-04 | | Dailybot dailybot.com | None found | – | 76 B | yes | no | 2026-11-04 | | Dappier dappier.com | No answer | – | | – | not read | 2026-11-04 | | dari.dev dari.dev | None found | – | 42 D | – | no | 2026-11-04 | | Dart dartai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | yes | 2026-11-04 | | Datadog datadoghq.com | Sign-in required OAuth DCR; tools not seen, not counted | @datadog/datadog-ci | 69 C | – | no | 2026-11-04 | | Datasaur datasaur.ai | None found | – | 69 C | – | no | 2026-11-04 | | DC Hub dchub.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | Deci deci.ai | None found | – | 44 D | – | no | 2026-11-04 | | Dedalus Labs dedaluslabs.ai | No answer | – | 85 B | – | no | 2026-11-04 | | Deed deed.page | Verified no auth | – | | yes | not read | 2026-11-04 | | Deepnote deepnote.com | None found | – | 65 C | – | no | 2026-11-04 | | DeepSource deepsource.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | DeepWiki deepwiki.com | Verified no auth | – | | – | not read | 2026-11-04 | | Deno deno.com | None found | deno | 65 C | – | no | 2026-11-04 | | Depot depot.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Designbase designbase.com | None found | – | 55 C | – | no | 2026-11-04 | | Designesy designesy.org | Verified no auth | – | | – | not read | 2026-11-04 | | DeskCrew deskcrew.io | None found | – | | yes | not read | 2026-11-04 | | Desktopcommander desktopcommander.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DevCycle devcycle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Devin devin.ai | Verified no auth | – | 67 C | yes | not read | 2026-11-04 | | Devo devo.com | None found | – | 43 D | – | no | 2026-11-04 | | Devtron devtron.ai | Credential wall API key | – | 48 C | – | no | 2026-11-04 | | DevZero devzero.io | None found | – | 58 C | – | no | 2026-11-04 | | Dialer getdialer.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DialMCP dialmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Didit One didit.me | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | – | no | 2026-11-04 | | Digestseo digestseo.com | Verified no auth | – | | – | not read | 2026-11-04 | | DigitalOcean digitalocean.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 74 B | – | no | 2026-11-04 | | Directus directus.io | None found | – | 47 D | – | no | 2026-11-04 | | Dittowords dittowords.com | None found | – | 67 C | – | no | 2026-11-04 | | Divblox divblox.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dm dm.de | Verified no auth | – | 51 C | – | no | 2026-11-04 | | DMCA.com dmca.com | Verified no auth | – | | – | no | 2026-11-04 | | Docker docker.com | No answer | – | 69 C | – | no | 2026-11-04 | | Docket docketqa.com | None found | – | 58 C | – | no | 2026-11-04 | | DocNexus docnexus.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DocSpring docspring.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dodo Payments dodopayments.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | not read | 2026-11-04 | | Dojah dojah.io | None found | – | 77 B | – | no | 2026-11-04 | | Dorik dorik.com | None found | – | 35 D | – | no | 2026-11-04 | | Double double.bot | None found | – | 54 C | – | no | 2026-11-04 | | Draftbit draftbit.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Dragoneye dragoneye.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Draw draw.io | Verified no auth | – | 13 F | – | not read | 2026-11-04 | | DrDroid drdroid.io | None found | – | 61 C | – | no | 2026-11-04 | | Dreamwork dreamworkhq.com | Verified no auth | – | | – | not read | 2026-11-04 | | DropTheHassle dropthehassle.com | Verified no auth | – | | – | not read | 2026-11-04 | | DSers dsers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dueback dueback.co | Verified no auth | – | | – | not read | 2026-11-04 | | Duffel duffel.com | None found | – | 65 C | – | no | 2026-11-04 | | Dynatrace dynatrace.com | None found | – | 82 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/d/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with E | Agent MCP Directory" description: "35 companies starting with E: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/e site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with E | Agent MCP Directory > 35 companies starting with E: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/e Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with E 35 companies in the directory start with the letter E: 10 listed tools to a client with no credentials, 17 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from EAN-Search.org to Extend. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | EAN-Search.org ean-search.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Easy itseasy.co | Verified no auth | – | 87 A | – | no | 2026-11-04 | | EasyGerber easygerber.com | Verified no auth | – | | – | not read | 2026-11-04 | | Easyship easyship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Edgaze edgaze.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Editalmd editalmd.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Egnyte egnyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Elastic elastic.co | None found | – | 59 C | – | no | 2026-11-04 | | Electroneek electroneek.com | None found | – | 68 C | – | no | 2026-11-04 | | Elementary Data elementary-data.com | No answer | – | 56 C | – | no | 2026-11-04 | | ElevenFlo elevenflo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ElevenLabs elevenlabs.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Elfsight AI elfsight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Ellipsis ellipsis.dev | No answer | – | 69 C | – | no | 2026-11-04 | | Embrace embrace.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 38 D | – | no | 2026-11-04 | | emem emem.dev | Verified no auth | – | 85 B | – | not read | 2026-11-04 | | EmpirioLabs AI empiriolabs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Encord encord.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 69 C | – | no | 2026-11-04 | | Env0 env0.com | None found | – | 73 B | – | no | 2026-11-04 | | Eodly eodly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | not read | 2026-11-04 | | Epidemic Sound epidemicsound.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Epinu epinu.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Epsilla epsilla.com | None found | – | 57 C | – | no | 2026-11-04 | | eResource Scheduler eresourcescheduler.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | esimgomobile esimgomobile.com | Verified no auth | – | | – | not read | 2026-11-04 | | Etherscan etherscan.io | Verified no auth | – | | – | no | 2026-11-04 | | Everhour everhour.com | None found | – | 68 C | – | no | 2026-11-04 | | Evermuse evermuse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | EveryCalc everycalc.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | Evidently AI evidentlyai.com | None found | – | 58 C | – | no | 2026-11-04 | | Exa exa.ai | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Example4 example4.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Explorium explorium.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Expo expo.dev | Sign-in required OAuth DCR; tools not seen, not counted | eas-cli | 66 C | – | no | 2026-11-04 | | Extend extend.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/e/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with F | Agent MCP Directory" description: "48 companies starting with F: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/f site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with F | Agent MCP Directory > 48 companies starting with F: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/f Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with F 48 companies in the directory start with the letter F: 13 listed tools to a client with no credentials, 22 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from FairValid to fynk. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | FairValid fairvalid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fastero fastero.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | FastJVM fastjvm.com | None found | – | 43 D | – | no | 2026-11-04 | | Fastly fastly.com | None found | – | 70 B | – | no | 2026-11-04 | | Fastmail fastmail.com | None found | – | 37 D | – | no | 2026-11-04 | | Fastshot fastshot.ai | None found | – | 66 C | – | no | 2026-11-04 | | Fathom fathom.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | Faxette faxette.com | Verified no auth | – | | – | not read | 2026-11-04 | | Faxforagents faxforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | Ferryhopper ferryhopper.com | Verified no auth | – | | – | not read | 2026-11-04 | | Fiber AI fiber.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | | Fiddler AI fiddler.ai | None found | – | 68 C | – | no | 2026-11-04 | | Figma figma.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | FinancialFilings financialfilings.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Find-A-Domain findadomain.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Findabis findabis.com | Verified no auth | – | | – | not read | 2026-11-04 | | Firebase firebase.google.com | None found | firebase-tools | 56 C | – | not read | 2026-11-04 | | Fireflies.ai fireflies.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | FireHydrant firehydrant.com | None found | – | 49 C | – | no | 2026-11-04 | | Firmafakta firmafakta.se | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Firmament getfirmament.com | No answer | – | | – | not read | 2026-11-04 | | Flagsmith flagsmith.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 47 D | – | no | 2026-11-04 | | FlickDirect flickdirect.com | Verified no auth | – | | – | not read | 2026-11-04 | | Flightcontrol flightcontrol.dev | None found | – | 46 D | – | no | 2026-11-04 | | Flightpowers flightpowers.com | Verified no auth | – | | yes | not read | 2026-11-04 | | FlightQueue flightqueue.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | FlightSeatMap flightseatmap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Floot floot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | FlowLeap flowleap.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flowra flowra.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flowtel flowtel.ai | None found | – | 55 C | – | no | 2026-11-04 | | FlutterFlow flutterflow.io | None found | – | 53 C | – | no | 2026-11-04 | | Flux fluxcd.io | None found | – | 38 D | – | no | 2026-11-04 | | Fly fly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | no | 2026-11-04 | | FlyBest flybest.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Follore follore.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Font Awesome fontawesome.com | None found | – | 56 C | – | no | 2026-11-04 | | Footgun getfootgun.com | Verified no auth | – | | – | not read | 2026-11-04 | | Formasty formasty.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | Forter forter.com | Verified no auth | – | 92 A | yes | no | 2026-11-04 | | Frase frase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 89 A | yes | no | 2026-11-04 | | Freestyle freestyle.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | yes | no | 2026-11-04 | | Frihet frihet.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Fuentio fuentio.com | Verified no auth | – | | – | not read | 2026-11-04 | | FullEnrich fullenrich.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | not read | 2026-11-04 | | Fund Momentum fundmomentum.vc | Verified no auth | – | | yes | not read | 2026-11-04 | | FusionAuth fusionauth.io | Verified no auth | – | 71 B | – | no | 2026-11-04 | | fynk fynk.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/f/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with G | Agent MCP Directory" description: "48 companies starting with G: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/g site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with G | Agent MCP Directory > 48 companies starting with G: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/g Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with G 48 companies in the directory start with the letter G: 13 listed tools to a client with no credentials, 18 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from Gaipagents to GuruHotel. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Gaipagents gaipagents.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Galileo AI galileo.ai | None found | – | 78 B | – | no | 2026-11-04 | | GameAnalytics gameanalytics.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | Gamedev gamedev.pl | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Gamma gamma.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | GenMagic genmagic.co | Verified no auth | – | | yes | not read | 2026-11-04 | | Getappniche getappniche.com | Verified no auth | – | | – | not read | 2026-11-04 | | Getdecipher getdecipher.com | None found | – | 45 D | – | no | 2026-11-04 | | GetMattered getmattered.com | Verified no auth | – | | – | not read | 2026-11-04 | | Getmocha getmocha.com | None found | – | 46 D | – | not read | 2026-11-04 | | Ghost ghost.org | None found | – | 70 B | – | no | 2026-11-04 | | GitBook gitbook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 86 A | – | no | 2026-11-04 | | Gitea gitea.com | None found | – | 55 C | – | no | 2026-11-04 | | GitHub github.com | Sign-in required OAuth; tools not seen, not counted | – | 65 C | yes | no | 2026-11-04 | | Githubcopilot githubcopilot.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | GitLab gitlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | GitMCP gitmcp.io | Verified no auth | – | 37 D | – | not read | 2026-11-04 | | GitOps gitops.tech | None found | – | 37 D | – | no | 2026-11-04 | | Gitpod gitpod.io | None found | – | 41 D | – | not read | 2026-11-04 | | GlanceAI glance.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Glassflow glassflow.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Glean glean.com | None found | – | 72 B | – | no | 2026-11-04 | | Glide glide.app | None found | – | 50 C | – | no | 2026-11-04 | | Glideapps glideapps.com | No answer | – | 64 C | – | no | 2026-11-04 | | Glif glif.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | yes | no | 2026-11-04 | | Globalping globalping.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | GoCardless gocardless.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Goldsky goldsky.com | Verified no auth | – | 81 B | – | not read | 2026-11-04 | | Gomdori gomdori.app | Verified no auth | – | | – | not read | 2026-11-04 | | Google google.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | Google Cloud cloud.google.com | None found | – | 51 C | – | no | 2026-11-04 | | Google Cloud googleapis.com | Verified no auth | – | | – | no | 2026-11-04 | | Google Gemini gemini.google.com | None found | @google/gemini-cli | 43 D | – | not read | 2026-11-04 | | GoSQLX gosqlx.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Grafana grafana.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Grafbase grafbase.com | No answer | – | 45 D | – | no | 2026-11-04 | | Granola granola.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Graphcms graphcms.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Graphify graphify.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | Grav getgrav.org | None found | – | 68 C | – | no | 2026-11-04 | | Graylog graylog.org | None found | – | 45 D | – | no | 2026-11-04 | | Greca House grecahouse.com | Verified no auth | – | | – | not read | 2026-11-04 | | Greptile greptile.com | None found | – | 77 B | – | no | 2026-11-04 | | GrowthBook growthbook.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | Gryz gryz.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Gumroad gumroad.com | None found | – | 69 C | – | no | 2026-11-04 | | Guru getguru.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | GuruHotel guruhotel.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/g/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with H | Agent MCP Directory" description: "46 companies starting with H: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/h site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with H | Agent MCP Directory > 46 companies starting with H: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/h Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with H 46 companies in the directory start with the letter H: 10 listed tools to a client with no credentials, 16 answered with a sign-in challenge (not counted), and 3 have a CLI on record. Rows run from Habitica to Hypotize. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Habitica habitica.com | None found | – | 34 D | – | no | 2026-11-04 | | HackerRank hackerrank.com | None found | – | 69 C | – | no | 2026-11-04 | | Hands for Agents handsforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | hardoz hardoz.eu.cc | No answer | – | | – | not read | 2026-11-04 | | Harness harness.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 75 B | – | no | 2026-11-04 | | HARVEST.com harvest.com | None found | – | 39 D | – | no | 2026-11-04 | | HasData hasdata.com | Verified no auth | – | | – | not read | 2026-11-04 | | HashiCorp hashicorp.com | None found | – | 60 C | – | no | 2026-11-04 | | Hasura hasura.io | None found | – | 51 C | – | no | 2026-11-04 | | Hatchet hatchet.run | None found | – | 53 C | – | no | 2026-11-04 | | Haystackeditor haystackeditor.com | None found | – | 44 D | – | no | 2026-11-04 | | Hcti hcti.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Healthline healthline.com | None found | – | 75 B | – | no | 2026-11-04 | | Helena helena.bio | Verified no auth | – | | – | not read | 2026-11-04 | | HelixDB helix-db.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 82 B | yes | no | 2026-11-04 | | HemmaBo hemmabo.com | Verified no auth | – | | – | not read | 2026-11-04 | | Hermoso hermoso.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Heroku heroku.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | heroku | 73 B | – | no | 2026-11-04 | | HeroUI heroui.com | None found | – | 81 B | yes | no | 2026-11-04 | | HetrixTools hetrixtools.com | None found | – | 59 C | – | no | 2026-11-04 | | Hetzner hetzner.com | None found | – | 50 C | – | no | 2026-11-04 | | Hexclave hexclave.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 85 B | yes | no | 2026-11-04 | | Hiro hiro.so | None found | – | 49 C | – | no | 2026-11-04 | | Hitsteps hitsteps.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Hive hive.com | None found | – | 66 C | – | no | 2026-11-04 | | Hive Intelligence hiveintelligence.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | Honeybadger honeybadger.io | None found | – | 72 B | – | not read | 2026-11-04 | | Honeycomb honeycomb.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | Hookpulse hookpulse.net | Verified no auth | – | | yes | not read | 2026-11-04 | | Hookstep hookstep.in | Credential wall API key | – | | – | not read | 2026-11-04 | | hoop.dev hoop.dev | None found | – | 41 D | – | no | 2026-11-04 | | Hostinger hostinger.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | yes | 2026-11-04 | | hotglue hotglue.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | HubSpot hubspot.com | Sign-in required OAuth; tools not seen, not counted | @hubspot/cli | 72 B | – | no | 2026-11-04 | | Hubstaff hubstaff.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Huddo huddo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Hugging Face huggingface.co | Verified no auth | huggingface_hub | 82 B | – | no | 2026-11-04 | | HVTracker hvtracker.net | Verified no auth | – | | – | not read | 2026-11-04 | | Hydrant hydrant.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Hygraph hygraph.com | None found | – | 69 C | – | no | 2026-11-04 | | HypAware hypaware.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | HYPD AI hypd.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | Hyperbeam hyperbeam.com | None found | – | 57 C | – | no | 2026-11-04 | | Hyperresearch hyperresearch.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | not read | 2026-11-04 | | Hyperspell hyperspell.com | None found | – | 75 B | – | no | 2026-11-04 | | Hypotize hypotize.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/h/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with I | Agent MCP Directory" description: "34 companies starting with I: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/i site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with I | Agent MCP Directory > 34 companies starting with I: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/i Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with I 34 companies in the directory start with the letter I: 8 listed tools to a client with no credentials, 13 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from Icons8 to ix. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Icons8 icons8.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | iDevice idevice.com | Verified no auth | – | | – | not read | 2026-11-04 | | IFTTT ifttt.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | iHatePosting ihateposting.com | Verified no auth | – | | – | not read | 2026-11-04 | | ImageKit imagekit.io | Verified no auth | – | 63 C | – | not read | 2026-11-04 | | Imgix imgix.com | None found | – | 67 C | – | no | 2026-11-04 | | imzala.net imzala.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Inamprotocol inamprotocol.org | Verified no auth | – | | – | not read | 2026-11-04 | | incident.io incident.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 64 C | – | no | 2026-11-04 | | IncidentFox incidentfox.ai | None found | – | 67 C | – | no | 2026-11-04 | | Inconvo inconvo.com | None found | – | 60 C | – | no | 2026-11-04 | | Indeed indeed.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 25 F | – | no | 2026-11-04 | | IndustryLens industry-lens.com | Verified no auth | – | | – | not read | 2026-11-04 | | Infer infer.so | None found | – | 37 D | – | no | 2026-11-04 | | Infield infield.ai | None found | – | 48 C | – | no | 2026-11-04 | | Infobip infobip.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Infra infra.new | None found | – | 60 C | – | no | 2026-11-04 | | Infracost infracost.io | No answer | – | 50 C | – | no | 2026-11-04 | | Inkeep inkeep.com | No answer | – | 71 B | – | no | 2026-11-04 | | InsForge insforge.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | – | no | 2026-11-04 | | Instant instantdb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Integuru integuru.ai | None found | – | 47 D | – | no | 2026-11-04 | | Intercom intercom.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | Interfaze interfaze.ai | None found | – | 66 C | yes | no | 2026-11-04 | | Interfere interfere.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Inttegro inttegro.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Intuned intunedhq.com | None found | – | 63 C | – | no | 2026-11-04 | | Invideo invideo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 54 C | – | not read | 2026-11-04 | | Invokary invokary.com | Verified no auth | – | | – | not read | 2026-11-04 | | IOMETE iomete.com | None found | – | 60 C | – | no | 2026-11-04 | | ISMS Copilot ismscopilot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | yes | not read | 2026-11-04 | | Isonavigator isonavigator.io | Verified no auth | – | | – | not read | 2026-11-04 | | Isto Intents istointents.com | Verified no auth | – | | – | not read | 2026-11-04 | | ix ix.dev | None found | – | 39 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/i/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with J | Agent MCP Directory" description: "12 companies starting with J: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/j site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with J | Agent MCP Directory > 12 companies starting with J: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/j Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with J 12 companies in the directory start with the letter J: 3 listed tools to a client with no credentials, 6 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from Jam.dev to JustClaw-It. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Jam.dev jam.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | JANCTION janction.jp | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Javadocs.dev javadocs.dev | Verified no auth | – | 47 D | yes | not read | 2026-11-04 | | Jet Admin jetadmin.io | None found | – | 65 C | – | no | 2026-11-04 | | JetBrains jetbrains.com | None found | – | 62 C | – | no | 2026-11-04 | | JFrog jfrog.com | None found | – | 70 B | – | no | 2026-11-04 | | Jitsu jitsu.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | no | 2026-11-04 | | JobsPipe jobspipe.dev | Verified no auth | – | 96 A+ | yes | not read | 2026-11-04 | | Jotform jotform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | JumpCloud jumpcloud.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | JustCall justcall.host | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | JustClaw-It justclaw.it.com | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/j/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with K | Agent MCP Directory" description: "30 companies starting with K: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/k site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with K | Agent MCP Directory > 30 companies starting with K: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/k Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with K 30 companies in the directory start with the letter K: 6 listed tools to a client with no credentials, 8 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from K9s to Kujolang.ai. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | K9s k9scli.io | None found | – | 42 D | – | no | 2026-11-04 | | Kaiv kaiv.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Kajabi kajabi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | no | 2026-11-04 | | Kanbanize kanbanize.com | None found | – | 43 D | – | no | 2026-11-04 | | Karate Labs karatelabs.io | None found | – | 63 C | – | no | 2026-11-04 | | kari kari.com | Verified no auth | – | | – | not read | 2026-11-04 | | Kashikoi getkashikoi.com | None found | – | 39 D | – | no | 2026-11-04 | | Keenable keenable.ai | Verified no auth | – | 68 C | yes | not read | 2026-11-04 | | Keep(卡路里科技)-自律给我自由 google.keep.com | None found | – | 52 C | – | no | 2026-11-04 | | Keet trykeet.com | None found | – | 53 C | – | no | 2026-11-04 | | Kema kema-studio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | KERNEL kernel.sh | None found | – | 86 A | – | no | 2026-11-04 | | Keyframe Labs keyframelabs.com | None found | – | 65 C | – | no | 2026-11-04 | | KeystoneJS keystonejs.com | None found | – | 55 C | – | no | 2026-11-04 | | Kili Technology kili-technology.com | None found | – | 59 C | – | no | 2026-11-04 | | Kiln kiln3d.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kin kinlab.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kinsta® kinsta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Kissflow kissflow.com | None found | – | 58 C | – | no | 2026-11-04 | | Kitemaker kitemaker.co | None found | – | 34 D | – | no | 2026-11-04 | | Klavis klavis.ai | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Kodza kodza.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Kollektiv thekollektiv.ai | No answer | – | | – | not read | 2026-11-04 | | Komodor komodor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Kong konghq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Koyeb koyeb.com | None found | – | 61 C | – | no | 2026-11-04 | | Kragos kragos.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kraken kraken.com | Verified no auth | – | 82 B | yes | no | 2026-11-04 | | Kubecost kubecost.com | None found | – | 43 D | – | no | 2026-11-04 | | Kujolang.ai kujolang.ai | Verified no auth | – | 55 C | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/k/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with L | Agent MCP Directory" description: "52 companies starting with L: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/l site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with L | Agent MCP Directory > 52 companies starting with L: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/l Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with L 52 companies in the directory start with the letter L: 7 listed tools to a client with no credentials, 23 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from Lambda to Luw.ai. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Lambda lambdalabs.com | None found | – | 44 D | – | no | 2026-11-04 | | Lambdatest lambdatest.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Laminar laminar.sh | None found | – | 41 D | – | no | 2026-11-04 | | Lanesurf lanesurf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | yes | no | 2026-11-04 | | Lark getlark.ai | None found | – | 56 C | – | no | 2026-11-04 | | Last9 last9.io | None found | – | 73 B | – | no | 2026-11-04 | | LaunchDarkly launchdarkly.com | No answer | – | 69 C | – | no | 2026-11-04 | | Layrcake layrcake.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lazaretto lazaretto.dev | Verified no auth | – | | yes | not read | 2026-11-04 | | Lazybird lazybird.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Leadbase leadbase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Leadpages leadpages.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | yes | no | 2026-11-04 | | Leantime leantime.io | None found | – | 52 C | – | no | 2026-11-04 | | Leash lea.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lemma uselemma.ai | None found | – | 66 C | – | no | 2026-11-04 | | Letterly letterly.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lezzoo lezzoo.com | Verified no auth | – | 69 C | – | no | 2026-11-04 | | LFG lfg.gm | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lightsprint lightsprint.ai | None found | – | 62 C | – | no | 2026-11-04 | | Lightstep lightstep.com | None found | – | 42 D | – | no | 2026-11-04 | | Lilac getlilac.com | None found | – | 67 C | – | no | 2026-11-04 | | Limrun limrun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | Linear linear.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Lingo.dev lingo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | Linode linode.com | None found | – | 53 C | – | no | 2026-11-04 | | Liquilens liquilens.in | Verified no auth | – | 72 B | – | not read | 2026-11-04 | | Listenetic listenetic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LiteLLM litellm.ai | None found | – | 73 B | – | no | 2026-11-04 | | LiveCRM livecrm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LiveScore MCP livescoremcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | LLM Pulse llmpulse.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | | Llmdata llmdata.com | None found | – | 35 D | – | no | 2026-11-04 | | Llmtxt llmtxt.dev | No answer | – | | – | not read | 2026-11-04 | | Local MCP local-mcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Localcmd localcmd.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Locus paywithlocus.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | yes | no | 2026-11-04 | | Lodestarindex lodestarindex.com | Verified no auth | – | | – | not read | 2026-11-04 | | Loft loft.sh | None found | – | 53 C | – | no | 2026-11-04 | | Loggly loggly.com | None found | – | 52 C | – | no | 2026-11-04 | | LogicMonitor logicmonitor.com | None found | – | 46 D | – | no | 2026-11-04 | | LogRocket logrocket.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Logseq logseq.com | None found | – | 38 D | – | no | 2026-11-04 | | Logz.io logz.io | None found | – | 58 C | – | no | 2026-11-04 | | Longbridge longbridge.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | not read | 2026-11-04 | | Lotas AI lotas.ai | None found | – | 51 C | – | no | 2026-11-04 | | Lucid lucid.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Luciq luciq.ai | None found | – | 77 B | – | no | 2026-11-04 | | Ludo AI ludo.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Luel luel.ai | None found | – | 58 C | – | no | 2026-11-04 | | Lumman lumman.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lusha lusha.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Luw.ai luw.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/l/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with M | Agent MCP Directory" description: "78 companies starting with M: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/m site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with M | Agent MCP Directory > 78 companies starting with M: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/m Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with M 78 companies in the directory start with the letter M: 16 listed tools to a client with no credentials, 28 answered with a sign-in challenge (not counted), and 3 have a CLI on record. Rows run from Maatsii to mypromind. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Maatsii maatsii.com | Verified no auth | – | | – | not read | 2026-11-04 | | mabl mabl.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Macfax macfax.com | Verified no auth | – | | – | not read | 2026-11-04 | | Magic Hour magichour.ai | Verified no auth | – | 89 A | yes | no | 2026-11-04 | | MagicBell magicbell.com | None found | – | 47 D | – | no | 2026-11-04 | | Magnitude magnitude.dev | None found | – | 74 B | – | no | 2026-11-04 | | Mailbuttons mailbuttons.com | Verified no auth | – | | – | not read | 2026-11-04 | | Mailkite mailkite.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Mailrith mailrith.com | Verified no auth | – | 97 A+ | yes | not read | 2026-11-04 | | Maitai trymaitai.com | None found | – | 60 C | – | no | 2026-11-04 | | Make make.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Malware Patrol malwarepatrol.net | No answer | – | | – | not read | 2026-11-04 | | ManageEngine manageengine.com | No answer | – | 62 C | – | no | 2026-11-04 | | Manicule manicule.dev | None found | – | 33 D | – | no | 2026-11-04 | | Manifold manifold.markets | Verified no auth | – | | – | not read | 2026-11-04 | | Manufact manufact.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | yes | no | 2026-11-04 | | Mapbox mapbox.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | MAQAMI maqami.co | Verified no auth | – | | – | not read | 2026-11-04 | | Market Eyes Live marketeyeslive.com | Verified no auth | – | | – | not read | 2026-11-04 | | Massdriver massdriver.cloud | None found | – | 63 C | – | no | 2026-11-04 | | Mastra mastra.ai | None found | – | 78 B | – | no | 2026-11-04 | | Maven trymaven.com | None found | – | 61 C | – | no | 2026-11-04 | | MCP Telegram mcp-telegram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | MCPEmails mcpemails.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | mcprush.com mcprush.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Measuremy measuremy.site | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mediawork mediawork.io | Verified no auth | – | | – | not read | 2026-11-04 | | MedicalNewsToday medicalnewstoday.com | None found | – | 75 B | – | no | 2026-11-04 | | Medplum medplum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 43 D | – | no | 2026-11-04 | | Medusa medusajs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Mellow Hub mellow.world | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mem mem.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Memocore memocore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Memxus memxus.com | Verified no auth | – | | – | not read | 2026-11-04 | | Mendix mendix.com | None found | – | 72 B | – | no | 2026-11-04 | | Mercado Libre mercadolibre.com | No answer | – | 40 D | – | no | 2026-11-04 | | Mercado Pago mercadopago.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Mergent mergent.co | None found | – | 59 C | – | no | 2026-11-04 | | Mergify mergify.com | None found | – | 75 B | yes | no | 2026-11-04 | | Metoro metoro.io | None found | – | 43 D | – | no | 2026-11-04 | | Mezmo mezmo.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | Microsoft microsoft.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Microsoft 365 cloud.microsoft | Sign-in required OAuth; tools not seen, not counted | – | | – | no | 2026-11-04 | | Microsoft Azure azure.microsoft.com | None found | – | 51 C | – | no | 2026-11-04 | | Microsoft Learn learn.microsoft.com | Verified no auth | azure-cli | 24 F | – | not read | 2026-11-04 | | Middleware middleware.io | None found | – | 52 C | – | no | 2026-11-04 | | Minded minded.com | None found | – | 58 C | – | no | 2026-11-04 | | Mindee mindee.com | None found | – | 73 B | – | no | 2026-11-04 | | Minds getminds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Mindsdb mindsdb.com | None found | – | 51 C | – | not read | 2026-11-04 | | Minicor minicor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | MiningBridge miningbridge.in | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mintlify mintlify.com | Verified no auth | mint | 74 B | – | no | 2026-11-04 | | Mirabelloconsultancy mirabelloconsultancy.com | Verified no auth | – | | – | not read | 2026-11-04 | | Miro miro.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Mito trymito.io | None found | – | 49 C | – | no | 2026-11-04 | | mlop mlop.ai | None found | – | 38 D | – | no | 2026-11-04 | | Mnemoverse mnemoverse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | MnogoReels mnogo-reels.ru | Verified no auth | – | | – | not read | 2026-11-04 | | Mobbin mobbin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | not read | 2026-11-04 | | MobileBoost mobileboost.io | None found | – | 66 C | – | no | 2026-11-04 | | Moda moda.dev | None found | – | 85 B | – | no | 2026-11-04 | | Modal modal.com | None found | modal | 63 C | – | no | 2026-11-04 | | Modelence modelence.com | None found | – | 60 C | – | no | 2026-11-04 | | Momentic momentic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | monday monday.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | yes | 2026-11-04 | | MongoDB mongodb.com | None found | – | 78 B | – | no | 2026-11-04 | | Moogsoft moogsoft.com | None found | – | 41 D | – | no | 2026-11-04 | | MorningStar morningstar.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Morph morphllm.com | No answer | – | 82 B | – | no | 2026-11-04 | | Morphik morphik.ai | No answer | – | 70 B | – | no | 2026-11-04 | | Moss moss.dev | None found | – | 81 B | – | no | 2026-11-04 | | MotionSpec motionspec.dev | Verified no auth | – | | – | not read | 2026-11-04 | | MovingLake movinglake.com | None found | – | 39 D | – | no | 2026-11-04 | | MuleSoft mulesoft.com | None found | – | 36 D | – | no | 2026-11-04 | | Mural mural.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Mux mux.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | mypromind mypromind.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/m/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with N | Agent MCP Directory" description: "36 companies starting with N: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/n site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with N | Agent MCP Directory > 36 companies starting with N: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/n Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with N 36 companies in the directory start with the letter N: 7 listed tools to a client with no credentials, 14 answered with a sign-in challenge (not counted), and 3 have a CLI on record. Rows run from Naive to Nyckel. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Naive usenaive.ai | None found | – | 48 C | – | no | 2026-11-04 | | Nameshift nameshift.com | No answer | – | | – | no | 2026-11-04 | | Nanonets nanonets.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Nebius nebius.com | None found | – | 73 B | – | no | 2026-11-04 | | Needle needle-ai.com | No answer | – | | – | not read | 2026-11-04 | | NegativeEV negativeev.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Neon neon.com | Sign-in required OAuth DCR; tools not seen, not counted | neonctl | 88 A | yes | no | 2026-11-04 | | Neon neon.tech | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | Netdata netdata.cloud | Credential wall API key | – | | – | not read | 2026-11-04 | | Netlify netlify.com | Sign-in required OAuth DCR; tools not seen, not counted | netlify-cli | 92 A | yes | no | 2026-11-04 | | Neuronto neuronto.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Nevercode nevercode.io | None found | – | 47 D | – | no | 2026-11-04 | | New Relic newrelic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | NewsCatcher newscatcherapi.com | Verified no auth | – | 63 C | – | no | 2026-11-04 | | Nginx nginx.com | None found | – | 47 D | – | no | 2026-11-04 | | ngrok ngrok.com | Sign-in required OAuth DCR; tools not seen, not counted | ngrok | 90 A | yes | no | 2026-11-04 | | Nimble nimble.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Nitrosend nitrosend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | | Noloco noloco.io | None found | – | 55 C | – | no | 2026-11-04 | | Nomas nomas.fyi | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Noonlaunch noonlaunch.com | Verified no auth | – | 61 C | yes | not read | 2026-11-04 | | Northflank northflank.com | Credential wall API key | – | 53 C | – | no | 2026-11-04 | | Notaiochianese notaiochianese.it | Verified no auth | – | | – | not read | 2026-11-04 | | Notion notion.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | – | no | 2026-11-04 | | Notion notion.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Notion HQ notionhq.com | None found | – | 56 C | – | no | 2026-11-04 | | Notte notte.cc | None found | – | 89 A | – | no | 2026-11-04 | | Novadata novadata.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Noveum noveum.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | not read | 2026-11-04 | | Nslookup nslookup.io | Verified no auth | – | | – | not read | 2026-11-04 | | Nuanced nuanced.dev | None found | – | 49 C | – | no | 2026-11-04 | | Nullstone nullstone.io | None found | – | 42 D | – | no | 2026-11-04 | | NUM itsnum.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Nuxt nuxt.com | No answer | – | 79 B | yes | no | 2026-11-04 | | NVIDIA nvidia.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Nyckel nyckel.com | None found | – | 64 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/n/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with O | Agent MCP Directory" description: "48 companies starting with O: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/o site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with O | Agent MCP Directory > 48 companies starting with O: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/o Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with O 48 companies in the directory start with the letter O: 8 listed tools to a client with no credentials, 19 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from Oakallow to Oximy. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Oakallow oakallow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Obolusfinanz obolusfinanz.de | Verified no auth | – | | – | not read | 2026-11-04 | | Octagon octagonai.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Octoml octoml.ai | None found | – | 38 D | – | no | 2026-11-04 | | OctoPerf octoperf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | Ocular useocular.com | None found | – | 59 C | – | no | 2026-11-04 | | Odigos odigos.io | None found | – | 69 C | – | no | 2026-11-04 | | Offline Protocol offlineprotocol.com | Verified no auth | – | | – | not read | 2026-11-04 | | Oids tryoids.com | Credential wall API key | – | | – | not read | 2026-11-04 | | Okfindex okfindex.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Okibi okibi.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | | Okteto okteto.com | None found | – | 58 C | – | no | 2026-11-04 | | Ollama ollama.com | None found | – | 65 C | – | no | 2026-11-04 | | Omnara omnara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | Omnidim omnidim.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | yes | not read | 2026-11-04 | | Omnistrate omnistrate.com | None found | – | 56 C | – | no | 2026-11-04 | | OneContext onecontext.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Onenote onenote.com | None found | – | 43 D | – | no | 2026-11-04 | | ONES ones.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | OneSchema oneschema.co | Credential wall API key | – | 56 C | – | no | 2026-11-04 | | Onlook onlook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | OpenAccountants openaccountants.com | Verified no auth | – | 64 C | – | not read | 2026-11-04 | | OpenAI openai.com | None found | @openai/codex | 58 C | yes | no | 2026-11-04 | | Openfoundry openfoundry.ai | None found | – | 37 D | – | no | 2026-11-04 | | Openlayer openlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | OpenMesh openmesh.dev | No answer | – | | – | not read | 2026-11-04 | | OpenReplay openreplay.com | None found | – | 66 C | – | no | 2026-11-04 | | Opentext opentext.com | None found | – | 30 D | – | no | 2026-11-04 | | OpenWork openworklabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | OpenZeppelin openzeppelin.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Opsgenie opsgenie.com | None found | – | 60 C | – | no | 2026-11-04 | | Opslane opslane.com | None found | – | 47 D | – | no | 2026-11-04 | | OpsLevel opslevel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | Opsramp opsramp.com | None found | – | 43 D | – | not read | 2026-11-04 | | Optionsahoy optionsahoy.com | Verified no auth | – | | yes | not read | 2026-11-04 | | OpusClip opus.pro | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | Ora ora.ai | Verified no auth | – | 95 A+ | yes | yes | 2026-11-04 | | Orangescrum orangescrum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | OrgGen AI orggen.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Orthogonal orthogonal.com | None found | – | 66 C | – | no | 2026-11-04 | | Osmosis osmosis.ai | None found | – | 69 C | – | no | 2026-11-04 | | Otter.ai otter.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Outlit outlit.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | no | 2026-11-04 | | Outset outset.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | OutSystems outsystems.com | None found | – | 63 C | – | no | 2026-11-04 | | OVHcloud ovhcloud.com | None found | – | 58 C | – | no | 2026-11-04 | | OwlCAD owlcad.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Oximy oximy.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/o/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with P | Agent MCP Directory" description: "87 companies starting with P: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/p site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with P | Agent MCP Directory > 87 companies starting with P: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/p Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with P 87 companies in the directory start with the letter P: 20 listed tools to a client with no credentials, 40 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from Paddle to Pylon. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Paddle paddle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Padlet padlet.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Pageaudit pageaudit.online | Verified no auth | – | | yes | not read | 2026-11-04 | | PageProofer pageproofer.com | Credential wall API key | – | | – | not read | 2026-11-04 | | PagerDuty pagerduty.com | None found | – | 71 B | – | no | 2026-11-04 | | Pageree pageree.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PagerTree pagertree.com | None found | – | 48 C | – | no | 2026-11-04 | | PaidSync.ai paidsync.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | PakBus pakbus.app | Verified no auth | – | | – | not read | 2026-11-04 | | Palenca palenca.com | None found | – | 42 D | – | not read | 2026-11-04 | | Palisade palisade.email | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Pally pally.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | PandaDoc pandadoc.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Pangolin pangolin.net | None found | – | 66 C | – | no | 2026-11-04 | | Pantheon pantheon.io | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Parad1gm parad1gm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ParadeDB paradedb.com | None found | – | 76 B | – | no | 2026-11-04 | | Paragon useparagon.com | None found | – | 70 B | – | no | 2026-11-04 | | Parallel parallel.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Parea parea.ai | None found | – | 49 C | – | no | 2026-11-04 | | Parse parse.bot | None found | – | 65 C | – | no | 2026-11-04 | | Parse.ly parsely.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | PatchDesign.AI patchdesign.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Pathrule pathrule.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PAVE pavecfi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Payload payloadcms.com | None found | – | 61 C | – | no | 2026-11-04 | | PayPal paypal.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Paytm paytm.com | Verified no auth | – | 52 C | – | no | 2026-11-04 | | Peek.com peek.com | Verified no auth | – | 39 D | – | not read | 2026-11-04 | | PensionHunter pensionhunter.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Perspective AI getperspective.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | not read | 2026-11-04 | | Pexafy pexafy.com | Verified no auth | – | | – | not read | 2026-11-04 | | PgDog pgdog.dev | None found | – | 51 C | – | no | 2026-11-04 | | Picsart picsart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | PicSee picsee.io | Verified no auth | – | | – | not read | 2026-11-04 | | Pingram pingram.io | None found | – | 88 A | – | not read | 2026-11-04 | | Pipeboard pipeboard.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | Pipefy pipefy.com | None found | – | 70 B | – | no | 2026-11-04 | | Pipekit pipekit.io | None found | – | 58 C | – | no | 2026-11-04 | | Pith pith.day | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Pixelesq pixelesq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | not read | 2026-11-04 | | PixelFlow pixelflow.so | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Plaid plaid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Plane plane.so | No answer | – | 78 B | yes | no | 2026-11-04 | | PlanetScale planetscale.com | None found | – | 79 B | – | no | 2026-11-04 | | Platform.sh platform.sh | None found | – | 56 C | – | no | 2026-11-04 | | Ploomber ploomber.io | None found | – | 34 D | – | not read | 2026-11-04 | | Plori plori.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | not read | 2026-11-04 | | POEditor poeditor.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Polar Signals polarsignals.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Poly poly.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Pontofato pontofato.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Porkbun porkbun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | – | no | 2026-11-04 | | Port IO port.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | Portainer portainer.io | None found | – | 70 B | – | no | 2026-11-04 | | Porter porter.run | None found | – | 73 B | – | no | 2026-11-04 | | PostData postdata.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | Postel postel.app | Verified no auth | – | | – | not read | 2026-11-04 | | Posteverywhere posteverywhere.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | – | not read | 2026-11-04 | | PostHog posthog.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Postman postman.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Posy posy.page | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Powmcp powmcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Praxim praxim.ai | None found | – | 39 D | – | no | 2026-11-04 | | Precip precip.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | Predictionmarketspicks predictionmarketspicks.com | Verified no auth | – | | – | not read | 2026-11-04 | | PredictLeads predictleads.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | Prembly prembly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | PreShiftIQ preshiftiq.com | Verified no auth | – | | – | not read | 2026-11-04 | | Primitive primitive.dev | Verified no auth | – | 96 A+ | yes | yes | 2026-11-04 | | PrintFriendly printfriendly.com | Credential wall API key | – | | yes | not read | 2026-11-04 | | Prisma prisma.io | Sign-in required OAuth DCR; tools not seen, not counted | prisma | 82 B | yes | no | 2026-11-04 | | Probativegrowth probativegrowth.com | Verified no auth | – | | – | not read | 2026-11-04 | | Process Street process.st | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | Processmaker processmaker.com | None found | – | 45 D | – | no | 2026-11-04 | | Projectx projectx.cloud | None found | – | 36 D | – | no | 2026-11-04 | | ProLevelMax prolevelmax.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Prominara prominara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | Prompeteer prompeteer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Promptless promptless.ai | None found | – | 60 C | – | no | 2026-11-04 | | PropelAuth propelauth.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Ptpge ptpge.org | Verified no auth | – | | – | not read | 2026-11-04 | | Publora publora.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Pulse thepulse.markets | Verified no auth | – | | – | not read | 2026-11-04 | | Pulumi pulumi.com | None found | – | 80 B | – | no | 2026-11-04 | | Pushary pushary.com | Verified no auth | – | 79 B | – | not read | 2026-11-04 | | Pylon pylonump.com | None found | – | 56 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/p/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with Q | Agent MCP Directory" description: "8 companies starting with Q: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/q site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with Q | Agent MCP Directory > 8 companies starting with Q: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/q Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with Q 8 companies in the directory start with the letter Q: 0 listed tools to a client with no credentials, 5 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from Qualityclouds to Quorum AI. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Qualityclouds qualityclouds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Qualityclouds qualityclouds.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Quantstruct quantstruct.com | None found | – | 53 C | – | no | 2026-11-04 | | Queryvary queryvary.com | None found | – | 34 D | – | not read | 2026-11-04 | | Quicknode quicknode.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Quill quill.co | None found | – | 39 D | – | no | 2026-11-04 | | Quillm quillm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Quorum AI quorum.dog | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/q/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with R | Agent MCP Directory" description: "67 companies starting with R: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/r site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with R | Agent MCP Directory > 67 companies starting with R: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/r Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with R 67 companies in the directory start with the letter R: 13 listed tools to a client with no credentials, 21 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from Radar Cnpj to Ryvn. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Radar Cnpj radar-cnpj.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Railway railway.com | Sign-in required OAuth DCR; tools not seen, not counted | @railway/cli | 89 A | yes | not read | 2026-11-04 | | Rainforest QA rainforestqa.com | None found | – | 70 B | – | no | 2026-11-04 | | Ramp ramp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Rampify rampify.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rancher rancher.com | None found | – | 40 D | – | no | 2026-11-04 | | Random Labs randomlabs.ai | None found | – | 45 D | – | no | 2026-11-04 | | Rankability rankability.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | Rapid7 rapid7.com | None found | – | 62 C | – | no | 2026-11-04 | | Rapier rapier.website | Verified no auth | – | | – | not read | 2026-11-04 | | Raygun raygun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Read AI read.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | Readdle readdle.com | None found | – | 45 D | – | no | 2026-11-04 | | ReadMe readme.com | None found | – | 64 C | – | no | 2026-11-04 | | Realeyes realeyes.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Recall.ai recall.ai | None found | – | 73 B | – | no | 2026-11-04 | | Redis redis.io | No answer | – | 62 C | – | no | 2026-11-04 | | Redpanda redpanda.com | Verified no auth | – | 68 C | – | no | 2026-11-04 | | Refine refine.dev | None found | – | 46 D | – | no | 2026-11-04 | | Reflect reflect.app | None found | – | 46 D | yes | no | 2026-11-04 | | Reflex reflex.dev | None found | – | 67 C | – | no | 2026-11-04 | | RegAI regai.tw | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RegEvidenceHub regevidencehub.com | Verified no auth | – | | – | not read | 2026-11-04 | | Reka reka.ai | Verified no auth | – | 77 B | – | no | 2026-11-04 | | Release release.com | None found | – | 52 C | – | no | 2026-11-04 | | Relvato relvato.com | Verified no auth | – | | – | not read | 2026-11-04 | | Relvy relvy.ai | None found | – | 42 D | – | no | 2026-11-04 | | Remote MCP remote-mcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Render render.com | Sign-in required OAuth; tools not seen, not counted | – | 82 B | yes | yes | 2026-11-04 | | Replicas replicas.dev | None found | – | 78 B | – | no | 2026-11-04 | | Replit replit.com | No answer | – | 73 B | – | no | 2026-11-04 | | Replo replo.app | None found | – | 64 C | – | no | 2026-11-04 | | ReplyOnTheFly replyonthefly.com | Verified no auth | – | | – | not read | 2026-11-04 | | ReputeMap reputemap.com | Verified no auth | – | | – | not read | 2026-11-04 | | Rescuetime rescuetime.com | None found | – | 56 C | – | no | 2026-11-04 | | Resemble AI resemble.ai | Verified no auth | – | 74 B | – | not read | 2026-11-04 | | Respan respan.ai | None found | – | 72 B | – | no | 2026-11-04 | | RestaurantDoctorAI restaurantdoctorai.com | Verified no auth | – | | yes | not read | 2026-11-04 | | ResumeQuick resumequick.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Retool retool.com | None found | – | 78 B | – | no | 2026-11-04 | | Rev rev.com | None found | – | 48 C | – | no | 2026-11-04 | | Revyl revyl.ai | None found | – | 48 C | – | no | 2026-11-04 | | Rivet rivet.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Robocorp robocorp.com | None found | – | 41 D | – | no | 2026-11-04 | | Roboflow roboflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | RoboSystems robosystems.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RocketReach rocketreach.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | Rocketship deployrocketship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rokha rokha.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Rollbar rollbar.com | None found | – | 69 C | – | no | 2026-11-04 | | Rootly rootly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Rownd rownd.ai | None found | – | 34 D | – | no | 2026-11-04 | | Rta rta.lat | Verified no auth | – | | – | not read | 2026-11-04 | | Rulebase rulebase.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Rulebricks rulebricks.com | None found | – | 59 C | – | no | 2026-11-04 | | Run run.ai | None found | – | 37 D | – | not read | 2026-11-04 | | RunAnywhere runanywhere.ai | None found | – | 72 B | – | no | 2026-11-04 | | Runautomat runautomat.com | No answer | – | 65 C | – | no | 2026-11-04 | | Runcaptain runcaptain.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 57 C | – | no | 2026-11-04 | | Runcascade runcascade.com | None found | – | 45 D | – | no | 2026-11-04 | | Runcomfy runcomfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RunLocal runlocal.ai | None found | – | 44 D | – | no | 2026-11-04 | | Runpulse runpulse.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Runtm runtm.com | None found | – | 66 C | – | no | 2026-11-04 | | Runtrellis runtrellis.com | None found | – | 40 D | – | no | 2026-11-04 | | Rus.sh rus.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ryvn ryvn.ai | None found | – | 60 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/r/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with S | Agent MCP Directory" description: "170 companies starting with S: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/s site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with S | Agent MCP Directory > 170 companies starting with S: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/s Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with S 170 companies in the directory start with the letter S: 27 listed tools to a client with no credentials, 70 answered with a sign-in challenge (not counted), and 6 have a CLI on record. This page lists rows 1 to 100, from S2 to Soracom. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | S2 s2.dev | None found | – | 61 C | – | no | 2026-11-04 | | Sadiqoon sadiqoon.uk | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Saifs saifs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Salesforce salesforce.com | None found | @salesforce/cli | 51 C | – | no | 2026-11-04 | | Salvy salvy.com.br | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | SanctionsKit sanctionskit.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Sanity sanity.io | Sign-in required OAuth DCR; tools not seen, not counted | @sanity/cli | 72 B | – | no | 2026-11-04 | | SAP sap.com | None found | – | 52 C | – | not read | 2026-11-04 | | Say It Again sayitagain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sazabi sazabi.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Scaleway scaleway.com | None found | – | 69 C | – | no | 2026-11-04 | | Scalix Cloud scalix.world | Verified no auth | – | | – | not read | 2026-11-04 | | Scalr scalr.com | None found | – | 56 C | – | no | 2026-11-04 | | Scalyr scalyr.com | None found | – | 40 D | – | no | 2026-11-04 | | Scape scape.app | None found | – | 36 D | – | no | 2026-11-04 | | Scavio scavio.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scento scento.com | Verified no auth | – | 82 B | – | not read | 2026-11-04 | | Scholar Sidekick scholar-sidekick.com | Verified no auth | – | 98 A+ | yes | not read | 2026-11-04 | | Scorecard scorecard.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scoutapm scoutapm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | ScrapingBee scrapingbee.com | Verified no auth | – | 61 C | – | not read | 2026-11-04 | | Screenforge screenforge.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ScreensDesign screensdesign.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | Screenshot Scout screenshotscout.com | Credential wall API key | – | | – | not read | 2026-11-04 | | ScreenVerb screenverb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scripe scripe.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | Seam seam.co | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 53 C | – | no | 2026-11-04 | | Search Fragments searchfragments.com | Verified no auth | – | | – | not read | 2026-11-04 | | SearchAPI searchapi.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | SearchConsole.ai searchconsole.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Searcherries searcherries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Seller Profit Doctor sellerprofitdoctor.com | Verified no auth | – | | – | not read | 2026-11-04 | | Sellfy sellfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Semaphore semaphoreci.com | None found | – | 49 C | – | no | 2026-11-04 | | Semgrep semgrep.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Sendmux sendmux.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | – | not read | 2026-11-04 | | SendPulse sendpulse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | SentinelX sentinelx.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sentry sentry.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | Sentry sentry.io | Sign-in required OAuth DCR; tools not seen, not counted | @sentry/cli | 79 B | – | no | 2026-11-04 | | SEOmatic seomatic.ai | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | Sequencer sequencer.media | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SerpApi serpapi.com | Verified no auth | – | 59 C | – | not read | 2026-11-04 | | Serpstat serpstat.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Server4Agent server4agent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Servicebricks servicebricks.com | No answer | – | | – | not read | 2026-11-04 | | SF Tensor sf-tensor.com | None found | – | 38 D | – | no | 2026-11-04 | | Shaped shaped.ai | None found | – | 47 D | – | no | 2026-11-04 | | ShapelessAI shapelessai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Sherweb sherweb.com | Sign-in required OAuth; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | Shipbook shipbook.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shippo shippo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | ShipStatic shipstatic.com | Verified no auth | – | | – | not read | 2026-11-04 | | Shogun shogun.com | None found | – | 52 C | – | no | 2026-11-04 | | Shopify shopify.com | None found | @shopify/cli | 72 B | – | no | 2026-11-04 | | Short.io short.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shortcut shortcut.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | yes | no | 2026-11-04 | | Shortimize shortimize.com | Verified no auth | – | | – | not read | 2026-11-04 | | ShortSync shortsync.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shuttle shuttle.dev | None found | – | 47 D | – | no | 2026-11-04 | | SID AI sid.ai | None found | – | 35 D | – | no | 2026-11-04 | | Siemens siemens.com | Verified no auth | – | 56 C | – | no | 2026-11-04 | | SigmaMind AI sigmamind.ai | None found | – | 74 B | – | no | 2026-11-04 | | Signadot signadot.com | No answer | – | 68 C | – | no | 2026-11-04 | | SigNoz signoz.io | None found | – | 71 B | – | no | 2026-11-04 | | SimpleBackups simplebackups.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Simplenote simplenote.com | None found | – | 40 D | – | no | 2026-11-04 | | SimplePDF simplepdf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | yes | no | 2026-11-04 | | Simplescraper simplescraper.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Simvoly simvoly.com | None found | – | 54 C | – | no | 2026-11-04 | | Since.dev since.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sisense sisense.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Site24x7 site24x7.com | None found | – | 53 C | – | no | 2026-11-04 | | Sitecore sitecore.com | None found | – | 61 C | – | no | 2026-11-04 | | Sitelemetry sitelemetry.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sitepulsar sitepulsar.ai | Verified no auth | – | | yes | not read | 2026-11-04 | | Sixtyfour sixtyfour.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | SkillDB skilldb.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SKU.io sku.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SkyAccess skyaccess.com | Verified no auth | – | | – | not read | 2026-11-04 | | Skydropx skydropx.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 41 D | – | no | 2026-11-04 | | Skyhook skyhook.io | None found | – | 72 B | – | no | 2026-11-04 | | Skyvern skyvern.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | no | 2026-11-04 | | Slack slack.com | Sign-in required OAuth; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | SlideForge slideforge.dev | Verified no auth | – | | – | not read | 2026-11-04 | | SmartBear smartbear.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SmartGate smartgate.network | Credential wall API key | – | | – | not read | 2026-11-04 | | Smobi smobi.com | None found | – | 52 C | – | no | 2026-11-04 | | smol machines smolmachines.com | None found | – | 80 B | yes | no | 2026-11-04 | | Snorkel AI snorkel.ai | None found | – | 43 D | – | no | 2026-11-04 | | Snowflake snowflake.com | None found | snowflake-cli | 66 C | – | no | 2026-11-04 | | Snyk snyk.io | None found | – | 79 B | – | no | 2026-11-04 | | Social Growth Engineers socialgrowthengineers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sociality.io sociality.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | Socialync socialync.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Softr softr.io | None found | – | 67 C | – | no | 2026-11-04 | | Sofya sofya.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Sonar sonarsource.com | None found | – | 71 B | – | no | 2026-11-04 | | Sonatype sonatype.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | Soracom soracom.com | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/s/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Letter S, page 2 | Agent MCP Directory" description: "170 companies starting with S: MCP server, CLI and OpenAPI status, checked 4 November 2026. Page 2 of 2. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/s/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Letter S, page 2 | Agent MCP Directory > 170 companies starting with S: MCP server, CLI and OpenAPI status, checked 4 November 2026. Page 2 of 2. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/s/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with S, page 2 170 companies in the directory start with the letter S: 27 listed tools to a client with no credentials, 70 answered with a sign-in challenge (not counted), and 6 have a CLI on record. This page lists rows 101 to 170, from Sourcebot to Synth AI. ## Rows 101 to 170 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Sourcebot sourcebot.dev | None found | – | 65 C | – | no | 2026-11-04 | | SourceForge sourceforge.net | None found | – | 69 C | – | no | 2026-11-04 | | Sourcegraph sourcegraph.com | None found | – | 55 C | – | no | 2026-11-04 | | sourcehut sourcehut.org | None found | – | 46 D | – | no | 2026-11-04 | | Spacefast spacefast.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | not read | 2026-11-04 | | Spacelift spacelift.io | None found | – | 62 C | – | no | 2026-11-04 | | Speakeroo speakeroo.app | Verified no auth | – | 73 B | – | not read | 2026-11-04 | | Specific specific.dev | None found | – | 67 C | – | no | 2026-11-04 | | Speedscale speedscale.com | None found | – | 66 C | – | no | 2026-11-04 | | Spicrawl spicrawl.com | Verified no auth | – | | – | not read | 2026-11-04 | | Spike spike.app | None found | – | 34 D | – | no | 2026-11-04 | | Spike spike.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Spinnaker spinnaker.io | None found | – | 39 D | – | no | 2026-11-04 | | Split.io split.io | None found | – | 60 C | – | no | 2026-11-04 | | SpriteCook spritecook.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Spurtest spurtest.com | None found | – | 56 C | – | no | 2026-11-04 | | Square square.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 26 F | – | not read | 2026-11-04 | | Square squareup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Sre sre.ai | None found | – | 50 C | – | no | 2026-11-04 | | SRIFT srift.app | Verified no auth | – | | yes | not read | 2026-11-04 | | SST sst.dev | None found | – | 63 C | – | no | 2026-11-04 | | StableBrowse stablebrowse.com | None found | – | 54 C | – | no | 2026-11-04 | | Stably stably.ai | None found | – | 79 B | – | no | 2026-11-04 | | StackBlitz stackblitz.com | None found | – | 46 D | – | no | 2026-11-04 | | StackOverflow stackoverflow.com | Credential wall API key | – | 23 F | – | no | 2026-11-04 | | Stackup stackup.fi | None found | – | 37 D | – | no | 2026-11-04 | | stagewise stagewise.io | None found | – | 71 B | – | no | 2026-11-04 | | Standard Notes standardnotes.com | None found | – | 37 D | – | no | 2026-11-04 | | StarSling starsling.dev | None found | – | 50 C | – | no | 2026-11-04 | | Startup Ignition startupignition.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Statamic statamic.com | None found | – | 38 D | – | no | 2026-11-04 | | Statsig statsig.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | StatusCake statuscake.com | None found | – | 53 C | – | no | 2026-11-04 | | StatusGator statusgator.com | None found | – | 38 D | – | no | 2026-11-04 | | Statuspage statuspage.io | None found | – | 35 D | – | no | 2026-11-04 | | Steellantern steellantern.com | Verified no auth | – | | – | not read | 2026-11-04 | | Stillwind stillwind.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Storia storia.ai | None found | – | 43 D | – | not read | 2026-11-04 | | StoriesIG storiesig.info | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Storyblok storyblok.com | No tools listed | – | 67 C | – | no | 2026-11-04 | | Storybook storybook.js.org | None found | – | 64 C | – | no | 2026-11-04 | | Strapi strapi.io | None found | – | 64 C | – | no | 2026-11-04 | | Streamkap streamkap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Stripe stripe.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Struct struct.ai | None found | – | 67 C | – | no | 2026-11-04 | | Structura structura.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Studio99 studio99.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Studiomeyer studiomeyer.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | yes | not read | 2026-11-04 | | Studocu studocu.com | Verified no auth | – | 40 D | – | no | 2026-11-04 | | Stytch stytch.com | None found | – | 63 C | – | no | 2026-11-04 | | SubwayInfo NYC subwayinfo.nyc | Verified no auth | – | | yes | not read | 2026-11-04 | | SugarSync sugarsync.com | None found | – | 55 C | – | no | 2026-11-04 | | Sugra sugra.ai | Verified no auth | – | 49 C | – | not read | 2026-11-04 | | Sumologic sumologic.com | None found | – | 71 B | – | no | 2026-11-04 | | Sunpia sunpia.io | None found | – | 40 D | – | no | 2026-11-04 | | Supabase supabase.com | Sign-in required OAuth DCR; tools not seen, not counted | supabase | 93 A | yes | no | 2026-11-04 | | SuperAnnotate superannotate.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 54 C | – | no | 2026-11-04 | | Superb AI superb-ai.com | None found | – | 65 C | – | no | 2026-11-04 | | superglue superglue.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Supernova.io supernova.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Supervisely supervisely.com | None found | – | 65 C | – | no | 2026-11-04 | | SuprSend suprsend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | SurfacedBy AI surfacedby.com | Verified no auth | – | | – | not read | 2026-11-04 | | Surge surge.app | None found | – | 72 B | – | no | 2026-11-04 | | Svelte svelte.dev | Verified no auth | – | 58 C | – | not read | 2026-11-04 | | Svix svix.com | No answer | – | 69 C | – | no | 2026-11-04 | | Swarmia swarmia.com | None found | – | 60 C | – | no | 2026-11-04 | | Sweep sweep.dev | None found | – | 40 D | – | not read | 2026-11-04 | | Symbioza symbioza.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Synth AI usesynth.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/s/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with T | Agent MCP Directory" description: "79 companies starting with T: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/t site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with T | Agent MCP Directory > 79 companies starting with T: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/t Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with T 79 companies in the directory start with the letter T: 15 listed tools to a client with no credentials, 26 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from T3 to Typewise. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | T3 t3.chat | None found | – | 58 C | – | no | 2026-11-04 | | TableJourney tablejourney.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Tabnine tabnine.com | None found | – | 66 C | – | not read | 2026-11-04 | | Tailor tailor.tech | None found | – | 50 C | – | no | 2026-11-04 | | Tailscale tailscale.com | None found | – | 69 C | – | no | 2026-11-04 | | TakeMeUp.cv takemeup.cv | Verified no auth | – | | – | not read | 2026-11-04 | | Tallyfy tallyfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Taloflow taloflow.ai | None found | – | 39 D | – | no | 2026-11-04 | | Tana tana.inc | None found | – | 64 C | – | no | 2026-11-04 | | Tapcart tapcart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | Taplio taplio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | TapTax taptax.co.uk | Verified no auth | – | | – | not read | 2026-11-04 | | Taskfolk taskfolk.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Tavus tavus.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Taxapp taxapp.nz | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Teamwork.com teamwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Techfabric techfabric.com | Verified no auth | – | | – | not read | 2026-11-04 | | Telnyx telnyx.com | Verified no auth | – | 99 A+ | yes | yes | 2026-11-04 | | TempGuru tempguru.co | Verified no auth | – | | – | not read | 2026-11-04 | | Tempo tempo.new | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Temporal temporal.io | None found | – | 61 C | – | no | 2026-11-04 | | Tenet Industries tenetindustries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | | TensorPool tensorpool.dev | None found | – | 35 D | – | no | 2026-11-04 | | Termii termii.com | None found | – | 45 D | – | no | 2026-11-04 | | Terminal Tax terminal.tax | Verified no auth | – | | – | not read | 2026-11-04 | | Terminal Use terminaluse.com | None found | – | 48 C | – | no | 2026-11-04 | | Terracotta tryterracotta.com | None found | – | 52 C | – | no | 2026-11-04 | | Terrateam terrateam.io | None found | – | 52 C | – | no | 2026-11-04 | | Tesorio tesorio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | testRigor testrigor.com | Credential wall API key | – | 56 C | – | no | 2026-11-04 | | Texel.ai texel.ai | None found | – | 52 C | – | no | 2026-11-04 | | The Brains brains.ceo | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | The Bridge thebridge.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | The Context Company thecontext.company | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 58 C | – | no | 2026-11-04 | | The Token Company thetokencompany.com | None found | – | 72 B | yes | no | 2026-11-04 | | The White Report thewhitereport.com | Verified no auth | – | | – | not read | 2026-11-04 | | Theneo theneo.io | No answer | – | 67 C | – | no | 2026-11-04 | | There's An AI For That theresanaiforthat.com | Verified no auth | – | 9 F | – | not read | 2026-11-04 | | ThoughtSpot thoughtspot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | ThousandEyes thousandeyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | Thunder Compute thundercompute.com | None found | – | 76 B | – | no | 2026-11-04 | | Thunkable thunkable.com | None found | – | 48 C | – | no | 2026-11-04 | | TickTick ticktick.com | No answer | – | 61 C | – | no | 2026-11-04 | | Tilda tilda.cc | None found | – | 49 C | – | no | 2026-11-04 | | Time Doctor timedoctor.com | None found | – | 37 D | – | no | 2026-11-04 | | Timely timely.com | None found | – | 58 C | – | no | 2026-11-04 | | Tiptap tiptap.dev | None found | – | 62 C | – | no | 2026-11-04 | | tl;dv tldv.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | not read | 2026-11-04 | | Todoist todoist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Todoist todoist.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Toggl toggl.com | None found | – | 59 C | – | no | 2026-11-04 | | Tomiseregi tomiseregi.si | Verified no auth | – | | – | not read | 2026-11-04 | | TracePass tracepass.eu | Verified no auth | – | | yes | not read | 2026-11-04 | | Trackjs trackjs.com | None found | – | 55 C | – | no | 2026-11-04 | | Trainloop AI trainloop.ai | None found | – | 51 C | – | no | 2026-11-04 | | Trainy trainy.ai | None found | – | 77 B | – | no | 2026-11-04 | | Traveler.md traveler.md | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | yes | not read | 2026-11-04 | | Travis CI travis-ci.com | None found | – | 53 C | – | no | 2026-11-04 | | Tray.ai tray.io | None found | – | 62 C | – | no | 2026-11-04 | | Treza trezalabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | trivago trivago.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | Trivy trivy.dev | None found | – | 34 D | – | no | 2026-11-04 | | Truffle AI trytruffle.ai | None found | – | 47 D | – | no | 2026-11-04 | | Truthifi truthifi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Truthsystems truthsystems.ai | None found | – | 37 D | – | no | 2026-11-04 | | Trynia trynia.ai | None found | – | 62 C | – | no | 2026-11-04 | | Trypillar trypillar.com | None found | – | 49 C | – | not read | 2026-11-04 | | Tumult tumult.com | None found | – | 35 D | – | no | 2026-11-04 | | Turbo Notify turbonotify.com | Verified no auth | – | | – | not read | 2026-11-04 | | Turkishtechlab turkishtechlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Turso turso.tech | None found | – | 84 B | yes | no | 2026-11-04 | | Tusk usetusk.ai | None found | – | 56 C | – | no | 2026-11-04 | | TweetSave tweetsave.org | Verified no auth | – | | – | not read | 2026-11-04 | | Twelfth twelfth.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | yes | not read | 2026-11-04 | | Twelve Data twelvedata.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Twilio twilio.com | Verified no auth | twilio-cli | 85 B | – | no | 2026-11-04 | | txscribe txscribe.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Typeform typeform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Typewise typewise.app | None found | – | 75 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/t/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with U | Agent MCP Directory" description: "23 companies starting with U: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/u site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with U | Agent MCP Directory > 23 companies starting with U: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/u Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with U 23 companies in the directory start with the letter U: 2 listed tools to a client with no credentials, 16 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from Ubicloud to UXKIN. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Ubicloud ubicloud.com | None found | – | 49 C | – | no | 2026-11-04 | | UiPath uipath.com | None found | – | 62 C | – | no | 2026-11-04 | | Uizze uizze.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ulapcybo ulapcybo.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ultralayer ultralayer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Unblocked getunblocked.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | unify unify.ai | None found | – | 42 D | – | no | 2026-11-04 | | Unlayer unlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Unlimitless unlimitless.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Unsiloed AI unsiloed.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Unsloth unsloth.ai | None found | – | 43 D | – | no | 2026-11-04 | | Unstructured unstructured.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | updown.io updown.io | None found | – | 33 D | – | no | 2026-11-04 | | Upload-Post upload-post.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Upscrape upscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Upsolve AI upsolve.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | Upstash upstash.com | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Uptime.com :) uptime.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 59 C | – | no | 2026-11-04 | | UptimeRobot uptimerobot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Upwork upwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | Usercentrics usercentrics.eu | Verified no auth | – | | – | yes | 2026-11-04 | | UX Pilot uxpilot.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | not read | 2026-11-04 | | UXKIN uxkin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/u/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with V | Agent MCP Directory" description: "28 companies starting with V: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/v site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with V | Agent MCP Directory > 28 companies starting with V: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/v Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with V 28 companies in the directory start with the letter V: 5 listed tools to a client with no credentials, 13 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from v0 to Vybenetwork. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | v0 v0.dev | None found | – | 66 C | – | no | 2026-11-04 | | V7labs v7labs.com | None found | – | 72 B | – | no | 2026-11-04 | | Vaaya vaaya.ai | Verified no auth | – | 90 A | yes | not read | 2026-11-04 | | Valkyrlabs valkyrlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vanta vanta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | VectorShift vectorshift.ai | None found | – | 69 C | – | no | 2026-11-04 | | Veles getveles.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | Vercel vercel.com | Sign-in required OAuth DCR; tools not seen, not counted | vercel | 91 A | yes | no | 2026-11-04 | | Veridu veridu.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | VeriTeknik veriteknik.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Versive getversive.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | Veryfi veryfi.com | None found | – | 69 C | – | no | 2026-11-04 | | vibe vibe.codes | None found | – | 39 D | – | no | 2026-11-04 | | VibeFlow vibeflow.ai | None found | – | 73 B | – | no | 2026-11-04 | | VibeMarketing vibemarketing.ninja | Verified no auth | – | | – | not read | 2026-11-04 | | VibeSEO vibeseo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vidova vidova.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | Vike vike.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vimmerse vimmerse.net | None found | – | 52 C | – | no | 2026-11-04 | | Viridisconservation viridisconservation.com | Verified no auth | – | | – | not read | 2026-11-04 | | Virtualmin virtualmin.com | None found | – | 40 D | – | no | 2026-11-04 | | Visa visa.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | VISEON viseon.io | Verified no auth | – | | – | not read | 2026-11-04 | | vocode vocode.dev | None found | – | 60 C | – | no | 2026-11-04 | | Voker voker.ai | None found | – | 62 C | – | no | 2026-11-04 | | Vooban vooban.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vultr vultr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | Vybenetwork vybenetwork.com | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/v/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with W | Agent MCP Directory" description: "39 companies starting with W: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/w site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with W | Agent MCP Directory > 39 companies starting with W: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/w Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with W 39 companies in the directory start with the letter W: 6 listed tools to a client with no credentials, 12 answered with a sign-in challenge (not counted), and 2 have a CLI on record. Rows run from Waldium to WunderGraph. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Waldium waldium.com | No answer | – | 37 D | – | no | 2026-11-04 | | Wall Marketing wall.marketing | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Warp warp.dev | None found | – | 80 B | – | no | 2026-11-04 | | WarpBuild warpbuild.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Wasmer wasmer.io | None found | – | 62 C | – | no | 2026-11-04 | | Watchgoose watchgoose.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | yes | not read | 2026-11-04 | | Waydev waydev.co | None found | – | 64 C | – | no | 2026-11-04 | | WayStation waystation.ai | No answer | – | | – | not read | 2026-11-04 | | Web3Juice web3juice.com | Verified no auth | – | | – | not read | 2026-11-04 | | Webflow webflow.com | Sign-in required OAuth DCR; tools not seen, not counted | @webflow/webflow-cli | 78 B | – | not read | 2026-11-04 | | Webhound webhound.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | WebinarIgnition webinarignition.com | Verified no auth | – | | – | not read | 2026-11-04 | | Webiny webiny.com | None found | – | 67 C | – | no | 2026-11-04 | | WebZum webzum.com | Verified no auth | – | | – | not read | 2026-11-04 | | WeTransfer wetransfer.com | None found | – | 39 D | – | no | 2026-11-04 | | WeWeb weweb.io | None found | – | 62 C | – | no | 2026-11-04 | | Whalesync whalesync.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Whimsical whimsical.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | | WhitePact whitepact.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WhyLabs whylabs.ai | None found | – | 47 D | – | no | 2026-11-04 | | Wild Moose AI wildmoose.ai | None found | – | 59 C | – | no | 2026-11-04 | | Windmill windmill.dev | None found | – | 56 C | – | no | 2026-11-04 | | Windsurf windsurf.com | None found | – | 57 C | – | no | 2026-11-04 | | WITAN Markets witan.markets | Verified no auth | – | | yes | not read | 2026-11-04 | | Wix wix.com | Sign-in required OAuth DCR; tools not seen, not counted | @wix/cli | 64 C | – | no | 2026-11-04 | | Wiz wiz.io | None found | – | 58 C | – | no | 2026-11-04 | | Wolfram wolfram.com | Verified no auth | – | | – | no | 2026-11-04 | | Woodpecker CI woodpecker-ci.org | None found | – | 39 D | – | no | 2026-11-04 | | Workamajig workamajig.com | No answer | – | 62 C | – | no | 2026-11-04 | | Workato workato.com | No answer | – | 64 C | – | no | 2026-11-04 | | Workflowy workflowy.com | None found | – | 59 C | – | no | 2026-11-04 | | WorkOS workos.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Wp wp.com | None found | – | 46 D | – | no | 2026-11-04 | | WP Agent getwpagent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WP Engine wpengine.com | None found | – | 68 C | – | no | 2026-11-04 | | WPWriter wpwriter.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WRDO wrdo.co.za | Verified no auth | – | 48 C | – | not read | 2026-11-04 | | Wrike wrike.com | No answer | – | 66 C | – | no | 2026-11-04 | | WunderGraph wundergraph.com | None found | – | 70 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/w/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with X | Agent MCP Directory" description: "3 companies starting with X: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/x site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with X | Agent MCP Directory > 3 companies starting with X: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/x Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with X 3 companies in the directory start with the letter X: 2 listed tools to a client with no credentials, 1 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from Xenition to Xquik. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Xenition xenition.com | Verified no auth | – | | – | not read | 2026-11-04 | | XMemo xmemo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | not read | 2026-11-04 | | Xquik xquik.com | Verified no auth | – | 92 A | yes | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/x/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with Y | Agent MCP Directory" description: "1 company starting with Y: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Dated and sourced." canonical: https://agentmcpdirectory.com/directory/letter/y site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with Y | Agent MCP Directory > 1 company starting with Y: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Dated and sourced. Source: https://agentmcpdirectory.com/directory/letter/y Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with Y 1 company in the directory start with the letter Y: 1 listed tools to a client with no credentials, 0 answered with a sign-in challenge (not counted), and 0 have a CLI on record. Rows run from YouSpot to YouSpot. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | YouSpot youspot.com | Verified no auth | – | 98 A+ | yes | yes | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/y/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Companies starting with Z | Agent MCP Directory" description: "15 companies starting with Z: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry." canonical: https://agentmcpdirectory.com/directory/letter/z site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Companies starting with Z | Agent MCP Directory > 15 companies starting with Z: MCP server, CLI and OpenAPI status, checked 4 November 2026. Each row links to a full entry. Source: https://agentmcpdirectory.com/directory/letter/z Site: Agent MCP Directory Last reviewed: 2026-11-05 # Companies starting with Z 15 companies in the directory start with the letter Z: 5 listed tools to a client with no credentials, 7 answered with a sign-in challenge (not counted), and 1 has a CLI on record. Rows run from Zapier to Zoom. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Zapier zapier.com | Sign-in required OAuth DCR; tools not seen, not counted | zapier-platform-cli | 84 B | – | no | 2026-11-04 | | Zed zed.dev | None found | – | 57 C | – | no | 2026-11-04 | | Zenable zenable.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Zentrik zentrik.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | not read | 2026-11-04 | | ZeroDev zerodev.app | None found | – | 46 D | – | no | 2026-11-04 | | ZeroEntropy zeroentropy.dev | No answer | – | 73 B | – | no | 2026-11-04 | | ZeroEval zeroeval.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 65 C | – | no | 2026-11-04 | | zeroheight zeroheight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Zinc zinc.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | | Zine zine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Zip-Codes.com zip-codes.com | Verified no auth | – | | – | not read | 2026-11-04 | | Zip1 zip1.io | Verified no auth | – | | – | not read | 2026-11-04 | | Ziptax zip.tax | Verified no auth | – | | – | not read | 2026-11-04 | | Zomato zomato.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 16 F | – | not read | 2026-11-04 | | Zoom zoom.us | Sign-in required OAuth; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letter/z/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Letterly MCP server | Agent MCP Directory" description: "Letterly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/letterly-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Letterly MCP server | Agent MCP Directory > Letterly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/letterly-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Letterly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Letterly at mcp.letterly.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Letterly | | --- | --- | | Domain | letterly.app | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for letterly.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.letterly.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 349 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:10Z https://mcp.letterly.app/mcp sent initialize result auth-required (HTTP 401) 756 ms - 20:03:29Z https://mcp.letterly.app/mcp sent initialize result auth-required (HTTP 401) 349 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://mcp.letterly.app/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.letterly.app | | Authorization server metadata | api.letterly.app | | Registration endpoint | https://api.letterly.app/register | ### The sign-in route, step by step 1. Request `https://mcp.letterly.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.letterly.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.letterly.app/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Letterly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.letterly/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/letterly-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=letterly), read 4 November 2026 - [Letterly website](https://letterly.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lezzoo MCP server | Agent MCP Directory" description: "Lezzoo has an open MCP server with 21 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lezzoo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lezzoo MCP server | Agent MCP Directory > Lezzoo has an open MCP server with 21 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lezzoo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lezzoo: MCP server, CLI and agent surfaces Yes: Lezzoo runs a public MCP server at mcp.lezzoo.com that listed 21 tools to a client with no credentials on 4 November 2026. Examples: search, search\_merchant\_products, get\_full\_menu. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for lezzoo.com is 69, grade C, read on 5 November 2026. ## Fact sheet | Company | Lezzoo | | --- | --- | | Domain | lezzoo.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 69, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for lezzoo.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.lezzoo.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | lezzoo-mcp 0.15.0 | | Capabilities | resources, tools | | Tools | 21 | | Resources | 6 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 678 ms over 1 attempt | ### Tools listed 21 tools - search - search\_merchant\_products - get\_full\_menu - get\_product\_details - get\_top\_searches - auth\_status - logout - get\_profile - get\_addresses - get\_order\_history - track\_order - view\_cart - add\_to\_cart - update\_cart\_item - remove\_cart\_item - clear\_cart - get\_payment\_methods - get\_wallet\_balance - review\_order - place\_order - get\_payment\_link ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:11Z https://mcp.lezzoo.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 805 ms - 20:03:30Z https://mcp.lezzoo.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 678 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.lezzoo.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lezzoo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: lezzoo.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.lezzoo/lezzoo | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lezzoo-com/index.md) ## Sources - [Ora score page for lezzoo.com](https://ora.ai/score/lezzoo.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/score) - [Where Lezzoo was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.lezzoo%2Flezzoo), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lezzoo), read 4 November 2026 - [Lezzoo website](https://lezzoo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LFG MCP server | Agent MCP Directory" description: "LFG: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lfg-gm site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LFG MCP server | Agent MCP Directory > LFG: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lfg-gm Site: Agent MCP Directory Last reviewed: 2026-11-05 # LFG: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for LFG at mcp.lfg.gm answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | LFG (registry title: LFG Alarm) | | --- | --- | | Domain | lfg.gm | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for lfg.gm when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.lfg.gm | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 787 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:12Z https://mcp.lfg.gm sent initialize result auth-required (HTTP 401) 1782 ms - 20:03:31Z https://mcp.lfg.gm sent initialize result auth-required (HTTP 401) 787 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="LFG Alarm", resource_metadata="https://mcp.lfg.gm/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.lfg.gm | | Authorization server metadata | mcp.lfg.gm | | Registration endpoint | https://mcp.lfg.gm/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.lfg.gm` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.lfg.gm/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.lfg.gm/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for LFG. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: gm.lfg/alarm | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lfg-gm/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lfg), read 4 November 2026 - [LFG website](https://lfg.gm), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lightsprint MCP server | Agent MCP Directory" description: "Does Lightsprint have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lightsprint-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lightsprint MCP server | Agent MCP Directory > Does Lightsprint have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/lightsprint-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lightsprint: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Lightsprint (lightsprint.ai), so the connector had nothing to connect to. Ora's cached score for lightsprint.ai is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Lightsprint (registry title: lightsprint.ai) | | --- | --- | | Domain | lightsprint.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for lightsprint.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Lightsprint. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for lightsprint.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Lightsprint. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lightsprint-ai/index.md) ## Sources - [Ora score page for lightsprint.ai](https://ora.ai/score/lightsprint.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Lightsprint was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Lightsprint website](https://lightsprint.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lightstep MCP server | Agent MCP Directory" description: "Does Lightstep have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lightstep-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lightstep MCP server | Agent MCP Directory > Does Lightstep have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/lightstep-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lightstep: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Lightstep (lightstep.com), so the connector had nothing to connect to. Ora's cached score for lightstep.com is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Lightstep (registry title: lightstep.com) | | --- | --- | | Domain | lightstep.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for lightstep.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Lightstep. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for lightstep.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Lightstep. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lightstep-com/index.md) ## Sources - [Ora score page for lightstep.com](https://ora.ai/score/lightstep.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Lightstep was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Limrun MCP server | Agent MCP Directory" description: "Limrun: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/limrun-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Limrun MCP server | Agent MCP Directory > Limrun: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/limrun-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Limrun: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Limrun at mcp.limrun.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Limrun | | --- | --- | | Domain | limrun.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 81, grade B; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for limrun.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.limrun.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,272 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:12Z https://mcp.limrun.com/mcp sent initialize result auth-required (HTTP 401) 1327 ms - 20:03:31Z https://mcp.limrun.com/mcp sent initialize result auth-required (HTTP 401) 1272 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="mcp", resource_metadata="https://mcp.limrun.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.limrun.com | | Authorization server metadata | api.limrun.com | | Registration endpoint | https://api.limrun.com/authn/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.limrun.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.limrun.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.limrun.com/authn/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Limrun. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: limrun.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.limrun/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/limrun-com/index.md) ## Sources - [Ora score page for limrun.com](https://ora.ai/score/limrun.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=limrun), read 4 November 2026 - [Limrun website](https://limrun.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Linear MCP server | Agent MCP Directory" description: "Linear: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/linear-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Linear MCP server | Agent MCP Directory > Linear: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/linear-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Linear: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Linear at mcp.linear.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Linear | | --- | --- | | Domain | linear.app | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 8,389 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for linear.app, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.linear.app/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 110 ms over 1 attempt | | Documentation | linear.app | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:14Z https://mcp.linear.app/mcp sent initialize result auth-required (HTTP 401) 83 ms - 20:01:53Z https://mcp.linear.app/mcp sent initialize result auth-required (HTTP 401) 110 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.linear.app/.well-known/oauth-protected-resource/mcp", scope="read write" | | Protected resource metadata | mcp.linear.app | | Authorization server metadata | mcp.linear.app | | Registration endpoint | https://mcp.linear.app/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.linear.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.linear.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.linear.app/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Linear. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.linear/linear | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/linear-app/index.md) ## Sources - [Linear MCP documentation](https://linear.app/docs/mcp), read 4 November 2026 - [Ora score page for linear.app](https://ora.ai/score/linear.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=linear), read 4 November 2026 - [Linear website](https://linear.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lingo.dev MCP server | Agent MCP Directory" description: "Lingo.dev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/lingo-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lingo.dev MCP server | Agent MCP Directory > Lingo.dev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/lingo-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lingo.dev: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Lingo.dev at mcp.lingo.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Lingo.dev | | --- | --- | | Domain | lingo.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 50, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for lingo.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.lingo.dev/main | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 221 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:12Z https://mcp.lingo.dev/main sent initialize result auth-required (HTTP 401) 1002 ms - 20:03:30Z https://mcp.lingo.dev/main sent initialize result auth-required (HTTP 401) 221 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.lingo.dev/.well-known/oauth-protected-resource/main" | | Protected resource metadata | mcp.lingo.dev | | Authorization server metadata | oauth.lingo.dev | | Registration endpoint | https://oauth.lingo.dev/register | ### The sign-in route, step by step 1. Request `https://mcp.lingo.dev/main` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.lingo.dev/.well-known/oauth-protected-resource/main` to find the authorization server. 3. Register a client at the registration endpoint `https://oauth.lingo.dev/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lingo.dev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.lingo/main | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lingo-dev/index.md) ## Sources - [Ora score page for lingo.dev](https://ora.ai/score/lingo.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Lingo.dev was found](https://registry.modelcontextprotocol.io/v0/servers?search=dev.lingo%2Fmain), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lingo), read 4 November 2026 - [Lingo.dev website](https://lingo.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Linode MCP server | Agent MCP Directory" description: "Does Linode have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/linode-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Linode MCP server | Agent MCP Directory > Does Linode have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/linode-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Linode: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Linode (linode.com), so the connector had nothing to connect to. Ora's cached score for linode.com is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Linode | | --- | --- | | Domain | linode.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 742 on the list of 4 November 2026 | | Ora score | 53, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for linode.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Linode. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for linode.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Linode. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/linode-com/index.md) ## Sources - [Ora score page for linode.com](https://ora.ai/score/linode.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/score) - [Where Linode was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Linode website](https://linode.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Liquilens MCP server | Agent MCP Directory" description: "Liquilens has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/liquilens-in site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Liquilens MCP server | Agent MCP Directory > Liquilens has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/liquilens-in Site: Agent MCP Directory Last reviewed: 2026-11-05 # Liquilens: MCP server, CLI and agent surfaces Yes: Liquilens runs a public MCP server at liquilens.in that listed 3 tools to a client with no credentials on 4 November 2026. Examples: financial\_evidence\_topics, financial\_evidence\_route, financial\_evidence\_fetch. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for liquilens.in is 72, grade B, read on 5 November 2026. ## Fact sheet | Company | Liquilens (registry title: Financial Evidence) | | --- | --- | | Domain | liquilens.in | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 72, grade B; Ora scanned the domain on 30 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for liquilens.in, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://liquilens.in/mcp/financial-evidence | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | financial-evidence 0.1.16 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 182 ms over 1 attempt | ### Tools listed 3 tools - financial\_evidence\_topics - financial\_evidence\_route - financial\_evidence\_fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:12Z https://liquilens.in/mcp/financial-evidence sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 470 ms - 20:03:31Z https://liquilens.in/mcp/financial-evidence sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 182 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://liquilens.in/mcp/financial-evidence` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Liquilens. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/liquilens-in/index.md) ## Sources - [Ora score page for liquilens.in](https://ora.ai/score/liquilens.in?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 August 2026, read from GET /api/score) - [Liquilens website](https://liquilens.in), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Listenetic MCP server | Agent MCP Directory" description: "Listenetic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/listenetic-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Listenetic MCP server | Agent MCP Directory > Listenetic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/listenetic-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Listenetic: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Listenetic at mcp.listenetic.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Listenetic | | --- | --- | | Domain | listenetic.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for listenetic.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.listenetic.com/v1/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 534 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:18Z https://mcp.listenetic.com/v1/mcp sent initialize result auth-required (HTTP 401) 6661 ms - 20:03:31Z https://mcp.listenetic.com/v1/mcp sent initialize result auth-required (HTTP 401) 534 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.listenetic.com/v1/mcp/.well-known/oauth-protected-resource", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.listenetic.com | | Authorization server metadata | auth.listenetic.com | | Registration endpoint | https://auth.listenetic.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.listenetic.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.listenetic.com/v1/mcp/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.listenetic.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Listenetic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/listenetic-com/index.md) ## Sources - [Where Listenetic was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Listenetic website](https://listenetic.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LiteLLM MCP server | Agent MCP Directory" description: "Does LiteLLM have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/litellm-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LiteLLM MCP server | Agent MCP Directory > Does LiteLLM have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/litellm-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # LiteLLM: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for LiteLLM (litellm.ai), so the connector had nothing to connect to. Ora's cached score for litellm.ai is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | LiteLLM (registry title: litellm.ai) | | --- | --- | | Domain | litellm.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for litellm.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for LiteLLM. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for litellm.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for LiteLLM. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/litellm-ai/index.md) ## Sources - [Ora score page for litellm.ai](https://ora.ai/score/litellm.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where LiteLLM was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [LiteLLM website](https://litellm.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LiveCRM MCP server | Agent MCP Directory" description: "LiveCRM: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM." canonical: https://agentmcpdirectory.com/directory/livecrm-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LiveCRM MCP server | Agent MCP Directory > LiveCRM: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM. Source: https://agentmcpdirectory.com/directory/livecrm-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # LiveCRM: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for LiveCRM at api.livecrm.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | LiveCRM | | --- | --- | | Domain | livecrm.ai | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for livecrm.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.livecrm.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 678 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:13Z https://api.livecrm.ai/mcp sent initialize result auth-required (HTTP 401) 1127 ms - 20:03:31Z https://api.livecrm.ai/mcp sent initialize result auth-required (HTTP 401) 678 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.livecrm.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | api.livecrm.ai | | Authorization server metadata | api.livecrm.ai | | Registration endpoint | https://api.livecrm.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://api.livecrm.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.livecrm.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.livecrm.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for LiveCRM. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.livecrm/livecrm | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/livecrm-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=livecrm), read 4 November 2026 - [LiveCRM website](https://livecrm.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LiveScore MCP server | Agent MCP Directory" description: "LiveScore MCP has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/livescoremcp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LiveScore MCP server | Agent MCP Directory > LiveScore MCP has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/livescoremcp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # LiveScore MCP: MCP server, CLI and agent surfaces Yes: LiveScore MCP runs a public MCP server at livescoremcp.com that listed 16 tools to a client with no credentials on 4 November 2026. Examples: fetch, get\_day\_fixtures, get\_fixtures. It speaks sse, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | LiveScore MCP | | --- | --- | | Domain | livescoremcp.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for livescoremcp.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://livescoremcp.com/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | sse | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | livescore-mcp 1.5.0 | | Capabilities | prompts, resources, tools | | Tools | 16 | | Resources | 1 | | Prompts | 4 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 931 ms over 2 attempts | ### Tools listed 16 tools - fetch - get\_day\_fixtures - get\_fixtures - get\_head\_to\_head - get\_league\_fixtures - get\_live\_scores - get\_match - get\_match\_commentary - get\_match\_report - get\_player - get\_standings - get\_team - get\_team\_image - get\_top\_scorers - health - search ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:14Z https://livescoremcp.com/sse sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1026 ms - 20:03:32Z https://livescoremcp.com/sse sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 931 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://livescoremcp.com/sse` over sse. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for LiveScore MCP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/livescoremcp-com/index.md) ## Sources - [Where LiveScore MCP was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [LiveScore MCP website](https://livescoremcp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Llmdata MCP server | Agent MCP Directory" description: "Does Llmdata have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/llmdata-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Llmdata MCP server | Agent MCP Directory > Does Llmdata have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/llmdata-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Llmdata: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Llmdata (llmdata.com), so the connector had nothing to connect to. Ora's cached score for llmdata.com is 35, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Llmdata (registry title: llmdata.com) | | --- | --- | | Domain | llmdata.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 35, grade D; Ora scanned the domain on 8 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for llmdata.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Llmdata. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for llmdata.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Llmdata. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/llmdata-com/index.md) ## Sources - [Ora score page for llmdata.com](https://ora.ai/score/llmdata.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 August 2026, read from GET /api/leaderboard) - [Where Llmdata was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Llmdata website](https://llmdata.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LLM Pulse MCP server | Agent MCP Directory" description: "LLM Pulse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/llmpulse-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LLM Pulse MCP server | Agent MCP Directory > LLM Pulse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/llmpulse-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # LLM Pulse: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for LLM Pulse at api.llmpulse.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | LLM Pulse | | --- | --- | | Domain | llmpulse.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 74, grade B; Ora scanned the domain on 30 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for llmpulse.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.llmpulse.ai/api/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 408 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:13Z https://api.llmpulse.ai/api/v1/mcp sent initialize result auth-required (HTTP 401) 609 ms - 20:03:32Z https://api.llmpulse.ai/api/v1/mcp sent initialize result auth-required (HTTP 401) 408 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.llmpulse.ai/.well-known/oauth-protected-resource/api/v1/mcp", error="invalid_token", error_description="missing bearer token" | | Protected resource metadata | api.llmpulse.ai | | Authorization server metadata | llmpulse.ai | | Registration endpoint | https://llmpulse.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://api.llmpulse.ai/api/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.llmpulse.ai/.well-known/oauth-protected-resource/api/v1/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://llmpulse.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for LLM Pulse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/llmpulse-ai/index.md) ## Sources - [Ora score page for llmpulse.ai](https://ora.ai/score/llmpulse.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 August 2026, read from GET /api/score) - [Where LLM Pulse was found](https://github.com/mcp/LLM-Pulse/llmpulse-mcp), read 4 November 2026 - [LLM Pulse website](https://llmpulse.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Llmtxt MCP server | Agent MCP Directory" description: "Llmtxt has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/llmtxt-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Llmtxt MCP server | Agent MCP Directory > Llmtxt has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/llmtxt-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Llmtxt: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Llmtxt (mcp.llmtxt.dev), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: ENOTFOUND. The row is kept so the claim is visible and can be re-checked next edition. ## Fact sheet | Company | Llmtxt (registry title: LLM Text) | | --- | --- | | Domain | llmtxt.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for llmtxt.dev when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.llmtxt.dev/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 3 ms over 1 attempt | | Result | ENOTFOUND | ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:58:13Z https://mcp.llmtxt.dev/sse sent initialize result no-answer 161 ms - 20:03:31Z https://mcp.llmtxt.dev/sse sent initialize result no-answer 3 ms - 20:03:31Z https://mcp.llmtxt.dev/mcp sent initialize result no-answer 1 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.llmtxt.dev/sse`. The connector could not tell what it wants: ENOTFOUND. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Llmtxt. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/llmtxt-dev/index.md) ## Sources - [Where Llmtxt was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Local MCP server | Agent MCP Directory" description: "Local MCP: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/local-mcp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Local MCP server | Agent MCP Directory > Local MCP: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/local-mcp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Local MCP: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Local MCP at local-mcp.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Local MCP (registry title: LMCP) | | --- | --- | | Domain | local-mcp.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for local-mcp.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://local-mcp.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 754 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:14Z https://local-mcp.com/mcp sent initialize result auth-required (HTTP 401) 1310 ms - 20:03:32Z https://local-mcp.com/mcp sent initialize result auth-required (HTTP 401) 754 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://local-mcp.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | local-mcp.com | | Authorization server metadata | www.local-mcp.com | | Registration endpoint | https://www.local-mcp.com/oauth/register | ### The sign-in route, step by step 1. Request `https://local-mcp.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://local-mcp.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://www.local-mcp.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Local MCP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.local-mcp/local-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Yes: lanchuske/local-mcp | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/local-mcp-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=local-mcp), read 4 November 2026 - [Local MCP website](https://local-mcp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Localcmd MCP server | Agent MCP Directory" description: "Localcmd: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/localcmd-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Localcmd MCP server | Agent MCP Directory > Localcmd: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/localcmd-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Localcmd: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Localcmd at localcmd.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Localcmd (registry title: Local Commander) | | --- | --- | | Domain | localcmd.app | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for localcmd.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://localcmd.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 556 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:14Z https://localcmd.app/mcp sent initialize result auth-required (HTTP 401) 690 ms - 20:03:32Z https://localcmd.app/mcp sent initialize result auth-required (HTTP 401) 556 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://localcmd.app/.well-known/oauth-protected-resource/mcp", scope="devices:read sessions:manage files:read files:write commands:execute processes:control localhost:access" | | Protected resource metadata | localcmd.app | | Authorization server metadata | localcmd.app | | Registration endpoint | https://localcmd.app/oauth/register | ### The sign-in route, step by step 1. Request `https://localcmd.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://localcmd.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://localcmd.app/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Localcmd. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.localcmd/local-commander | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/localcmd-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=localcmd), read 4 November 2026 - [Localcmd website](https://localcmd.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lodestarindex MCP server | Agent MCP Directory" description: "Lodestarindex has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lodestarindex-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lodestarindex MCP server | Agent MCP Directory > Lodestarindex has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lodestarindex-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lodestarindex: MCP server, CLI and agent surfaces Yes: Lodestarindex runs a public MCP server at api.lodestarindex.com that listed 7 tools to a client with no credentials on 4 November 2026. Examples: get\_receipt, batch\_receipts, find\_business. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Lodestarindex (registry title: Lodestar Stamp) | | --- | --- | | Domain | lodestarindex.com | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for lodestarindex.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.lodestarindex.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | lodestar-stamp-mcp 0.1.19 | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 759 ms over 1 attempt | ### Tools listed 7 tools - get\_receipt - batch\_receipts - find\_business - list\_markets - list\_index - list\_sources - list\_gaps ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:15Z https://api.lodestarindex.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1770 ms - 20:03:32Z https://api.lodestarindex.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 759 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.lodestarindex.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lodestarindex. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.github.Banjo-Ventures/lodestar-stamp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lodestarindex-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lodestarindex), read 4 November 2026 - [Lodestarindex website](https://lodestarindex.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Loft MCP server | Agent MCP Directory" description: "Does Loft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/loft-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Loft MCP server | Agent MCP Directory > Does Loft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/loft-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Loft: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Loft (loft.sh), so the connector had nothing to connect to. Ora's cached score for loft.sh is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Loft (registry title: loft.sh) | | --- | --- | | Domain | loft.sh | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for loft.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Loft. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for loft.sh, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Loft. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/loft-sh/index.md) ## Sources - [Ora score page for loft.sh](https://ora.ai/score/loft.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/leaderboard) - [Where Loft was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Loft website](https://loft.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Loggly MCP server | Agent MCP Directory" description: "Does Loggly have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/loggly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Loggly MCP server | Agent MCP Directory > Does Loggly have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/loggly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Loggly: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Loggly (loggly.com), so the connector had nothing to connect to. Ora's cached score for loggly.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Loggly (registry title: loggly.com) | | --- | --- | | Domain | loggly.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 4,918 on the list of 4 November 2026 | | Ora score | 52, grade C; Ora scanned the domain on 10 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for loggly.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Loggly. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for loggly.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Loggly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/loggly-com/index.md) ## Sources - [Ora score page for loggly.com](https://ora.ai/score/loggly.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 September 2026, read from GET /api/score) - [Where Loggly was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Loggly website](https://loggly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LogicMonitor MCP server | Agent MCP Directory" description: "Does LogicMonitor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/logicmonitor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LogicMonitor MCP server | Agent MCP Directory > Does LogicMonitor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/logicmonitor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # LogicMonitor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for LogicMonitor (logicmonitor.com), so the connector had nothing to connect to. Ora's cached score for logicmonitor.com is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | LogicMonitor (registry title: logicmonitor.com) | | --- | --- | | Domain | logicmonitor.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 5,725 on the list of 4 November 2026 | | Ora score | 46, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for logicmonitor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for LogicMonitor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for logicmonitor.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for LogicMonitor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/logicmonitor-com/index.md) ## Sources - [Ora score page for logicmonitor.com](https://ora.ai/score/logicmonitor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/score) - [Where LogicMonitor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [LogicMonitor website](https://logicmonitor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "LogRocket MCP server | Agent MCP Directory" description: "LogRocket: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/logrocket-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # LogRocket MCP server | Agent MCP Directory > LogRocket: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/logrocket-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # LogRocket: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for LogRocket; the connector's guess at mcp.logrocket.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | LogRocket | | --- | --- | | Domain | logrocket.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for logrocket.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.logrocket.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,222 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:15Z https://mcp.logrocket.com/mcp sent initialize result auth-required (HTTP 401) 1170 ms - 20:03:33Z https://mcp.logrocket.com/mcp sent initialize result auth-required (HTTP 401) 1222 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.logrocket.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.logrocket.com | | Authorization server metadata | mcp.logrocket.com | | Registration endpoint | https://mcp.logrocket.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.logrocket.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.logrocket.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.logrocket.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for LogRocket. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/logrocket-com/index.md) ## Sources - [Ora score page for logrocket.com](https://ora.ai/score/logrocket.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where LogRocket was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [LogRocket website](https://logrocket.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Logseq MCP server | Agent MCP Directory" description: "Does Logseq have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/logseq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Logseq MCP server | Agent MCP Directory > Does Logseq have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/logseq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Logseq: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Logseq (logseq.com), so the connector had nothing to connect to. Ora's cached score for logseq.com is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Logseq (registry title: logseq.com) | | --- | --- | | Domain | logseq.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for logseq.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Logseq. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for logseq.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Logseq. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/logseq-com/index.md) ## Sources - [Ora score page for logseq.com](https://ora.ai/score/logseq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/leaderboard) - [Where Logseq was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Logseq website](https://logseq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Logz.io MCP server | Agent MCP Directory" description: "Does Logz.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/logz-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Logz.io MCP server | Agent MCP Directory > Does Logz.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/logz-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Logz.io: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Logz.io (logz.io), so the connector had nothing to connect to. Ora's cached score for logz.io is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Logz.io | | --- | --- | | Domain | logz.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for logz.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Logz.io. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for logz.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Logz.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: logz.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/logz-io/index.md) ## Sources - [Ora score page for logz.io](https://ora.ai/score/logz.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where Logz.io was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Logz.io website](https://logz.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Longbridge MCP server | Agent MCP Directory" description: "Longbridge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/longbridge-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Longbridge MCP server | Agent MCP Directory > Longbridge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/longbridge-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Longbridge: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Longbridge at mcp.longbridge.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Longbridge | | --- | --- | | Domain | longbridge.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 62, grade C; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for longbridge.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.longbridge.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,734 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:16Z https://mcp.longbridge.com sent initialize result auth-required (HTTP 401) 1291 ms - 20:03:34Z https://mcp.longbridge.com sent initialize result auth-required (HTTP 401) 1734 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.longbridge.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.longbridge.com | | Authorization server metadata | mcp.longbridge.com | | Registration endpoint | https://openapi.longbridge.com/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.longbridge.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.longbridge.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://openapi.longbridge.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Longbridge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.longbridge/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/longbridge-com/index.md) ## Sources - [Ora score page for longbridge.com](https://ora.ai/score/longbridge.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=longbridge), read 4 November 2026 - [Longbridge website](https://longbridge.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lotas AI MCP server | Agent MCP Directory" description: "Does Lotas AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lotas-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lotas AI MCP server | Agent MCP Directory > Does Lotas AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/lotas-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lotas AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Lotas AI (lotas.ai), so the connector had nothing to connect to. Ora's cached score for lotas.ai is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Lotas AI | | --- | --- | | Domain | lotas.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for lotas.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Lotas AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for lotas.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Lotas AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lotas-ai/index.md) ## Sources - [Ora score page for lotas.ai](https://ora.ai/score/lotas.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Lotas AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Lotas AI website](https://lotas.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lucid MCP server | Agent MCP Directory" description: "Lucid: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lucid-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lucid MCP server | Agent MCP Directory > Lucid: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lucid-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lucid: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Lucid at mcp.lucid.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Lucid | | --- | --- | | Domain | lucid.app | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for lucid.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.lucid.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 892 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:16Z https://mcp.lucid.app/mcp sent initialize result auth-required (HTTP 401) 949 ms - 20:03:33Z https://mcp.lucid.app/mcp sent initialize result auth-required (HTTP 401) 892 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.lucid.app | | Authorization server metadata | mcp.lucid.app | | Registration endpoint | https://mcp.lucid.app/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.lucid.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.lucid.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.lucid.app/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lucid. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.lucid.mcp/lucid | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lucid-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lucid), read 4 November 2026 - [Lucid website](https://lucid.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Luciq MCP server | Agent MCP Directory" description: "Does Luciq have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/luciq-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Luciq MCP server | Agent MCP Directory > Does Luciq have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/luciq-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Luciq: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Luciq (luciq.ai), so the connector had nothing to connect to. Ora's cached score for luciq.ai is 77, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Luciq (registry title: luciq.ai) | | --- | --- | | Domain | luciq.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 77, grade B; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for luciq.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Luciq. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for luciq.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Luciq. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/luciq-ai/index.md) ## Sources - [Ora score page for luciq.ai](https://ora.ai/score/luciq.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/leaderboard) - [Where Luciq was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Luciq website](https://luciq.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ludo AI MCP server | Agent MCP Directory" description: "Ludo AI has an open MCP server with 48 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ludo-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ludo AI MCP server | Agent MCP Directory > Ludo AI has an open MCP server with 48 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ludo-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ludo AI: MCP server, CLI and agent surfaces Yes: Ludo AI runs a public MCP server at mcp.ludo.ai that listed 48 tools to a client with no credentials on 4 November 2026. Examples: validateApiKeyEndpoint, createImage, generateWithStyle. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Ludo AI (registry title: Ludo AI Game Assets) | | --- | --- | | Domain | ludo.ai | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for ludo.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.ludo.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | ludoai 0.9.10 | | Capabilities | tools | | Tools | 48 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 506 ms over 1 attempt | ### Tools listed 48 tools; the first 40 names are recorded - validateApiKeyEndpoint - createImage - generateWithStyle - editImage - animateSprite - animateSpriteKeyframes - generatePose - rotateSprite - transferMotion - getDocs - searchDocs - listAnimationPresets - editSpritesheet - rotateSpritesheet - adjustSpritesheet - createSpriteAudio - listDirectionalSpriteStyles - previewDirectionalSprites - createDirectionalSprites - createDirectionalStills - fitDirectionalAccessory - attachDirectionalAccessories - createVideo - createVideoFromReferences - editVideo - upscaleVideo - removeBackground - upscaleImage - convertToPixelArt - create3DModel - create3DModelImage - rigModel - animate3DModel - animate3DModelPreset - createSoundEffect - createAmbiance - createMusic - createAudioTransform - createVoice - createSpeech ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:16Z https://mcp.ludo.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 631 ms - 20:03:33Z https://mcp.ludo.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 506 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.ludo.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ludo AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.ludo/game-assets | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ludo-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ludo), read 4 November 2026 - [Ludo AI website](https://ludo.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Luel MCP server | Agent MCP Directory" description: "Does Luel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/luel-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Luel MCP server | Agent MCP Directory > Does Luel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/luel-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Luel: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Luel (luel.ai), so the connector had nothing to connect to. Ora's cached score for luel.ai is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Luel (registry title: luel.ai) | | --- | --- | | Domain | luel.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for luel.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Luel. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for luel.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Luel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/luel-ai/index.md) ## Sources - [Ora score page for luel.ai](https://ora.ai/score/luel.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Luel was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Luel website](https://luel.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lumman MCP server | Agent MCP Directory" description: "Lumman: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lumman-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lumman MCP server | Agent MCP Directory > Lumman: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lumman-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lumman: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Lumman at mail.lumman.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Lumman (registry title: Multi Calendar) | | --- | --- | | Domain | lumman.co | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for lumman.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mail.lumman.co/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 882 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:17Z https://mail.lumman.co/mcp sent initialize result auth-required (HTTP 401) 1141 ms - 20:03:34Z https://mail.lumman.co/mcp sent initialize result auth-required (HTTP 401) 882 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="lumman-mailboxes", resource_metadata="https://mail.lumman.co/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mail.lumman.co | | Authorization server metadata | gwvrgdrmewwgkjovauzm.supabase.co | | Registration endpoint | https://gwvrgdrmewwgkjovauzm.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://mail.lumman.co/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mail.lumman.co/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://gwvrgdrmewwgkjovauzm.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lumman. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.lumman/calendar, co.lumman/mail | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lumman-co/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lumman), read 4 November 2026 - [Lumman website](https://lumman.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lusha MCP server | Agent MCP Directory" description: "Lusha: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/lusha-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lusha MCP server | Agent MCP Directory > Lusha: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/lusha-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lusha: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Lusha at mcp.lusha.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Lusha (registry title: lusha.com) | | --- | --- | | Domain | lusha.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 86, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for lusha.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.lusha.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 599 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:16Z https://mcp.lusha.com/mcp sent initialize result auth-required (HTTP 401) 638 ms - 20:03:33Z https://mcp.lusha.com/mcp sent initialize result auth-required (HTTP 401) 599 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="missing Authorization header", scope="mcp", resource_metadata="https://mcp.lusha.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.lusha.com | | Authorization server metadata | auth.lusha.com | | Registration endpoint | https://auth.lusha.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.lusha.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.lusha.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.lusha.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Lusha. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.lusha.mcp/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/lusha-com/index.md) ## Sources - [Ora score page for lusha.com](https://ora.ai/score/lusha.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Lusha was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.lusha.mcp%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=lusha), read 4 November 2026 - [Lusha website](https://lusha.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Luw.ai MCP server | Agent MCP Directory" description: "Luw.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/luw-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Luw.ai MCP server | Agent MCP Directory > Luw.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/luw-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Luw.ai: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Luw.ai at mcp.luw.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Luw.ai | | --- | --- | | Domain | luw.ai | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for luw.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.luw.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 843 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:17Z https://mcp.luw.ai/mcp sent initialize result auth-required (HTTP 401) 943 ms - 20:03:34Z https://mcp.luw.ai/mcp sent initialize result auth-required (HTTP 401) 843 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.luw.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.luw.ai | | Authorization server metadata | mcp.luw.ai | | Registration endpoint | https://mcp.luw.ai/register | ### The sign-in route, step by step 1. Request `https://mcp.luw.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.luw.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.luw.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Luw.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.luw/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/luw-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=luw), read 4 November 2026 - [Luw.ai website](https://luw.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Maatsii MCP server | Agent MCP Directory" description: "Maatsii has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/maatsii-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Maatsii MCP server | Agent MCP Directory > Maatsii has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/maatsii-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Maatsii: MCP server, CLI and agent surfaces Yes: Maatsii runs a public MCP server at mcp.maatsii.com that listed 10 tools to a client with no credentials on 4 November 2026. Examples: maatsii\_get\_chart, maatsii\_get\_group, maatsii\_chart\_map. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Maatsii | | --- | --- | | Domain | maatsii.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for maatsii.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.maatsii.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | maatsii-linreg-connector 1.5.1 | | Capabilities | tools, prompts, resources | | Tools | 10 | | Resources | 4 | | Prompts | 1 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,249 ms over 1 attempt | ### Tools listed 10 tools - maatsii\_get\_chart - maatsii\_get\_group - maatsii\_chart\_map - maatsii\_list\_setups - maatsii\_match\_setup - maatsii\_get\_setup - maatsii\_reading\_guide - maatsii\_analysis\_framework - maatsii\_fan\_guide - maatsii\_get\_concept ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:17Z https://mcp.maatsii.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1372 ms - 20:03:34Z https://mcp.maatsii.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1249 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.maatsii.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Maatsii. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.maatsii/linreg | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/maatsii-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=maatsii), read 4 November 2026 - [Maatsii website](https://maatsii.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "mabl MCP server | Agent MCP Directory" description: "mabl: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mabl-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # mabl MCP server | Agent MCP Directory > mabl: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mabl-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # mabl: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for mabl at mcp.mabl.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | mabl | | --- | --- | | Domain | mabl.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 71, grade B; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mabl.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mabl.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,193 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:17Z https://mcp.mabl.com/mcp sent initialize result auth-required (HTTP 401) 870 ms - 20:03:34Z https://mcp.mabl.com/mcp sent initialize result auth-required (HTTP 401) 1193 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.mabl.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.mabl.com | | Authorization server metadata | mcp.mabl.com | | Registration endpoint | https://mcp.mabl.com/register | ### The sign-in route, step by step 1. Request `https://mcp.mabl.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mabl.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.mabl.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for mabl. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mabl/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mabl-com/index.md) ## Sources - [Ora score page for mabl.com](https://ora.ai/score/mabl.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mabl), read 4 November 2026 - [mabl website](https://mabl.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Macfax MCP server | Agent MCP Directory" description: "Macfax has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/macfax-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Macfax MCP server | Agent MCP Directory > Macfax has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/macfax-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Macfax: MCP server, CLI and agent surfaces Yes: Macfax runs a public MCP server at macfax.com that listed 8 tools to a client with no credentials on 4 November 2026. Examples: lookup\_mac\_serial, get\_mac\_price\_stats, get\_mac\_market\_value. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Macfax | | --- | --- | | Domain | macfax.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for macfax.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://macfax.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | com.macfax/macfax 1.0.0 | | Capabilities | tools | | Tools | 8 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,409 ms over 1 attempt | ### Tools listed 8 tools - lookup\_mac\_serial - get\_mac\_price\_stats - get\_mac\_market\_value - search\_mac\_listings - check\_mac\_listing - get\_mac\_report - create\_mac\_alert - get\_macfax\_credit\_balance ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:18Z https://macfax.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1931 ms - 20:03:35Z https://macfax.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1409 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://macfax.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Macfax. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.macfax/macfax | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/macfax-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=macfax), read 4 November 2026 - [Macfax website](https://macfax.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MagicBell MCP server | Agent MCP Directory" description: "Does MagicBell have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/magicbell-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MagicBell MCP server | Agent MCP Directory > Does MagicBell have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/magicbell-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MagicBell: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for MagicBell (magicbell.com), so the connector had nothing to connect to. Ora's cached score for magicbell.com is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | MagicBell (registry title: magicbell.com) | | --- | --- | | Domain | magicbell.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for magicbell.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for MagicBell. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for magicbell.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for MagicBell. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/magicbell-com/index.md) ## Sources - [Ora score page for magicbell.com](https://ora.ai/score/magicbell.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where MagicBell was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [MagicBell website](https://magicbell.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Magic Hour MCP server | Agent MCP Directory" description: "Magic Hour has an open MCP server with 49 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/magichour-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Magic Hour MCP server | Agent MCP Directory > Magic Hour has an open MCP server with 49 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/magichour-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Magic Hour: MCP server, CLI and agent surfaces Yes: Magic Hour runs a public MCP server at mcp.magichour.ai that listed 49 tools to a client with no credentials on 4 November 2026. Examples: get\_workflow\_guide, upload\_chatgpt\_image, ping. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for magichour.ai is 89, grade A, read on 5 November 2026. ## Fact sheet | Company | Magic Hour | | --- | --- | | Domain | magichour.ai | | Category | Gaming & Media (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 89, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for magichour.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.magichour.ai/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | magic-hour 0.1.0 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 49 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,613 ms over 1 attempt | ### Tools listed 49 tools; the first 40 names are recorded - get\_workflow\_guide - upload\_chatgpt\_image - ping - wait\_for\_video\_project - wait\_for\_image\_project - wait\_for\_audio\_project - fetch\_image\_download - fetch\_audio\_download - fetch\_video\_download - get\_account\_info - list\_saved\_items - get\_upload\_urls - get\_face\_detection\_results - detect\_faces - get\_video\_project - delete\_video\_project - create\_talking\_photo - create\_spoken\_ad\_video - edit\_video - translate\_video - upscale\_video - create\_animation - create\_video\_from\_audio - add\_subtitles\_to\_video - replace\_character\_in\_video - swap\_face\_in\_video - create\_video\_from\_image - create\_lip\_sync\_video - create\_video\_from\_text - restyle\_video - get\_image\_project - delete\_image\_project - change\_clothes\_in\_photo - edit\_face\_in\_photo - create\_gif\_or\_short\_video - edit\_image - generate\_headshot - generate\_image - upscale\_image - create\_meme ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:19Z https://mcp.magichour.ai/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1832 ms - 20:03:36Z https://mcp.magichour.ai/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1613 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.magichour.ai/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Magic Hour. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: magichour.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: magichour.ai/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/magichour-ai/index.md) ## Sources - [Ora score page for magichour.ai](https://ora.ai/score/magichour.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Magic Hour website](https://magichour.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Magnitude MCP server | Agent MCP Directory" description: "Does Magnitude have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/magnitude-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Magnitude MCP server | Agent MCP Directory > Does Magnitude have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/magnitude-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Magnitude: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Magnitude (magnitude.dev), so the connector had nothing to connect to. Ora's cached score for magnitude.dev is 74, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Magnitude (registry title: magnitude.dev) | | --- | --- | | Domain | magnitude.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 74, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for magnitude.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Magnitude. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for magnitude.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Magnitude. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/magnitude-dev/index.md) ## Sources - [Ora score page for magnitude.dev](https://ora.ai/score/magnitude.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Magnitude was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Magnitude website](https://magnitude.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mailbuttons MCP server | Agent MCP Directory" description: "Mailbuttons has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mailbuttons-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mailbuttons MCP server | Agent MCP Directory > Mailbuttons has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mailbuttons-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mailbuttons: MCP server, CLI and agent surfaces Yes: Mailbuttons runs a public MCP server at mailbuttons.com that listed 12 tools to a client with no credentials on 4 November 2026. Examples: mailbuttons\_list\_messages, mailbuttons\_get\_message, mailbuttons\_get\_thread. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Mailbuttons | | --- | --- | | Domain | mailbuttons.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for mailbuttons.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mailbuttons.com/api/v1/mcp/rpc | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | mailbuttons-mcp 0.1.4 | | Capabilities | tools | | Tools | 12 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 586 ms over 1 attempt | ### Tools listed 12 tools - mailbuttons\_list\_messages - mailbuttons\_get\_message - mailbuttons\_get\_thread - mailbuttons\_get\_attachment\_text - mailbuttons\_send\_email - mailbuttons\_list\_drafts - mailbuttons\_get\_draft - mailbuttons\_extract\_code - mailbuttons\_propose\_sender - mailbuttons\_request\_promotion - mailbuttons\_audit\_tail - mailbuttons\_export\_audit ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:18Z https://mailbuttons.com/api/v1/mcp/rpc sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 689 ms - 20:03:35Z https://mailbuttons.com/api/v1/mcp/rpc sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 586 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mailbuttons.com/api/v1/mcp/rpc` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mailbuttons. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mailbuttons/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mailbuttons-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mailbuttons), read 4 November 2026 - [Mailbuttons website](https://mailbuttons.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mailkite MCP server | Agent MCP Directory" description: "Mailkite: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/mailkite-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mailkite MCP server | Agent MCP Directory > Mailkite: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/mailkite-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mailkite: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mailkite at mcp.mailkite.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mailkite | | --- | --- | | Domain | mailkite.dev | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 71, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mailkite.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mailkite.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 191 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:18Z https://mcp.mailkite.dev/mcp sent initialize result auth-required (HTTP 401) 822 ms - 20:03:34Z https://mcp.mailkite.dev/mcp sent initialize result auth-required (HTTP 401) 191 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.mailkite.dev/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.mailkite.dev | | Authorization server metadata | mcp.mailkite.dev | | Registration endpoint | https://mcp.mailkite.dev/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.mailkite.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mailkite.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.mailkite.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mailkite. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.mailkite/agent-mail, dev.mailkite/email-agent, dev.mailkite/inbound-email and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mailkite-dev/index.md) ## Sources - [Ora score page for mailkite.dev](https://ora.ai/score/mailkite.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mailkite), read 4 November 2026 - [Mailkite website](https://mailkite.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mailrith MCP server | Agent MCP Directory" description: "Mailrith has an open MCP server with 55 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mailrith-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mailrith MCP server | Agent MCP Directory > Mailrith has an open MCP server with 55 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mailrith-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mailrith: MCP server, CLI and agent surfaces Yes: Mailrith runs a public MCP server at api.mailrith.com that listed 55 tools to a client with no credentials on 4 November 2026. Examples: discovery\_get\_capabilities, workspace\_get, sender\_identities\_list. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for mailrith.com is 97, grade A+, read on 5 November 2026. ## Fact sheet | Company | Mailrith (registry title: Mailrith Email Marketing) | | --- | --- | | Domain | mailrith.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 97, grade A+; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mailrith.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.mailrith.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | mailrith 2.0.1 | | Capabilities | tools, resources, prompts | | Tools | 55 | | Resources | 2 | | Prompts | 1 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,985 ms over 1 attempt | ### Tools listed 55 tools; the first 40 names are recorded - discovery\_get\_capabilities - workspace\_get - sender\_identities\_list - sender\_identities\_get - analytics\_create\_report - analytics\_get\_report - subscribers\_list - subscribers\_get - subscribers\_upsert - subscribers\_update - subscribers\_update\_status - subscribers\_add\_tag - subscribers\_remove\_tag - subscribers\_add\_to\_sequence - subscribers\_remove\_from\_sequence - tags\_list - tags\_get - tags\_create - custom\_fields\_list - custom\_fields\_get - segments\_list - segments\_get - segments\_preview - broadcasts\_list - broadcasts\_create - broadcasts\_get - broadcasts\_update - broadcasts\_preflight - broadcasts\_send\_test - broadcasts\_schedule - broadcasts\_unschedule - broadcasts\_send - broadcasts\_cancel - broadcasts\_get\_send\_progress - sequences\_list - sequences\_create - sequences\_get - sequences\_update - sequences\_preflight - sequences\_preview\_journey ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:20Z https://api.mailrith.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1979 ms - 20:03:36Z https://api.mailrith.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1985 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.mailrith.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mailrith. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: mailrith.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mailrith/mailrith | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mailrith-com/index.md) ## Sources - [Ora score page for mailrith.com](https://ora.ai/score/mailrith.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mailrith), read 4 November 2026 - [Mailrith website](https://mailrith.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Make MCP server | Agent MCP Directory" description: "Make: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/make-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Make MCP server | Agent MCP Directory > Make: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/make-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Make: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Make at mcp.make.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Make | | --- | --- | | Domain | make.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 7,858 on the list of 4 November 2026 | | Ora score | 78, grade B; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for make.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.make.com/v2 | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 700 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:13Z https://mcp.make.com/v2 sent initialize result auth-required (HTTP 401) 626 ms - 20:01:52Z https://mcp.make.com/v2 sent initialize result auth-required (HTTP 401) 700 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.make.com/.well-known/oauth-protected-resource/v2" | | Protected resource metadata | mcp.make.com | | Authorization server metadata | www.make.com | | Registration endpoint | https://www.make.com/oauth/v2/register/mcp-openai | ### The sign-in route, step by step 1. Request `https://mcp.make.com/v2` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.make.com/.well-known/oauth-protected-resource/v2` to find the authorization server. 3. Register a client at the registration endpoint `https://www.make.com/oauth/v2/register/mcp-openai` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Make. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: make.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.make/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/make-com/index.md) ## Sources - [Ora score page for make.com](https://ora.ai/score/make.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/score) - [Where Make was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.make%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=make), read 4 November 2026 - [Make website](https://make.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Malware Patrol MCP server | Agent MCP Directory" description: "Malware Patrol has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/malwarepatrol-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Malware Patrol MCP server | Agent MCP Directory > Malware Patrol has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/malwarepatrol-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # Malware Patrol: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Malware Patrol (mcp.malwarepatrol.net), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: UND\_ERR\_CONNECT\_TIMEOUT. The row is kept so the claim is visible and can be re-checked next edition. ## Fact sheet | Company | Malware Patrol | | --- | --- | | Domain | malwarepatrol.net | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for malwarepatrol.net when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.malwarepatrol.net/v1 | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 10,959 ms over 1 attempt | | Result | UND_ERR_CONNECT_TIMEOUT | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:28Z https://mcp.malwarepatrol.net/v1 sent initialize result no-answer 10630 ms - 20:03:45Z https://mcp.malwarepatrol.net/v1 sent initialize result no-answer 10959 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.malwarepatrol.net/v1`. The connector could not tell what it wants: UND\_ERR\_CONNECT\_TIMEOUT. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Malware Patrol. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.github.AndreC10002/mcp-server-threat-intelligence | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/malwarepatrol-net/index.md) ## Sources - [Where Malware Patrol was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=malwarepatrol), read 4 November 2026 - [Malware Patrol website](https://malwarepatrol.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ManageEngine MCP server | Agent MCP Directory" description: "ManageEngine has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/manageengine-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ManageEngine MCP server | Agent MCP Directory > ManageEngine has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/manageengine-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ManageEngine: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for ManageEngine; the connector tried mcp.manageengine.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: HTTP 200 . 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ManageEngine. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/manageengine-com/index.md) ## Sources - [Ora score page for manageengine.com](https://ora.ai/score/manageengine.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/score) - [Where ManageEngine was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ManageEngine website](https://manageengine.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Manicule MCP server | Agent MCP Directory" description: "Does Manicule have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/manicule-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Manicule MCP server | Agent MCP Directory > Does Manicule have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/manicule-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Manicule: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Manicule (manicule.dev), so the connector had nothing to connect to. Ora's cached score for manicule.dev is 33, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Manicule (registry title: manicule.dev) | | --- | --- | | Domain | manicule.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 33, grade D; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for manicule.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Manicule. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for manicule.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Manicule. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/manicule-dev/index.md) ## Sources - [Ora score page for manicule.dev](https://ora.ai/score/manicule.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/leaderboard) - [Where Manicule was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Manicule website](https://manicule.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Manifold MCP server | Agent MCP Directory" description: "Manifold has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/manifold-markets site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Manifold MCP server | Agent MCP Directory > Manifold has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/manifold-markets Site: Agent MCP Directory Last reviewed: 2026-11-05 # Manifold: MCP server, CLI and agent surfaces Yes: Manifold runs a public MCP server at api.manifold.markets that listed 5 tools to a client with no credentials on 4 November 2026. Examples: search-markets, get-market, get-user. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Manifold | | --- | --- | | Domain | manifold.markets | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for manifold.markets when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.manifold.markets/v0/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | manifold-markets 0.2.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 648 ms over 1 attempt | ### Tools listed 5 tools - search-markets - get-market - get-user - get-bets - search-users ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:19Z https://api.manifold.markets/v0/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 733 ms - 20:03:35Z https://api.manifold.markets/v0/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 648 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://api.manifold.markets/v0/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Manifold. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/manifold-markets/index.md) ## Sources - [Where Manifold was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Manifold website](https://manifold.markets), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Manufact MCP server | Agent MCP Directory" description: "Manufact: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/manufact-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Manufact MCP server | Agent MCP Directory > Manufact: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/manufact-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Manufact: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Manufact; the connector's guess at mcp.manufact.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Manufact | | --- | --- | | Domain | manufact.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 83, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for manufact.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.manufact.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 619 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:20Z https://mcp.manufact.com/mcp sent initialize result auth-required (HTTP 401) 1436 ms - 20:03:35Z https://mcp.manufact.com/mcp sent initialize result auth-required (HTTP 401) 619 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication is required for this request.", resource_metadata="https://mcp.manufact.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.manufact.com | | Authorization server metadata | cloud.manufact.com | | Registration endpoint | https://cloud.manufact.com/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.manufact.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.manufact.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://cloud.manufact.com/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Manufact. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: manufact.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/manufact-com/index.md) ## Sources - [Ora score page for manufact.com](https://ora.ai/score/manufact.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/leaderboard) - [Where Manufact was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Manufact website](https://manufact.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mapbox MCP server | Agent MCP Directory" description: "Mapbox: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mapbox-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mapbox MCP server | Agent MCP Directory > Mapbox: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mapbox-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mapbox: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mapbox at mcp.mapbox.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mapbox | | --- | --- | | Domain | mapbox.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 1,910 on the list of 4 November 2026 | | Ora score | 77, grade B; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mapbox.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mapbox.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,077 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.mapbox.com/mcp sent initialize result auth-required (HTTP 401) 772 ms - 20:01:34Z https://mcp.mapbox.com/mcp sent initialize result auth-required (HTTP 401) 1077 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer, realm="https://mcp.mapbox.com/mcp", scope="styles:tiles styles:read fonts:read datasets:read tokens:read", error="Bearer token required", resource_metadata="https://mcp.mapbox.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.mapbox.com | | Authorization server metadata | mcp.mapbox.com | | Registration endpoint | https://api.mapbox.com/oauth/register?scope=styles%3Atiles%20styles%3Aread%20fonts%3Aread%20datasets%3Aread%20tokens%3Aread | ### The sign-in route, step by step 1. Request `https://mcp.mapbox.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mapbox.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.mapbox.com/oauth/register?scope=styles%3Atiles%20styles%3Aread%20fonts%3Aread%20datasets%3Aread%20tokens%3Aread` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mapbox. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mapbox-com/index.md) ## Sources - [Ora score page for mapbox.com](https://ora.ai/score/mapbox.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/score) - [Where Mapbox was found](https://github.com/mcp/mapbox/mcp-server), read 4 November 2026 - [Mapbox website](https://mapbox.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MAQAMI MCP server | Agent MCP Directory" description: "MAQAMI has an open MCP server with 41 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/maqami-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MAQAMI MCP server | Agent MCP Directory > MAQAMI has an open MCP server with 41 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/maqami-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # MAQAMI: MCP server, CLI and agent surfaces Yes: MAQAMI runs a public MCP server at mcp.maqami.co that listed 41 tools to a client with no credentials on 4 November 2026. Examples: get\_prebooks\_prebookid, post\_rates\_prebook, listBookings. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | MAQAMI (registry title: MAQAMI Travel) | | --- | --- | | Domain | maqami.co | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for maqami.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.maqami.co/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | MAQAMI Travel MCP Server 1.0.9 | | Capabilities | tools | | Tools | 41 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,523 ms over 1 attempt | ### Tools listed 41 tools; the first 40 names are recorded - get\_prebooks\_prebookid - post\_rates\_prebook - listBookings - get\_bookings\_bookingid - cancel\_hotel\_booking - put\_bookings\_bookingid\_amend - post\_bookings\_bookingid\_alternative\_prebooks - getExperienceBooking - getExperienceBookingCancelPreview - cancelExperienceBooking - get\_data\_flights\_airlines\_iatas\_iatacode - get\_data\_flights\_airports\_iatas\_iatacode - get\_data\_flights\_airports\_iatas - post\_flights\_rates - post\_flights\_verify - get\_flights\_bookings\_bookingid - get\_flights\_bookings\_bookingid\_services - get\_flights\_bookings\_bookingid\_cancellations - post\_flights\_bookings\_bookingid\_cancellations - get\_data\_flights\_airlines - get\_data\_flights\_airlines\_iatas - get\_data\_flights\_airports - post\_hotels\_rates - post\_hotels\_min\_rates - getHotelTaxSchema - get\_data\_hotels - get\_data\_hotels\_semantic\_search - get\_data\_hotel\_ask - post\_data\_hotel\_highlights - get\_data\_hotels\_room\_search - get\_data\_hotel - get\_data\_reviews - get\_data\_cities - get\_data\_countries - get\_data\_currencies - get\_data\_iatacodes - get\_data\_facilities - get\_data\_hoteltypes - get\_data\_chains - get\_data\_languages ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:21Z https://mcp.maqami.co/ sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2703 ms - 20:03:36Z https://mcp.maqami.co/ sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1523 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.maqami.co/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for MAQAMI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Yes: ahmednegm-1711/maqami-travel | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/maqami-co/index.md) ## Sources - [MAQAMI website](https://maqami.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Market Eyes Live MCP server | Agent MCP Directory" description: "Market Eyes Live has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/marketeyeslive-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Market Eyes Live MCP server | Agent MCP Directory > Market Eyes Live has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/marketeyeslive-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Market Eyes Live: MCP server, CLI and agent surfaces Yes: Market Eyes Live runs a public MCP server at marketeyeslive.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: get\_stock\_rating, compare\_stocks, get\_mortgage\_rate\_context. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Market Eyes Live (registry title: Market Eyes Live - stock ratings and mortgage-rate context) | | --- | --- | | Domain | marketeyeslive.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for marketeyeslive.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://marketeyeslive.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | market-eyes-live 1.4.0 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,651 ms over 1 attempt | ### Tools listed 3 tools - get\_stock\_rating - compare\_stocks - get\_mortgage\_rate\_context ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:21Z https://marketeyeslive.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2399 ms - 20:03:37Z https://marketeyeslive.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1651 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://marketeyeslive.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Market Eyes Live. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/marketeyeslive-com/index.md) ## Sources - [Market Eyes Live website](https://marketeyeslive.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Massdriver MCP server | Agent MCP Directory" description: "Does Massdriver have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/massdriver-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Massdriver MCP server | Agent MCP Directory > Does Massdriver have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/massdriver-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # Massdriver: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Massdriver (massdriver.cloud), so the connector had nothing to connect to. Ora's cached score for massdriver.cloud is 63, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Massdriver (registry title: massdriver.cloud) | | --- | --- | | Domain | massdriver.cloud | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for massdriver.cloud, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Massdriver. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for massdriver.cloud, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Massdriver. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/massdriver-cloud/index.md) ## Sources - [Ora score page for massdriver.cloud](https://ora.ai/score/massdriver.cloud?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Massdriver was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Massdriver website](https://massdriver.cloud), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mastra MCP server | Agent MCP Directory" description: "Does Mastra have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mastra-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mastra MCP server | Agent MCP Directory > Does Mastra have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mastra-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mastra: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Mastra (mastra.ai), so the connector had nothing to connect to. Ora's cached score for mastra.ai is 78, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Mastra (registry title: mastra.ai) | | --- | --- | | Domain | mastra.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 78, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mastra.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Mastra. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mastra.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Mastra. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mastra-ai/index.md) ## Sources - [Ora score page for mastra.ai](https://ora.ai/score/mastra.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Mastra was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mastra website](https://mastra.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP Telegram server | Agent MCP Directory" description: "MCP Telegram: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/mcp-telegram-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MCP Telegram server | Agent MCP Directory > MCP Telegram: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/mcp-telegram-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP Telegram: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for MCP Telegram at mcp.mcp-telegram.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | MCP Telegram (registry title: Chatroost: unofficial Telegram MCP server) | | --- | --- | | Domain | mcp-telegram.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for mcp-telegram.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mcp-telegram.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 479 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:20Z https://mcp.mcp-telegram.com/mcp sent initialize result auth-required (HTTP 401) 624 ms - 20:03:36Z https://mcp.mcp-telegram.com/mcp sent initialize result auth-required (HTTP 401) 479 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.mcp-telegram.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.mcp-telegram.com | | Authorization server metadata | mcp.mcp-telegram.com | | Registration endpoint | https://mcp.mcp-telegram.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.mcp-telegram.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mcp-telegram.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.mcp-telegram.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for MCP Telegram. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mcp-telegram-com/index.md) ## Sources - [Where MCP Telegram was found](https://github.com/mcp/mcp-telegram/mcp-telegram), read 4 November 2026 - [MCP Telegram website](https://mcp-telegram.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MCPEmails MCP server | Agent MCP Directory" description: "MCPEmails: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce." canonical: https://agentmcpdirectory.com/directory/mcpemails-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MCPEmails MCP server | Agent MCP Directory > MCPEmails: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce. Source: https://agentmcpdirectory.com/directory/mcpemails-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCPEmails: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for MCPEmails at mcpemails.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | MCPEmails | | --- | --- | | Domain | mcpemails.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for mcpemails.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcpemails.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 753 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:21Z https://mcpemails.com/api/mcp sent initialize result auth-required (HTTP 401) 1254 ms - 20:03:37Z https://mcpemails.com/api/mcp sent initialize result auth-required (HTTP 401) 753 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="MCPEmails", resource_metadata="https://mcpemails.com/.well-known/oauth-protected-resource", scope="read:email" | | Protected resource metadata | mcpemails.com | | Authorization server metadata | mcpemails.com | | Registration endpoint | https://mcpemails.com/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcpemails.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcpemails.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcpemails.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for MCPEmails. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mcpemails/emails | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mcpemails-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mcpemails), read 4 November 2026 - [MCPEmails website](https://mcpemails.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "mcprush.com MCP server | Agent MCP Directory" description: "mcprush.com: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/mcprush-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # mcprush.com MCP server | Agent MCP Directory > mcprush.com: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/mcprush-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # mcprush.com: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for mcprush.com at mcprush.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | mcprush.com (registry title: mcprush.com - Catalogue MCP) | | --- | --- | | Domain | mcprush.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for mcprush.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcprush.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 638 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:21Z https://mcprush.com/mcp sent initialize result auth-required (HTTP 401) 897 ms - 20:03:37Z https://mcprush.com/mcp sent initialize result auth-required (HTTP 401) 638 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcprush", resource_metadata="https://mcprush.com/.well-known/oauth-protected-resource", scope="catalogue" | | Protected resource metadata | mcprush.com | | Authorization server metadata | mcprush.com | | Registration endpoint | https://mcprush.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcprush.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcprush.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcprush.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for mcprush.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mcprush/catalogue | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mcprush-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mcprush), read 4 November 2026 - [mcprush.com website](https://mcprush.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Measuremy MCP server | Agent MCP Directory" description: "Measuremy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/measuremy-site site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Measuremy MCP server | Agent MCP Directory > Measuremy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/measuremy-site Site: Agent MCP Directory Last reviewed: 2026-11-05 # Measuremy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Measuremy at a.measuremy.site answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Measuremy (registry title: measuremy.site) | | --- | --- | | Domain | measuremy.site | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for measuremy.site when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://a.measuremy.site/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 218 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:21Z https://a.measuremy.site/mcp sent initialize result auth-required (HTTP 401) 754 ms - 20:03:37Z https://a.measuremy.site/mcp sent initialize result auth-required (HTTP 401) 218 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://a.measuremy.site/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | a.measuremy.site | | Authorization server metadata | measuremy.site | | Registration endpoint | https://measuremy.site/oauth/register | ### The sign-in route, step by step 1. Request `https://a.measuremy.site/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://a.measuremy.site/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://measuremy.site/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Measuremy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/measuremy-site/index.md) ## Sources - [Measuremy website](https://measuremy.site), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mediawork MCP server | Agent MCP Directory" description: "Mediawork has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mediawork-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mediawork MCP server | Agent MCP Directory > Mediawork has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mediawork-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mediawork: MCP server, CLI and agent surfaces Yes: Mediawork runs a public MCP server at mcp.mediawork.io that listed 10 tools to a client with no credentials on 4 November 2026. Examples: list\_services, list\_places, search\_facilities. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Mediawork | | --- | --- | | Domain | mediawork.io | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for mediawork.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mediawork.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | mediawork 0.1.0 | | Capabilities | tools | | Tools | 10 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 905 ms over 1 attempt | ### Tools listed 10 tools - list\_services - list\_places - search\_facilities - get\_facility - search\_faq - list\_blog\_posts - get\_blog\_post - get\_plans - search - fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:22Z https://mcp.mediawork.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1017 ms - 20:03:37Z https://mcp.mediawork.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 905 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.mediawork.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mediawork. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mediawork-io/index.md) ## Sources - [Mediawork website](https://mediawork.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MedicalNewsToday MCP server | Agent MCP Directory" description: "Does MedicalNewsToday have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/medicalnewstoday-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MedicalNewsToday MCP server | Agent MCP Directory > Does MedicalNewsToday have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/medicalnewstoday-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MedicalNewsToday: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for MedicalNewsToday (medicalnewstoday.com), so the connector had nothing to connect to. Ora's cached score for medicalnewstoday.com is 75, grade B, read on 5 November 2026. The company was added from the shared crawl, which found /.well-known/mcp.json on the domain. ## Fact sheet | Company | MedicalNewsToday (registry title: medicalnewstoday.com) | | --- | --- | | Domain | medicalnewstoday.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | None found | | Tranco rank | 2,308 on the list of 4 November 2026 | | Ora score | 75, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for medicalnewstoday.com, a vendor-published score) | | Company found through | the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for MedicalNewsToday. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for medicalnewstoday.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for MedicalNewsToday. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card (older path) | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/medicalnewstoday-com/index.md) ## Sources - [Ora score page for medicalnewstoday.com](https://ora.ai/score/medicalnewstoday.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Where MedicalNewsToday was found](https://medicalnewstoday.com/.well-known/mcp.json), read 4 November 2026 - [MedicalNewsToday website](https://medicalnewstoday.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Medplum MCP server | Agent MCP Directory" description: "Medplum: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Healthcare." canonical: https://agentmcpdirectory.com/directory/medplum-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Medplum MCP server | Agent MCP Directory > Medplum: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Healthcare. Source: https://agentmcpdirectory.com/directory/medplum-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Medplum: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Medplum at api.medplum.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Medplum (registry title: medplum.com) | | --- | --- | | Domain | medplum.com | | Category | Healthcare (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 43, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for medplum.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.medplum.com/mcp/stream | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,313 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:23Z https://api.medplum.com/mcp/stream sent initialize result auth-required (HTTP 401) 1390 ms - 20:03:38Z https://api.medplum.com/mcp/stream sent initialize result auth-required (HTTP 401) 1313 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://api.medplum.com/" | | Protected resource metadata | api.medplum.com | | Authorization server metadata | api.medplum.com | | Registration endpoint | https://api.medplum.com/oauth2/register | ### The sign-in route, step by step 1. Request `https://api.medplum.com/mcp/stream` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.medplum.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.medplum.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Medplum. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.medplum/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/medplum-com/index.md) ## Sources - [Ora score page for medplum.com](https://ora.ai/score/medplum.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Medplum was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.medplum%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=medplum), read 4 November 2026 - [Medplum website](https://medplum.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Medusa MCP server | Agent MCP Directory" description: "Medusa: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/medusajs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Medusa MCP server | Agent MCP Directory > Medusa: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/medusajs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Medusa: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Medusa at docs.medusajs.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Medusa | | --- | --- | | Domain | medusajs.com | | Category | Commerce Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 73, grade B; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for medusajs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://docs.medusajs.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 826 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:23Z https://docs.medusajs.com/mcp sent initialize result auth-required (HTTP 401) 2135 ms - 20:03:38Z https://docs.medusajs.com/mcp sent initialize result auth-required (HTTP 401) 826 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="medusa", resource_metadata="https://docs.medusajs.com/.well-known/oauth-protected-resource" | | Protected resource metadata | docs.medusajs.com | | Authorization server metadata | cloud.medusajs.com | | Registration endpoint | https://api.prod.medusajs.cloud/v1/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://docs.medusajs.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://docs.medusajs.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.prod.medusajs.cloud/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Medusa. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.medusajs/cloud, com.medusajs/medusa-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/medusajs-com/index.md) ## Sources - [Ora score page for medusajs.com](https://ora.ai/score/medusajs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where Medusa was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.medusajs%2Fcloud), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=medusajs), read 4 November 2026 - [Medusa website](https://medusajs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mellow Hub MCP server | Agent MCP Directory" description: "Mellow Hub: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/mellow-world site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mellow Hub MCP server | Agent MCP Directory > Mellow Hub: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/mellow-world Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mellow Hub: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mellow Hub at www.mellow.world answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mellow Hub | | --- | --- | | Domain | mellow.world | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for mellow.world when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.mellow.world/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,493 ms over 2 attempts | | Result | initialize error: Header mismatch: MCP-Protocol-Version header is required. | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:23Z https://www.mellow.world/mcp sent initialize, initialize result auth-required (HTTP 401) 1430 ms - 20:03:39Z https://www.mellow.world/mcp sent initialize, initialize result auth-required (HTTP 401) 1493 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Mellow Hub", resource_metadata="https://www.mellow.world/.well-known/oauth-protected-resource", scope="channels:read channels:connect media:write posts:read posts:write posts:publish metrics:read" | | Protected resource metadata | www.mellow.world | | Authorization server metadata | www.mellow.world | | Registration endpoint | https://www.mellow.world/api/hub/oauth/register | ### The sign-in route, step by step 1. Request `https://www.mellow.world/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.mellow.world/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.mellow.world/api/hub/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mellow Hub. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mellow-world/index.md) ## Sources - [Mellow Hub website](https://mellow.world), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mem MCP server | Agent MCP Directory" description: "Mem: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mem-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mem MCP server | Agent MCP Directory > Mem: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mem-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mem: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Mem; the connector's guess at mcp.mem.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mem (registry title: mem.ai) | | --- | --- | | Domain | mem.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 67, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mem.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mem.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 970 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:23Z https://mcp.mem.ai/mcp sent initialize result auth-required (HTTP 401) 908 ms - 20:03:38Z https://mcp.mem.ai/mcp sent initialize result auth-required (HTTP 401) 970 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.mem.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.mem.ai | | Authorization server metadata | api.mem.ai | | Registration endpoint | https://api.mem.ai/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.mem.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mem.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.mem.ai/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mem. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mem-ai/index.md) ## Sources - [Ora score page for mem.ai](https://ora.ai/score/mem.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Mem was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mem website](https://mem.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Memocore MCP server | Agent MCP Directory" description: "Memocore: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/memocore-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Memocore MCP server | Agent MCP Directory > Memocore: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/memocore-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Memocore: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Memocore at memocore.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Memocore | | --- | --- | | Domain | memocore.ai | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for memocore.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://memocore.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,146 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:23Z https://memocore.ai/mcp sent initialize result auth-required (HTTP 401) 1305 ms - 20:03:38Z https://memocore.ai/mcp sent initialize result auth-required (HTTP 401) 1146 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://memocore.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | memocore.ai | | Authorization server metadata | memocore.ai | | Registration endpoint | https://memocore.ai/register | ### The sign-in route, step by step 1. Request `https://memocore.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://memocore.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://memocore.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Memocore. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.memocore/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/memocore-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=memocore), read 4 November 2026 - [Memocore website](https://memocore.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Memxus MCP server | Agent MCP Directory" description: "Memxus has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/memxus-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Memxus MCP server | Agent MCP Directory > Memxus has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/memxus-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Memxus: MCP server, CLI and agent surfaces Yes: Memxus runs a public MCP server at mcp.memxus.com that listed 9 tools to a client with no credentials on 4 November 2026. Examples: remember, recall, get\_context. It speaks streamable-http, protocol 2024-11-05. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Memxus | | --- | --- | | Domain | memxus.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for memxus.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.memxus.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | memxus 1.3.2 | | Capabilities | tools, resources | | Tools | 9 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,487 ms over 1 attempt | ### Tools listed 9 tools - remember - recall - get\_context - list\_memories - get\_memory - list\_collections - forget - memory\_stats - update ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:24Z https://mcp.memxus.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1733 ms - 20:03:39Z https://mcp.memxus.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1487 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.memxus.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Memxus. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.memxus/memxus | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Yes: memxus/memxus | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/memxus-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=memxus), read 4 November 2026 - [Memxus website](https://memxus.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mendix MCP server | Agent MCP Directory" description: "Does Mendix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mendix-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mendix MCP server | Agent MCP Directory > Does Mendix have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mendix-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mendix: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Mendix (mendix.com), so the connector had nothing to connect to. Ora's cached score for mendix.com is 72, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Mendix (registry title: mendix.com) | | --- | --- | | Domain | mendix.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mendix.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Mendix. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mendix.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Mendix. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: mendix.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mendix-com/index.md) ## Sources - [Ora score page for mendix.com](https://ora.ai/score/mendix.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Mendix was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mendix website](https://mendix.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mercado Libre MCP server | Agent MCP Directory" description: "Mercado Libre has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/mercadolibre-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mercado Libre MCP server | Agent MCP Directory > Mercado Libre has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/mercadolibre-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mercado Libre: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Mercado Libre (mcp.mercadolibre.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: HTTP 200 < | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:00Z https://mcp.mercadolibre.com/mcp sent initialize result no-answer (HTTP 200) 2196 ms - 20:01:36Z https://mcp.mercadolibre.com/mcp sent initialize result no-answer (HTTP 200) 2156 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.mercadolibre.com/mcp`. The connector could not tell what it wants: HTTP 200 Mercado Pago: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/mercadopago-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mercado Pago: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mercado Pago at mcp.mercadopago.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mercado Pago (registry title: Mercado Pago MCP Server) | | --- | --- | | Domain | mercadopago.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,502 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for mercadopago.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mercadopago.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,117 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:06Z https://mcp.mercadopago.com/mcp sent initialize result auth-required (HTTP 401) 560 ms - 20:01:43Z https://mcp.mercadopago.com/mcp sent initialize result auth-required (HTTP 401) 1117 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.mercadopago.com | | Authorization server metadata | mcp.mercadopago.com | | Registration endpoint | https://mcp.mercadopago.com/oauth/register/mcp | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.mercadopago.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mercadopago.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.mercadopago.com/oauth/register/mcp` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mercado Pago. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mercadopago-com/index.md) ## Sources - [Where Mercado Pago was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Mercado Pago website](https://mercadopago.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mergent MCP server | Agent MCP Directory" description: "Does Mergent have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mergent-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mergent MCP server | Agent MCP Directory > Does Mergent have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mergent-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mergent: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Mergent (mergent.co), so the connector had nothing to connect to. Ora's cached score for mergent.co is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Mergent (registry title: mergent.co) | | --- | --- | | Domain | mergent.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mergent.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Mergent. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mergent.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Mergent. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mergent-co/index.md) ## Sources - [Ora score page for mergent.co](https://ora.ai/score/mergent.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Mergent was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mergent website](https://mergent.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mergify MCP server | Agent MCP Directory" description: "Does Mergify have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mergify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mergify MCP server | Agent MCP Directory > Does Mergify have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mergify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mergify: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Mergify (mergify.com), so the connector had nothing to connect to. Ora's cached score for mergify.com is 75, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Mergify | | --- | --- | | Domain | mergify.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 75, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mergify.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Mergify. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mergify.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Mergify. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: docs.mergify.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mergify-com/index.md) ## Sources - [Ora score page for mergify.com](https://ora.ai/score/mergify.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Mergify was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mergify website](https://mergify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Metoro MCP server | Agent MCP Directory" description: "Does Metoro have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/metoro-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Metoro MCP server | Agent MCP Directory > Does Metoro have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/metoro-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Metoro: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Metoro (metoro.io), so the connector had nothing to connect to. Ora's cached score for metoro.io is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Metoro (registry title: metoro.io) | | --- | --- | | Domain | metoro.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for metoro.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Metoro. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for metoro.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Metoro. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/metoro-io/index.md) ## Sources - [Ora score page for metoro.io](https://ora.ai/score/metoro.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Metoro was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Metoro website](https://metoro.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mezmo MCP server | Agent MCP Directory" description: "Mezmo: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/mezmo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mezmo MCP server | Agent MCP Directory > Mezmo: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/mezmo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mezmo: MCP server, CLI and agent surfaces Not counted. No source names an endpoint for Mezmo; the connector's guess at mcp.mezmo.com asked for credentials on 4 November 2026 and published no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Mezmo (registry title: mezmo.com) | | --- | --- | | Domain | mezmo.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 65, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mezmo.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mezmo.com/mcp | | --- | --- | | How it was found | mcp.mezmo.com was tried as a guess and answered; see the result below | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,261 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:25Z https://mcp.mezmo.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1180 ms - 20:03:40Z https://mcp.mezmo.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1261 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.mezmo.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mezmo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mezmo-com/index.md) ## Sources - [Ora score page for mezmo.com](https://ora.ai/score/mezmo.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/leaderboard) - [Where Mezmo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mezmo website](https://mezmo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Microsoft MCP server | Agent MCP Directory" description: "Microsoft has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/microsoft-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Microsoft MCP server | Agent MCP Directory > Microsoft has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/microsoft-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Microsoft: MCP server, CLI and agent surfaces Yes: Microsoft runs a public MCP server at learn.microsoft.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: microsoft\_docs\_search, microsoft\_code\_sample\_search, microsoft\_docs\_fetch. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for microsoft.com is 62, grade C, read on 5 November 2026. ## Fact sheet | Company | Microsoft | | --- | --- | | Domain | microsoft.com | | Category | Identity & Auth (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 9 on the list of 4 November 2026 | | Ora score | 62, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for microsoft.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://learn.microsoft.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Microsoft Learn MCP Server 1.0.0 | | Capabilities | logging, prompts, resources, tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,137 ms over 1 attempt | ### Tools listed 3 tools - microsoft\_docs\_search - microsoft\_code\_sample\_search - microsoft\_docs\_fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:52Z https://learn.microsoft.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1157 ms - 20:01:27Z https://learn.microsoft.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1137 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://learn.microsoft.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Microsoft. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.microsoft.esrp/esrp-oss-mcp-test, com.microsoft/esrp-oss-mcp-test, com.microsoft/microsoft-learn-mcp and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/microsoft-com/index.md) ## Sources - [Ora score page for microsoft.com](https://ora.ai/score/microsoft.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Where Microsoft was found](https://github.com/mcp/MicrosoftDocs/mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=microsoft), read 4 November 2026 - [Microsoft website](https://microsoft.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Middleware MCP server | Agent MCP Directory" description: "Does Middleware have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/middleware-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Middleware MCP server | Agent MCP Directory > Does Middleware have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/middleware-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Middleware: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Middleware (middleware.io), so the connector had nothing to connect to. Ora's cached score for middleware.io is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Middleware (registry title: middleware.io) | | --- | --- | | Domain | middleware.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 30 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for middleware.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Middleware. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for middleware.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Middleware. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/middleware-io/index.md) ## Sources - [Ora score page for middleware.io](https://ora.ai/score/middleware.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 September 2026, read from GET /api/leaderboard) - [Where Middleware was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Middleware website](https://middleware.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Minded MCP server | Agent MCP Directory" description: "Does Minded have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/minded-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Minded MCP server | Agent MCP Directory > Does Minded have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/minded-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Minded: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Minded (minded.com), so the connector had nothing to connect to. Ora's cached score for minded.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Minded (registry title: minded.com) | | --- | --- | | Domain | minded.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for minded.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Minded. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for minded.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Minded. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/minded-com/index.md) ## Sources - [Ora score page for minded.com](https://ora.ai/score/minded.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Where Minded was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Minded website](https://minded.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mindee MCP server | Agent MCP Directory" description: "Does Mindee have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mindee-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mindee MCP server | Agent MCP Directory > Does Mindee have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mindee-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mindee: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Mindee (mindee.com), so the connector had nothing to connect to. Ora's cached score for mindee.com is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Mindee (registry title: mindee.com) | | --- | --- | | Domain | mindee.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mindee.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Mindee. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mindee.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Mindee. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mindee-com/index.md) ## Sources - [Ora score page for mindee.com](https://ora.ai/score/mindee.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Mindee was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mindee website](https://mindee.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mindsdb MCP server | Agent MCP Directory" description: "Does Mindsdb have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mindsdb-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mindsdb MCP server | Agent MCP Directory > Does Mindsdb have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mindsdb-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mindsdb: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Mindsdb (mindsdb.com), so the connector had nothing to connect to. Ora's cached score for mindsdb.com is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Mindsdb (registry title: mindsdb.com) | | --- | --- | | Domain | mindsdb.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mindsdb.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Mindsdb. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mindsdb.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Mindsdb. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mindsdb-com/index.md) ## Sources - [Ora score page for mindsdb.com](https://ora.ai/score/mindsdb.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where Mindsdb was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mindsdb website](https://mindsdb.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Minicor MCP server | Agent MCP Directory" description: "Minicor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/minicor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Minicor MCP server | Agent MCP Directory > Minicor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/minicor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Minicor: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Minicor; the connector's guess at mcp.minicor.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Minicor (registry title: minicor.com) | | --- | --- | | Domain | minicor.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 80, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for minicor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.minicor.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 756 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:25Z https://mcp.minicor.com/mcp sent initialize result auth-required (HTTP 401) 699 ms - 20:03:40Z https://mcp.minicor.com/mcp sent initialize result auth-required (HTTP 401) 756 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="minicor-mcp", resource_metadata="https://mcp.minicor.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.minicor.com | | Authorization server metadata | mcp.minicor.com | | Registration endpoint | https://mcp.minicor.com/register | ### The sign-in route, step by step 1. Request `https://mcp.minicor.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.minicor.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.minicor.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Minicor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/minicor-com/index.md) ## Sources - [Ora score page for minicor.com](https://ora.ai/score/minicor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Minicor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Minicor website](https://minicor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MiningBridge MCP server | Agent MCP Directory" description: "MiningBridge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/miningbridge-in site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MiningBridge MCP server | Agent MCP Directory > MiningBridge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/miningbridge-in Site: Agent MCP Directory Last reviewed: 2026-11-05 # MiningBridge: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for MiningBridge at intel.miningbridge.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | MiningBridge (registry title: MiningBridge Intelligence) | | --- | --- | | Domain | miningbridge.in | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for miningbridge.in when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://intel.miningbridge.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 795 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:26Z https://intel.miningbridge.com/api/mcp sent initialize result auth-required (HTTP 401) 913 ms - 20:03:40Z https://intel.miningbridge.com/api/mcp sent initialize result auth-required (HTTP 401) 795 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://intel.miningbridge.com/.well-known/oauth-protected-resource" | | Protected resource metadata | intel.miningbridge.com | | Authorization server metadata | intel.miningbridge.com | | Registration endpoint | https://intel.miningbridge.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://intel.miningbridge.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://intel.miningbridge.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://intel.miningbridge.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for MiningBridge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: in.miningbridge/intel | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/miningbridge-in/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=miningbridge), read 4 November 2026 - [MiningBridge website](https://miningbridge.in), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mintlify MCP server | Agent MCP Directory" description: "Mintlify has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mintlify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mintlify MCP server | Agent MCP Directory > Mintlify has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mintlify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mintlify: MCP server, CLI and agent surfaces Yes: Mintlify runs a public MCP server at www.mintlify.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: search\_mintlify, query\_docs\_filesystem\_mintlify, submit\_feedback. It speaks streamable-http, protocol 2025-11-25. A CLI is on record: mint on npm. ## Fact sheet | Company | Mintlify | | --- | --- | | Domain | mintlify.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 74, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mintlify.com, a vendor-published score) | | Company found through | the vendor's own documentation; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.mintlify.com/docs/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Mintlify 1.0.0 | | Capabilities | tools, resources | | Tools | 3 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,728 ms over 1 attempt | | Documentation | mintlify.com | ### Tools listed 3 tools - search\_mintlify - query\_docs\_filesystem\_mintlify - submit\_feedback ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:27Z https://www.mintlify.com/docs/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1438 ms - 20:03:41Z https://www.mintlify.com/docs/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1728 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.mintlify.com/docs/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | mint on npm (page) | | --- | --- | | Exists | yes | | Latest version | 4.2.1201 | | Last publish | 4 November 2026 | | Command names | mint | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: mintlify.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mintlify/adminmcp, com.mintlify/searchmcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mintlify-com/index.md) ## Sources - [Mintlify MCP documentation](https://mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Ora score page for mintlify.com](https://ora.ai/score/mintlify.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mintlify), read 4 November 2026 - [Mintlify website](https://mintlify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mirabelloconsultancy MCP server | Agent MCP Directory" description: "Mirabelloconsultancy has an open MCP server with 68 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mirabelloconsultancy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mirabelloconsultancy MCP server | Agent MCP Directory > Mirabelloconsultancy has an open MCP server with 68 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mirabelloconsultancy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mirabelloconsultancy: MCP server, CLI and agent surfaces Yes: Mirabelloconsultancy runs a public MCP server at mcp.mirabelloconsultancy.com that listed 68 tools to a client with no credentials on 4 November 2026. Examples: list\_programmes, get\_programme, compare\_programmes. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Mirabelloconsultancy (registry title: Mirabello Immigration Intelligence) | | --- | --- | | Domain | mirabelloconsultancy.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for mirabelloconsultancy.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mirabelloconsultancy.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | mirabello-consultancy 1.4.3 | | Capabilities | tools, resources, prompts | | Tools | 68 | | Resources | 4 | | Prompts | 4 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 928 ms over 1 attempt | ### Tools listed 68 tools; the first 40 names are recorded - list\_programmes - get\_programme - compare\_programmes - get\_processing\_times - estimate\_total\_cost - recommend\_programmes - check\_visa\_free - get\_index - get\_recent\_changes - get\_about - get\_passport\_renewal - get\_malta\_citizen\_service - estimate\_malta\_passport\_fee - check\_maltese\_citizenship\_eligibility - book\_consultation - generate\_briefing - subscribe\_changes - check\_eligibility - get\_document\_checklist - estimate\_timeline - get\_country - get\_provenance - query\_graph - plan\_path - find\_pathways - find\_retirement\_routes - find\_fastest\_citizenship - get\_family\_pathway - get\_emigration\_flows - get\_capital\_controls - check\_visa\_requirement - list\_visa\_free\_destinations - get\_name\_change - get\_foundation\_rules - get\_nonresident\_banking - get\_property\_law - get\_entry\_requirements - get\_country\_tax - find\_low\_tax - find\_trust\_jurisdictions ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:27Z https://mcp.mirabelloconsultancy.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1782 ms - 20:03:40Z https://mcp.mirabelloconsultancy.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 928 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.mirabelloconsultancy.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mirabelloconsultancy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mirabelloconsultancy/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Yes: mirabelloconsultancy/investment-migration | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mirabelloconsultancy-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mirabelloconsultancy), read 4 November 2026 - [Mirabelloconsultancy website](https://mirabelloconsultancy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Miro MCP server | Agent MCP Directory" description: "Miro: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/miro-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Miro MCP server | Agent MCP Directory > Miro: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/miro-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Miro: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Miro at mcp.miro.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Miro | | --- | --- | | Domain | miro.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,165 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for miro.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.miro.com/ | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,353 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:58Z https://mcp.miro.com/ sent initialize result auth-required (HTTP 401) 497 ms - 20:01:34Z https://mcp.miro.com/ sent initialize result auth-required (HTTP 401) 1353 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.miro.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.miro.com | | Authorization server metadata | mcp.miro.com | | Registration endpoint | https://mcp.miro.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.miro.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.miro.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.miro.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Miro. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/miro-com/index.md) ## Sources - [Ora score page for miro.com](https://ora.ai/score/miro.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Miro was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Miro website](https://miro.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "mlop MCP server | Agent MCP Directory" description: "Does mlop have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/mlop-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # mlop MCP server | Agent MCP Directory > Does mlop have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/mlop-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # mlop: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for mlop (mlop.ai), so the connector had nothing to connect to. Ora's cached score for mlop.ai is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | mlop (registry title: mlop.ai) | | --- | --- | | Domain | mlop.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 4 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mlop.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for mlop. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mlop.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for mlop. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mlop-ai/index.md) ## Sources - [Ora score page for mlop.ai](https://ora.ai/score/mlop.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 October 2026, read from GET /api/leaderboard) - [Where mlop was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [mlop website](https://mlop.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mnemoverse MCP server | Agent MCP Directory" description: "Mnemoverse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/mnemoverse-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mnemoverse MCP server | Agent MCP Directory > Mnemoverse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/mnemoverse-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mnemoverse: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mnemoverse at mcp.mnemoverse.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mnemoverse (registry title: Mnemoverse Memory) | | --- | --- | | Domain | mnemoverse.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for mnemoverse.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mnemoverse.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 662 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:27Z https://mcp.mnemoverse.com/mcp sent initialize result auth-required (HTTP 401) 1117 ms - 20:03:40Z https://mcp.mnemoverse.com/mcp sent initialize result auth-required (HTTP 401) 662 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="Missing bearer token", resource_metadata="https://mcp.mnemoverse.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.mnemoverse.com | | Authorization server metadata | auth.mnemoverse.com | | Registration endpoint | https://auth.mnemoverse.com/api/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.mnemoverse.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mnemoverse.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.mnemoverse.com/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mnemoverse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mnemoverse-com/index.md) ## Sources - [Where Mnemoverse was found](https://github.com/mcp/mnemoverse/mcp-memory-server), read 4 November 2026 - [Mnemoverse website](https://mnemoverse.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MnogoReels MCP server | Agent MCP Directory" description: "MnogoReels has an open MCP server with 19 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mnogo-reels-ru site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MnogoReels MCP server | Agent MCP Directory > MnogoReels has an open MCP server with 19 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mnogo-reels-ru Site: Agent MCP Directory Last reviewed: 2026-11-05 # MnogoReels: MCP server, CLI and agent surfaces Yes: MnogoReels runs a public MCP server at mcp.mnogo-reels.ru that listed 19 tools to a client with no credentials on 4 November 2026. Examples: get\_account, get\_options\_guide, check\_video\_source. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | MnogoReels | | --- | --- | | Domain | mnogo-reels.ru | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for mnogo-reels.ru when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mnogo-reels.ru/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | mnogoreels 1.0.1 | | Capabilities | tools, prompts, resources, completions | | Tools | 19 | | Resources | 3 | | Prompts | 5 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,031 ms over 1 attempt | ### Tools listed 19 tools - get\_account - get\_options\_guide - check\_video\_source - quote\_clip\_job - create\_clip\_job - get\_clip\_job - list\_clip\_jobs - recut\_clip\_job - retry\_clip\_job - create\_transcription - get\_transcription - create\_article - get\_article - search\_broll - get\_broll\_asset - list\_packs - get\_pack - create\_youtube\_thumbnails - get\_youtube\_thumbnails ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:27Z https://mcp.mnogo-reels.ru/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1245 ms - 20:03:41Z https://mcp.mnogo-reels.ru/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1031 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.mnogo-reels.ru/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for MnogoReels. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mnogo-reels-ru/index.md) ## Sources - [MnogoReels website](https://mnogo-reels.ru), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mobbin MCP server | Agent MCP Directory" description: "Mobbin: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mobbin-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mobbin MCP server | Agent MCP Directory > Mobbin: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mobbin-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mobbin: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mobbin at api.mobbin.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mobbin | | --- | --- | | Domain | mobbin.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 83, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mobbin.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.mobbin.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 896 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:27Z https://api.mobbin.com/mcp sent initialize result auth-required (HTTP 401) 941 ms - 20:03:41Z https://api.mobbin.com/mcp sent initialize result auth-required (HTTP 401) 896 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.mobbin.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.mobbin.com | | Authorization server metadata | ujasntkfphywizsdaapi.supabase.co | | Registration endpoint | https://ujasntkfphywizsdaapi.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://api.mobbin.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.mobbin.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://ujasntkfphywizsdaapi.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mobbin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mobbin/mobbin | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mobbin-com/index.md) ## Sources - [Ora score page for mobbin.com](https://ora.ai/score/mobbin.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mobbin), read 4 November 2026 - [Mobbin website](https://mobbin.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MobileBoost MCP server | Agent MCP Directory" description: "Does MobileBoost have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mobileboost-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MobileBoost MCP server | Agent MCP Directory > Does MobileBoost have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mobileboost-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # MobileBoost: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for MobileBoost (mobileboost.io), so the connector had nothing to connect to. Ora's cached score for mobileboost.io is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | MobileBoost (registry title: mobileboost.io) | | --- | --- | | Domain | mobileboost.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mobileboost.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for MobileBoost. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mobileboost.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for MobileBoost. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mobileboost-io/index.md) ## Sources - [Ora score page for mobileboost.io](https://ora.ai/score/mobileboost.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where MobileBoost was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [MobileBoost website](https://mobileboost.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Moda MCP server | Agent MCP Directory" description: "Does Moda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/moda-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Moda MCP server | Agent MCP Directory > Does Moda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/moda-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Moda: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Moda (moda.dev), so the connector had nothing to connect to. Ora's cached score for moda.dev is 85, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Moda (registry title: moda.dev) | | --- | --- | | Domain | moda.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 85, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for moda.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Moda. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for moda.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Moda. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: moda.dev/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/moda-dev/index.md) ## Sources - [Ora score page for moda.dev](https://ora.ai/score/moda.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Moda was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Moda website](https://moda.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Modal MCP server | Agent MCP Directory" description: "Does Modal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/modal-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Modal MCP server | Agent MCP Directory > Does Modal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/modal-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Modal: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Modal (modal.com), so the connector had nothing to connect to. A CLI is on record: modal on pypi. Ora's cached score for modal.com is 63, grade C, read on 5 November 2026. ## Fact sheet | Company | Modal | | --- | --- | | Domain | modal.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for modal.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Modal. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for modal.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | modal on pypi (page) | | --- | --- | | Exists | yes | | Latest version | 1.6.3 | | Last publish | 27 October 2026 | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/modal-com/index.md) ## Sources - [modal on pypi](https://pypi.org/project/modal/), read 4 November 2026 - [Ora score page for modal.com](https://ora.ai/score/modal.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where Modal was found](https://modal.com/docs/guide), read 4 November 2026 - [Modal website](https://modal.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Modelence MCP server | Agent MCP Directory" description: "Does Modelence have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/modelence-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Modelence MCP server | Agent MCP Directory > Does Modelence have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/modelence-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Modelence: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Modelence (modelence.com), so the connector had nothing to connect to. Ora's cached score for modelence.com is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Modelence (registry title: modelence.com) | | --- | --- | | Domain | modelence.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for modelence.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Modelence. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for modelence.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Modelence. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/modelence-com/index.md) ## Sources - [Ora score page for modelence.com](https://ora.ai/score/modelence.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Modelence was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Modelence website](https://modelence.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Momentic MCP server | Agent MCP Directory" description: "Momentic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/momentic-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Momentic MCP server | Agent MCP Directory > Momentic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/momentic-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Momentic: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Momentic at mcp.momentic.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Momentic | | --- | --- | | Domain | momentic.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 83, grade B; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for momentic.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.momentic.ai | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,139 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:29Z https://mcp.momentic.ai sent initialize result auth-required (HTTP 401) 1622 ms - 20:03:42Z https://mcp.momentic.ai sent initialize result auth-required (HTTP 401) 1139 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.momentic.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.momentic.ai | | Authorization server metadata | auth.momentic.ai | | Registration endpoint | https://auth.momentic.ai/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.momentic.ai` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.momentic.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.momentic.ai/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Momentic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.momentic/momentic | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/momentic-ai/index.md) ## Sources - [Ora score page for momentic.ai](https://ora.ai/score/momentic.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Momentic was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.momentic%2Fmomentic), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=momentic), read 4 November 2026 - [Momentic website](https://momentic.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "monday MCP server | Agent MCP Directory" description: "monday: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/monday-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # monday MCP server | Agent MCP Directory > monday: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/monday-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # monday: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for monday at mcp.monday.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | monday (registry title: monday MCP) | | --- | --- | | Domain | monday.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,206 on the list of 4 November 2026 | | Ora score | 91, grade A; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for monday.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.monday.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 567 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:02Z https://mcp.monday.com/mcp sent initialize result auth-required (HTTP 401) 908 ms - 20:01:37Z https://mcp.monday.com/mcp sent initialize result auth-required (HTTP 401) 567 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.monday.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.monday.com | | Authorization server metadata | auth.monday.com | | Registration endpoint | https://auth.monday.com/oauth_ms/oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.monday.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.monday.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.monday.com/oauth_ms/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for monday. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: monday.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: monday.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | OAuth authorization server metadata | Found: monday.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.monday/monday.com | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/monday-com/index.md) ## Sources - [Ora score page for monday.com](https://ora.ai/score/monday.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Where monday was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=monday), read 4 November 2026 - [monday website](https://monday.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MongoDB MCP server | Agent MCP Directory" description: "Does MongoDB have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mongodb-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MongoDB MCP server | Agent MCP Directory > Does MongoDB have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mongodb-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MongoDB: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for MongoDB (mongodb.com), so the connector had nothing to connect to. Ora's cached score for mongodb.com is 78, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | MongoDB | | --- | --- | | Domain | mongodb.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 1,999 on the list of 4 November 2026 | | Ora score | 78, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mongodb.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for MongoDB. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mongodb.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for MongoDB. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mongodb-com/index.md) ## Sources - [Ora score page for mongodb.com](https://ora.ai/score/mongodb.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where MongoDB was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [MongoDB website](https://mongodb.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Moogsoft MCP server | Agent MCP Directory" description: "Does Moogsoft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/moogsoft-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Moogsoft MCP server | Agent MCP Directory > Does Moogsoft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/moogsoft-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Moogsoft: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Moogsoft (moogsoft.com), so the connector had nothing to connect to. Ora's cached score for moogsoft.com is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Moogsoft (registry title: moogsoft.com) | | --- | --- | | Domain | moogsoft.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for moogsoft.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Moogsoft. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for moogsoft.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Moogsoft. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/moogsoft-com/index.md) ## Sources - [Ora score page for moogsoft.com](https://ora.ai/score/moogsoft.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Moogsoft was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Moogsoft website](https://moogsoft.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MorningStar MCP server | Agent MCP Directory" description: "MorningStar: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: News & Intelligence." canonical: https://agentmcpdirectory.com/directory/morningstar-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MorningStar MCP server | Agent MCP Directory > MorningStar: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: News & Intelligence. Source: https://agentmcpdirectory.com/directory/morningstar-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MorningStar: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for MorningStar at mcp.morningstar.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | MorningStar | | --- | --- | | Domain | morningstar.com | | Category | News & Intelligence (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,597 on the list of 4 November 2026 | | Ora score | 47, grade D; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for morningstar.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.morningstar.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,161 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:03Z https://mcp.morningstar.com/mcp sent initialize result auth-required (HTTP 401) 1112 ms - 20:01:39Z https://mcp.morningstar.com/mcp sent initialize result auth-required (HTTP 401) 1161 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.morningstar.com | | Authorization server metadata | mcp.morningstar.com | | Registration endpoint | https://mcp.morningstar.com/oauth-issuer/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.morningstar.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.morningstar.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.morningstar.com/oauth-issuer/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for MorningStar. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: morningstar.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/morningstar-com/index.md) ## Sources - [Ora score page for morningstar.com](https://ora.ai/score/morningstar.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Where MorningStar was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [MorningStar website](https://morningstar.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Morphik MCP server | Agent MCP Directory" description: "Morphik has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/morphik-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Morphik MCP server | Agent MCP Directory > Morphik has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/morphik-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Morphik: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Morphik; the connector tried mcp.morphik.ai as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: DEPTH\_ZERO\_SELF\_SIGNED\_CERT. Ora's cached score for morphik.ai is 70, grade B, read on 5 November 2026. ## Fact sheet | Company | Morphik (registry title: morphik.ai) | | --- | --- | | Domain | morphik.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 70, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for morphik.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.morphik.ai/mcp | | --- | --- | | How it was found | mcp.morphik.ai was tried as a guess and did not answer | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 641 ms over 1 attempt | | Result | DEPTH_ZERO_SELF_SIGNED_CERT | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:28Z https://mcp.morphik.ai/mcp sent initialize result no-answer 645 ms - 20:03:42Z https://mcp.morphik.ai/mcp sent initialize result no-answer 641 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.morphik.ai/mcp`. The connector could not tell what it wants: DEPTH\_ZERO\_SELF\_SIGNED\_CERT. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Morphik. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/morphik-ai/index.md) ## Sources - [Ora score page for morphik.ai](https://ora.ai/score/morphik.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Morphik was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Morphik website](https://morphik.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Morph MCP server | Agent MCP Directory" description: "Morph has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/morphllm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Morph MCP server | Agent MCP Directory > Morph has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/morphllm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Morph: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Morph; the connector tried mcp.morphllm.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 400, GET HTTP 400 application/json). ## Fact sheet | Company | Morph (registry title: morphllm.com) | | --- | --- | | Domain | morphllm.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 82, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for morphllm.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.morphllm.com/mcp | | --- | --- | | How it was found | mcp.morphllm.com was tried as a guess and did not answer | | HTTP status | 400 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,607 ms over 2 attempts | | Result | no MCP answer (POST HTTP 400, GET HTTP 400 application/json) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:29Z https://mcp.morphllm.com/mcp sent initialize result no-answer (HTTP 400) 1608 ms - 20:03:43Z https://mcp.morphllm.com/mcp sent initialize result no-answer (HTTP 400) 1607 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.morphllm.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 400, GET HTTP 400 application/json). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Morph. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/morphllm-com/index.md) ## Sources - [Ora score page for morphllm.com](https://ora.ai/score/morphllm.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Morph was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Morph website](https://morphllm.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Moss MCP server | Agent MCP Directory" description: "Does Moss have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/moss-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Moss MCP server | Agent MCP Directory > Does Moss have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/moss-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Moss: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Moss (moss.dev), so the connector had nothing to connect to. Ora's cached score for moss.dev is 81, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Moss (registry title: moss.dev) | | --- | --- | | Domain | moss.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 81, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for moss.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Moss. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for moss.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Moss. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | Found: moss.dev/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: moss.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/moss-dev/index.md) ## Sources - [Ora score page for moss.dev](https://ora.ai/score/moss.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Moss was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Moss website](https://moss.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MotionSpec MCP server | Agent MCP Directory" description: "MotionSpec has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/motionspec-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MotionSpec MCP server | Agent MCP Directory > MotionSpec has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/motionspec-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # MotionSpec: MCP server, CLI and agent surfaces Yes: MotionSpec runs a public MCP server at api.motionspec.dev that listed 5 tools to a client with no credentials on 4 November 2026. Examples: motion\_catalog, motion\_validate, motion\_compile. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | MotionSpec (registry title: MotionSpec: web animation accessibility MCP) | | --- | --- | | Domain | motionspec.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for motionspec.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.motionspec.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | motionspec-mcp-server 1.2.12 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 180 ms over 1 attempt | ### Tools listed 5 tools - motion\_catalog - motion\_validate - motion\_compile - motion\_audit - motion\_stats ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:28Z https://api.motionspec.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 539 ms - 20:03:42Z https://api.motionspec.dev/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 180 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.motionspec.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for MotionSpec. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/motionspec-dev/index.md) ## Sources - [Where MotionSpec was found](https://github.com/mcp/MasterPlayspots/motionspec), read 4 November 2026 - [MotionSpec website](https://motionspec.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MovingLake MCP server | Agent MCP Directory" description: "Does MovingLake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/movinglake-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MovingLake MCP server | Agent MCP Directory > Does MovingLake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/movinglake-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MovingLake: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for MovingLake (movinglake.com), so the connector had nothing to connect to. Ora's cached score for movinglake.com is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | MovingLake (registry title: movinglake.com) | | --- | --- | | Domain | movinglake.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for movinglake.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for MovingLake. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for movinglake.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for MovingLake. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/movinglake-com/index.md) ## Sources - [Ora score page for movinglake.com](https://ora.ai/score/movinglake.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where MovingLake was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [MovingLake website](https://movinglake.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MuleSoft MCP server | Agent MCP Directory" description: "Does MuleSoft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mulesoft-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # MuleSoft MCP server | Agent MCP Directory > Does MuleSoft have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/mulesoft-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # MuleSoft: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for MuleSoft (mulesoft.com), so the connector had nothing to connect to. Ora's cached score for mulesoft.com is 36, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | MuleSoft | | --- | --- | | Domain | mulesoft.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 36, grade D; Ora scanned the domain on 5 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mulesoft.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for MuleSoft. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for mulesoft.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for MuleSoft. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mulesoft-com/index.md) ## Sources - [Ora score page for mulesoft.com](https://ora.ai/score/mulesoft.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 October 2026, read from GET /api/leaderboard) - [Where MuleSoft was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mural MCP server | Agent MCP Directory" description: "Mural: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mural-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mural MCP server | Agent MCP Directory > Mural: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mural-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mural: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mural at mcp-canvas.mural.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mural | | --- | --- | | Domain | mural.co | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 62, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for mural.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp-canvas.mural.co/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 946 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:30Z https://mcp-canvas.mural.co/mcp sent initialize result auth-required (HTTP 401) 1163 ms - 20:03:43Z https://mcp-canvas.mural.co/mcp sent initialize result auth-required (HTTP 401) 946 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp-canvas.mural.co/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp-canvas.mural.co | | Authorization server metadata | mcp-canvas.mural.co | | Registration endpoint | https://mcp-canvas.mural.co/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp-canvas.mural.co/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp-canvas.mural.co/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp-canvas.mural.co/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mural. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.mural/mural | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mural-co/index.md) ## Sources - [Ora score page for mural.co](https://ora.ai/score/mural.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Where Mural was found](https://registry.modelcontextprotocol.io/v0/servers?search=co.mural%2Fmural), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mural), read 4 November 2026 - [Mural website](https://mural.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mux MCP server | Agent MCP Directory" description: "Mux: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/mux-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mux MCP server | Agent MCP Directory > Mux: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/mux-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mux: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Mux at mcp.mux.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Mux (registry title: mux.com) | | --- | --- | | Domain | mux.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,854 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for mux.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.mux.com | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,184 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:03Z https://mcp.mux.com sent initialize result auth-required (HTTP 401) 821 ms - 20:01:40Z https://mcp.mux.com sent initialize result auth-required (HTTP 401) 1184 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.mux.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.mux.com | | Authorization server metadata | auth.mux.com | | Registration endpoint | https://auth.mux.com/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.mux.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.mux.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.mux.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Mux. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.mux/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mux-com/index.md) ## Sources - [Ora score page for mux.com](https://ora.ai/score/mux.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Where Mux was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.mux%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=mux), read 4 November 2026 - [Mux website](https://mux.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "mypromind MCP server | Agent MCP Directory" description: "mypromind: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/mypromind-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # mypromind MCP server | Agent MCP Directory > mypromind: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/mypromind-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # mypromind: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for mypromind at www.mypromind.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | mypromind (registry title: mypromind MCP) | | --- | --- | | Domain | mypromind.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for mypromind.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.mypromind.com/interface/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,306 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:32Z https://www.mypromind.com/interface/mcp sent initialize result auth-required (HTTP 401) 2784 ms - 20:03:44Z https://www.mypromind.com/interface/mcp sent initialize result auth-required (HTTP 401) 1306 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.mypromind.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | www.mypromind.com | | Authorization server metadata | clerk.mypromind.com | | Registration endpoint | https://clerk.mypromind.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://www.mypromind.com/interface/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.mypromind.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.mypromind.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for mypromind. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/mypromind-com/index.md) ## Sources - [Where mypromind was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [mypromind website](https://mypromind.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nameshift MCP server | Agent MCP Directory" description: "Nameshift has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/nameshift-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nameshift MCP server | Agent MCP Directory > Nameshift has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/nameshift-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nameshift: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Nameshift (api.nameshift.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 application/json; charset=utf-8). ## Fact sheet | Company | Nameshift (registry title: nameshift.com) | | --- | --- | | Domain | nameshift.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | No answer | | Tranco rank | 5,460 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for nameshift.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.nameshift.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | HTTP status | 404 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 332 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 application/json; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:07Z https://api.nameshift.com/mcp sent initialize result no-answer (HTTP 404) 324 ms - 20:01:45Z https://api.nameshift.com/mcp sent initialize result no-answer (HTTP 404) 332 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://api.nameshift.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 application/json; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Nameshift. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.nameshift/marketplace | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nameshift-com/index.md) ## Sources - [Where Nameshift was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.nameshift%2Fmarketplace), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=nameshift), read 4 November 2026 - [Nameshift website](https://nameshift.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nanonets MCP server | Agent MCP Directory" description: "Nanonets: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/nanonets-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nanonets MCP server | Agent MCP Directory > Nanonets: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/nanonets-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nanonets: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Nanonets; the connector's guess at mcp.nanonets.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Nanonets (registry title: nanonets.com) | | --- | --- | | Domain | nanonets.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 60, grade C; Ora scanned the domain on 20 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for nanonets.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.nanonets.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,670 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:31Z https://mcp.nanonets.com/mcp sent initialize result auth-required (HTTP 401) 1815 ms - 20:03:44Z https://mcp.nanonets.com/mcp sent initialize result auth-required (HTTP 401) 1670 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://mcp.nanonets.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.nanonets.com | | Authorization server metadata | mcp.nanonets.com | | Registration endpoint | https://mcp.nanonets.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.nanonets.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.nanonets.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.nanonets.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Nanonets. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nanonets-com/index.md) ## Sources - [Ora score page for nanonets.com](https://ora.ai/score/nanonets.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 August 2026, read from GET /api/leaderboard) - [Where Nanonets was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Nanonets website](https://nanonets.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nebius MCP server | Agent MCP Directory" description: "Does Nebius have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nebius-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nebius MCP server | Agent MCP Directory > Does Nebius have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/nebius-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nebius: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Nebius (nebius.com), so the connector had nothing to connect to. Ora's cached score for nebius.com is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Nebius | | --- | --- | | Domain | nebius.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for nebius.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Nebius. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for nebius.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Nebius. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nebius-com/index.md) ## Sources - [Ora score page for nebius.com](https://ora.ai/score/nebius.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Nebius was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Nebius website](https://nebius.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Needle MCP server | Agent MCP Directory" description: "Needle has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/needle-ai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Needle MCP server | Agent MCP Directory > Needle has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/needle-ai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Needle: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Needle (mcp.needle-ai.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: ENOTFOUND. The row is kept so the claim is visible and can be re-checked next edition. ## Fact sheet | Company | Needle | | --- | --- | | Domain | needle-ai.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for needle-ai.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.needle-ai.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 4 ms over 1 attempt | | Result | ENOTFOUND | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:30Z https://mcp.needle-ai.com/mcp sent initialize result no-answer 430 ms - 20:03:43Z https://mcp.needle-ai.com/mcp sent initialize result no-answer 4 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.needle-ai.com/mcp`. The connector could not tell what it wants: ENOTFOUND. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Needle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/needle-ai-com/index.md) ## Sources - [Where Needle was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Needle website](https://needle-ai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "NegativeEV MCP server | Agent MCP Directory" description: "NegativeEV has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/negativeev-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # NegativeEV MCP server | Agent MCP Directory > NegativeEV has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/negativeev-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # NegativeEV: MCP server, CLI and agent surfaces Yes: NegativeEV runs a public MCP server at negativeev.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: check\_bet, get\_slate, get\_usage. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | NegativeEV (registry title: NegativeEV bet checker) | | --- | --- | | Domain | negativeev.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for negativeev.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://negativeev.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | negativeev-bet-checker 1.4.5 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 509 ms over 1 attempt | ### Tools listed 3 tools - check\_bet - get\_slate - get\_usage ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:30Z https://negativeev.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 765 ms - 20:03:43Z https://negativeev.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 509 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://negativeev.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for NegativeEV. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: negativeev.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.negativeev/bet-checker | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/negativeev-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=negativeev), read 4 November 2026 - [NegativeEV website](https://negativeev.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Neon (neon.com) MCP server | Agent MCP Directory" description: "Neon (neon.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/neon-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Neon (neon.com) MCP server | Agent MCP Directory > Neon (neon.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/neon-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Neon: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Neon at mcp.neon.tech answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Neon | | --- | --- | | Domain | neon.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 88, grade A; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for neon.com, a vendor-published score) | | Company found through | the vendor's own documentation; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.neon.tech/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,055 ms over 1 attempt | | Documentation | neon.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:30Z https://mcp.neon.tech/mcp sent initialize result auth-required (HTTP 401) 914 ms - 20:03:44Z https://mcp.neon.tech/mcp sent initialize result auth-required (HTTP 401) 1055 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.neon.tech/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.neon.tech | | Authorization server metadata | mcp.neon.tech | | Registration endpoint | https://mcp.neon.tech/api/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.neon.tech/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.neon.tech/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.neon.tech/api/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | neonctl on npm (page) | | --- | --- | | Exists | yes | | Latest version | 8.18.0 | | Last publish | 3 November 2026 | | Command names | neon, neonctl | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: neon.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.neon/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/neon-com/index.md) ## Sources - [Neon MCP documentation](https://neon.com/docs/ai/neon-mcp-server), read 4 November 2026 - [Ora score page for neon.com](https://ora.ai/score/neon.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=neon), read 4 November 2026 - [Neon website](https://neon.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Neon (neon.tech) MCP server | Agent MCP Directory" description: "Neon (neon.tech): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/neon-tech site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Neon (neon.tech) MCP server | Agent MCP Directory > Neon (neon.tech): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/neon-tech Site: Agent MCP Directory Last reviewed: 2026-11-05 # Neon: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Neon at mcp.neon.tech answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Neon | | --- | --- | | Domain | neon.tech | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,235 on the list of 4 November 2026 | | Ora score | 88, grade A; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for neon.tech, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.neon.tech/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 864 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:04Z https://mcp.neon.tech/mcp sent initialize result auth-required (HTTP 401) 844 ms - 20:01:41Z https://mcp.neon.tech/mcp sent initialize result auth-required (HTTP 401) 864 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.neon.tech/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.neon.tech | | Authorization server metadata | mcp.neon.tech | | Registration endpoint | https://mcp.neon.tech/api/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.neon.tech/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.neon.tech/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.neon.tech/api/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Neon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: neon.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/neon-tech/index.md) ## Sources - [Ora score page for neon.tech](https://ora.ai/score/neon.tech?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/score) - [Where Neon was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Neon website](https://neon.tech), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Netdata MCP server | Agent MCP Directory" description: "Netdata: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/netdata-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Netdata MCP server | Agent MCP Directory > Netdata: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/netdata-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # Netdata: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Netdata at app.netdata.cloud asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Netdata | | --- | --- | | Domain | netdata.cloud | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for netdata.cloud when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.netdata.cloud/api/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 753 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:31Z https://app.netdata.cloud/api/v1/mcp sent initialize result auth-required-no-oauth (HTTP 401) 696 ms - 20:03:44Z https://app.netdata.cloud/api/v1/mcp sent initialize result auth-required-no-oauth (HTTP 401) 753 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://app.netdata.cloud/api/v1/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Netdata. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/netdata-cloud/index.md) ## Sources - [Netdata website](https://netdata.cloud), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Netlify MCP server | Agent MCP Directory" description: "Netlify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/netlify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Netlify MCP server | Agent MCP Directory > Netlify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/netlify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Netlify: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Netlify at netlify-mcp.netlify.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Netlify | | --- | --- | | Domain | netlify.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,927 on the list of 4 November 2026 | | Ora score | 92, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for netlify.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://netlify-mcp.netlify.app/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,695 ms over 1 attempt | | Documentation | docs.netlify.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:04Z https://netlify-mcp.netlify.app/mcp sent initialize result auth-required (HTTP 401) 1688 ms - 20:01:41Z https://netlify-mcp.netlify.app/mcp sent initialize result auth-required (HTTP 401) 1695 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="MCP Server", resource_metadata="https://netlify-mcp.netlify.app/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | netlify-mcp.netlify.app | | Authorization server metadata | netlify-mcp.netlify.app | | Registration endpoint | https://netlify-mcp.netlify.app/oauth-server/reg | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://netlify-mcp.netlify.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://netlify-mcp.netlify.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://netlify-mcp.netlify.app/oauth-server/reg` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | netlify-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 27.16.2 | | Last publish | 2 November 2026 | | Command names | ntl, netlify | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: netlify.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/netlify-com/index.md) ## Sources - [Netlify MCP documentation](https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/), read 4 November 2026 - [Ora score page for netlify.com](https://ora.ai/score/netlify.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Netlify website](https://netlify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Neuronto MCP server | Agent MCP Directory" description: "Neuronto has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/neuronto-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Neuronto MCP server | Agent MCP Directory > Neuronto has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/neuronto-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Neuronto: MCP server, CLI and agent surfaces Yes: Neuronto runs a public MCP server at neuronto.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: find\_resource, find\_tool, publish\_resource. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Neuronto (registry title: Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index) | | --- | --- | | Domain | neuronto.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for neuronto.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://neuronto.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | neuronto 1.0.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 704 ms over 1 attempt | ### Tools listed 4 tools - find\_resource - find\_tool - publish\_resource - registry\_stats ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:31Z https://neuronto.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 673 ms - 20:03:44Z https://neuronto.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 704 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://neuronto.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Neuronto. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: neuronto.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.neuronto/agents-tools-search-discovery-ard-registry, com.neuronto/x402-payments-facilitator | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/neuronto-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=neuronto), read 4 November 2026 - [Neuronto website](https://neuronto.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nevercode MCP server | Agent MCP Directory" description: "Does Nevercode have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nevercode-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nevercode MCP server | Agent MCP Directory > Does Nevercode have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/nevercode-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nevercode: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Nevercode (nevercode.io), so the connector had nothing to connect to. Ora's cached score for nevercode.io is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Nevercode (registry title: nevercode.io) | | --- | --- | | Domain | nevercode.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for nevercode.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Nevercode. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for nevercode.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Nevercode. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nevercode-io/index.md) ## Sources - [Ora score page for nevercode.io](https://ora.ai/score/nevercode.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Nevercode was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Nevercode website](https://nevercode.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "New Relic MCP server | Agent MCP Directory" description: "New Relic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/newrelic-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # New Relic MCP server | Agent MCP Directory > New Relic: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/newrelic-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # New Relic: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for New Relic at mcp.newrelic.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | New Relic (registry title: New Relic MCP Server) | | --- | --- | | Domain | newrelic.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 594 on the list of 4 November 2026 | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for newrelic.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.newrelic.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,516 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://mcp.newrelic.com/mcp sent initialize result auth-required (HTTP 401) 1431 ms - 20:01:31Z https://mcp.newrelic.com/mcp sent initialize result auth-required (HTTP 401) 1516 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="New Relic MCP", resource_metadata="https://mcp.newrelic.com/.well-known/oauth-protected-resource", scope="observability:read offline offline_access" | | Protected resource metadata | mcp.newrelic.com | | Authorization server metadata | oauth2.service.newrelic.com | | Registration endpoint | https://dcr.service.newrelic.com/register | ### The sign-in route, step by step 1. Request `https://mcp.newrelic.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.newrelic.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://dcr.service.newrelic.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for New Relic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.newrelic/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/newrelic-com/index.md) ## Sources - [Ora score page for newrelic.com](https://ora.ai/score/newrelic.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where New Relic was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.newrelic%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=newrelic), read 4 November 2026 - [New Relic website](https://newrelic.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "NewsCatcher MCP server | Agent MCP Directory" description: "NewsCatcher has an open MCP server with 61 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/newscatcherapi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # NewsCatcher MCP server | Agent MCP Directory > NewsCatcher has an open MCP server with 61 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/newscatcherapi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # NewsCatcher: MCP server, CLI and agent surfaces Yes: NewsCatcher runs a public MCP server at catchall-mcp.newscatcherapi.com that listed 61 tools to a client with no credentials on 4 November 2026. Examples: submit\_query, initialize\_query, get\_job\_status. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for newscatcherapi.com is 63, grade C, read on 5 November 2026. ## Fact sheet | Company | NewsCatcher (registry title: CatchAll) | | --- | --- | | Domain | newscatcherapi.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 63, grade C; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for newscatcherapi.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://catchall-mcp.newscatcherapi.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Newscatcher CatchAll API 4.1.3 | | Capabilities | logging, prompts, resources, tools | | Tools | 61 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 4,442 ms over 1 attempt | ### Tools listed 61 tools; the first 40 names are recorded - submit\_query - initialize\_query - get\_job\_status - pull\_results - pull\_job\_csv - continue\_job - list\_user\_jobs - delete\_job - validate\_query - list\_source\_groups - create\_monitor - list\_monitors - pull\_monitor\_results - pull\_monitor\_csv - list\_monitor\_jobs - disable\_monitor - enable\_monitor - update\_monitor - delete\_monitor - get\_monitor\_status - list\_webhooks - create\_webhook - get\_webhook - update\_webhook - delete\_webhook - test\_webhook - assign\_webhook\_resource - list\_webhook\_resources - remove\_webhook\_resource - list\_resource\_webhooks - get\_webhook\_history - trigger\_webhook - create\_dataset - list\_datasets - get\_dataset - update\_dataset - delete\_dataset - add\_dataset\_entities - remove\_dataset\_entities - list\_dataset\_entities ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:36Z https://catchall-mcp.newscatcherapi.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 5022 ms - 20:03:48Z https://catchall-mcp.newscatcherapi.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 4442 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://catchall-mcp.newscatcherapi.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for NewsCatcher. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.newscatcherapi/catchall | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/newscatcherapi-com/index.md) ## Sources - [Ora score page for newscatcherapi.com](https://ora.ai/score/newscatcherapi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/score) - [Where NewsCatcher was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.newscatcherapi%2Fcatchall), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=newscatcherapi), read 4 November 2026 - [NewsCatcher website](https://newscatcherapi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nginx MCP server | Agent MCP Directory" description: "Does Nginx have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nginx-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nginx MCP server | Agent MCP Directory > Does Nginx have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/nginx-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nginx: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Nginx (nginx.com), so the connector had nothing to connect to. Ora's cached score for nginx.com is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Nginx | | --- | --- | | Domain | nginx.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 103 on the list of 4 November 2026 | | Ora score | 47, grade D; Ora scanned the domain on 22 July 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for nginx.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Nginx. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for nginx.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Nginx. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nginx-com/index.md) ## Sources - [Ora score page for nginx.com](https://ora.ai/score/nginx.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 July 2026, read from GET /api/score) - [Where Nginx was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Nginx website](https://nginx.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ngrok MCP server | Agent MCP Directory" description: "ngrok: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ngrok-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ngrok MCP server | Agent MCP Directory > ngrok: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ngrok-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ngrok: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ngrok at mcp.ngrok.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ngrok | | --- | --- | | Domain | ngrok.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 7,252 on the list of 4 November 2026 | | Ora score | 90, grade A; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ngrok.com, a vendor-published score) | | Company found through | the vendor's own documentation; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.ngrok.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,719 ms over 1 attempt | | Documentation | ngrok.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:13Z https://mcp.ngrok.com/mcp sent initialize result auth-required (HTTP 401) 1551 ms - 20:01:52Z https://mcp.ngrok.com/mcp sent initialize result auth-required (HTTP 401) 1719 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.ngrok.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.ngrok.com | | Authorization server metadata | login.ngrok.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.ngrok.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.ngrok.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | ngrok on npm (page) | | --- | --- | | Exists | yes | | Latest version | 5.0.0-beta.2 | | Last publish | 7 May 2023 | | Command names | ngrok | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: ngrok.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: ngrok.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.ngrok/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ngrok-com/index.md) ## Sources - [ngrok MCP documentation](https://ngrok.com/docs/agent/cli/), read 4 November 2026 - [Ora score page for ngrok.com](https://ora.ai/score/ngrok.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ngrok), read 4 November 2026 - [ngrok website](https://ngrok.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nimble MCP server | Agent MCP Directory" description: "Nimble: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nimble-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nimble MCP server | Agent MCP Directory > Nimble: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/nimble-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nimble: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Nimble at app.nimble.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Nimble (registry title: Nimble CRM) | | --- | --- | | Domain | nimble.com | | Category | CRM (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 40, grade D; Ora scanned the domain on 20 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for nimble.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.nimble.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,265 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:33Z https://app.nimble.com/mcp sent initialize result auth-required (HTTP 401) 1797 ms - 20:03:45Z https://app.nimble.com/mcp sent initialize result auth-required (HTTP 401) 1265 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://app.nimble.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | app.nimble.com | | Authorization server metadata | app.nimble.com | | Registration endpoint | https://app.nimble.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://app.nimble.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.nimble.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.nimble.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Nimble. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.nimble.app/nimble-crm | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nimble-com/index.md) ## Sources - [Ora score page for nimble.com](https://ora.ai/score/nimble.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 August 2026, read from GET /api/leaderboard) - [Where Nimble was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.nimble.app%2Fnimble-crm), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=nimble), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nitrosend MCP server | Agent MCP Directory" description: "Nitrosend: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/nitrosend-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nitrosend MCP server | Agent MCP Directory > Nitrosend: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/nitrosend-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nitrosend: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Nitrosend at api.nitrosend.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Nitrosend | | --- | --- | | Domain | nitrosend.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 74, grade B; Ora scanned the domain on 29 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for nitrosend.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.nitrosend.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 625 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:33Z https://api.nitrosend.com/mcp sent initialize result auth-required (HTTP 401) 1120 ms - 20:03:45Z https://api.nitrosend.com/mcp sent initialize result auth-required (HTTP 401) 625 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.nitrosend.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.nitrosend.com | | Authorization server metadata | api.nitrosend.com | | Registration endpoint | https://api.nitrosend.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.nitrosend.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.nitrosend.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.nitrosend.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Nitrosend. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.nitrosend/nitrosend | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nitrosend-com/index.md) ## Sources - [Ora score page for nitrosend.com](https://ora.ai/score/nitrosend.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=nitrosend), read 4 November 2026 - [Nitrosend website](https://nitrosend.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Noloco MCP server | Agent MCP Directory" description: "Does Noloco have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/noloco-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Noloco MCP server | Agent MCP Directory > Does Noloco have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/noloco-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Noloco: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Noloco (noloco.io), so the connector had nothing to connect to. Ora's cached score for noloco.io is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Noloco (registry title: noloco.io) | | --- | --- | | Domain | noloco.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for noloco.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Noloco. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for noloco.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Noloco. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/noloco-io/index.md) ## Sources - [Ora score page for noloco.io](https://ora.ai/score/noloco.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/leaderboard) - [Where Noloco was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Noloco website](https://noloco.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nomas MCP server | Agent MCP Directory" description: "Nomas: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nomas-fyi site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nomas MCP server | Agent MCP Directory > Nomas: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/nomas-fyi Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nomas: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Nomas at mcp.nomas.fyi answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Nomas (registry title: Nomas Research) | | --- | --- | | Domain | nomas.fyi | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for nomas.fyi when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.nomas.fyi/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 954 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:33Z https://mcp.nomas.fyi/mcp sent initialize result auth-required (HTTP 401) 851 ms - 20:03:45Z https://mcp.nomas.fyi/mcp sent initialize result auth-required (HTTP 401) 954 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="nomas", resource_metadata="https://mcp.nomas.fyi/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.nomas.fyi | | Authorization server metadata | mcp.nomas.fyi | | Registration endpoint | https://mcp.nomas.fyi/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.nomas.fyi/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.nomas.fyi/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.nomas.fyi/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Nomas. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nomas-fyi/index.md) ## Sources - [Nomas website](https://nomas.fyi), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Noonlaunch MCP server | Agent MCP Directory" description: "Noonlaunch has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/noonlaunch-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Noonlaunch MCP server | Agent MCP Directory > Noonlaunch has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/noonlaunch-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Noonlaunch: MCP server, CLI and agent surfaces Yes: Noonlaunch runs a public MCP server at noonlaunch.com that listed 10 tools to a client with no credentials on 4 November 2026. Examples: search-directory, get-product, get-weekly-winners. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for noonlaunch.com is 61, grade C, read on 5 November 2026. ## Fact sheet | Company | Noonlaunch | | --- | --- | | Domain | noonlaunch.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 61, grade C; Ora scanned the domain on 17 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for noonlaunch.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://noonlaunch.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Noonlaunch 2.0.0 | | Capabilities | tools, resources, prompts | | Tools | 10 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 3,674 ms over 2 attempts | | Result | initialize error: Unsupported protocol version | ### Tools listed 10 tools - search-directory - get-product - get-weekly-winners - list-launch-directories - get-plans - check-product - submit-product - verify-badge - check-status - report-badge-problem ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:36Z https://noonlaunch.com/mcp sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3745 ms - 20:03:48Z https://noonlaunch.com/mcp sent initialize, initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3674 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://noonlaunch.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Noonlaunch. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: noonlaunch.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.noonlaunch/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/noonlaunch-com/index.md) ## Sources - [Ora score page for noonlaunch.com](https://ora.ai/score/noonlaunch.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=noonlaunch), read 4 November 2026 - [Noonlaunch website](https://noonlaunch.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Northflank MCP server | Agent MCP Directory" description: "Northflank: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/northflank-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Northflank MCP server | Agent MCP Directory > Northflank: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/northflank-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Northflank: MCP server, CLI and agent surfaces Not counted. No source names an endpoint for Northflank; the connector's guess at mcp.northflank.com asked for credentials on 4 November 2026 and published no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Northflank | | --- | --- | | Domain | northflank.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 53, grade C; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for northflank.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.northflank.com/mcp | | --- | --- | | How it was found | mcp.northflank.com was tried as a guess and answered; see the result below | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 761 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:33Z https://mcp.northflank.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 747 ms - 20:03:45Z https://mcp.northflank.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 761 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.northflank.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Northflank. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/northflank-com/index.md) ## Sources - [Ora score page for northflank.com](https://ora.ai/score/northflank.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/leaderboard) - [Where Northflank was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Northflank website](https://northflank.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Notaiochianese MCP server | Agent MCP Directory" description: "Notaiochianese has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/notaiochianese-it site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Notaiochianese MCP server | Agent MCP Directory > Notaiochianese has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/notaiochianese-it Site: Agent MCP Directory Last reviewed: 2026-11-05 # Notaiochianese: MCP server, CLI and agent surfaces Yes: Notaiochianese runs a public MCP server at mcp.notaiochianese.it that listed 6 tools to a client with no credentials on 4 November 2026. Examples: imposte\_acquisto\_immobile, valore\_catastale, usufrutto\_nuda\_proprieta. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Notaiochianese (registry title: Strumenti di calcolo dello Studio Notarile Chianese) | | --- | --- | | Domain | notaiochianese.it | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for notaiochianese.it when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.notaiochianese.it/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | it.notaiochianese/strumenti-di-calcolo 1.8.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 615 ms over 1 attempt | ### Tools listed 6 tools - imposte\_acquisto\_immobile - valore\_catastale - usufrutto\_nuda\_proprieta - vendita\_o\_donazione - imposte\_successione\_donazione - quote\_ereditarie ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:33Z https://mcp.notaiochianese.it/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 671 ms - 20:03:46Z https://mcp.notaiochianese.it/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 615 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.notaiochianese.it/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Notaiochianese. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/notaiochianese-it/index.md) ## Sources - [Notaiochianese website](https://notaiochianese.it), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Notion (notion.com) MCP server | Agent MCP Directory" description: "Notion (notion.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/notion-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Notion (notion.com) MCP server | Agent MCP Directory > Notion (notion.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/notion-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Notion: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Notion at mcp.notion.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Notion | | --- | --- | | Domain | notion.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 1,404 on the list of 4 November 2026 | | Ora score | 85, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for notion.com, a vendor-published score) | | Company found through | the vendor's own documentation; the GitHub MCP Registry; the official MCP Registry; the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.notion.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the GitHub MCP Registry; the official MCP Registry; the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 115 ms over 1 attempt | | Documentation | developers.notion.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:56Z https://mcp.notion.com/mcp sent initialize result auth-required (HTTP 401) 88 ms - 20:01:32Z https://mcp.notion.com/mcp sent initialize result auth-required (HTTP 401) 115 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.notion.com/.well-known/oauth-protected-resource/mcp", scope="default" | | Protected resource metadata | mcp.notion.com | | Authorization server metadata | mcp.notion.com | | Registration endpoint | https://mcp.notion.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.notion.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.notion.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.notion.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Notion. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: notion.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.notion/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/notion-com/index.md) ## Sources - [Notion MCP documentation](https://developers.notion.com/docs/mcp), read 4 November 2026 - [Ora score page for notion.com](https://ora.ai/score/notion.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=notion), read 4 November 2026 - [Notion website](https://notion.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Notion (notion.so) MCP server | Agent MCP Directory" description: "Notion (notion.so): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/notion-so site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Notion (notion.so) MCP server | Agent MCP Directory > Notion (notion.so): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/notion-so Site: Agent MCP Directory Last reviewed: 2026-11-05 # Notion: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Notion at mcp.notion.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Notion | | --- | --- | | Domain | notion.so | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,102 on the list of 4 November 2026 | | Ora score | 70, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for notion.so, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.notion.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 61 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.notion.com/mcp sent initialize result auth-required (HTTP 401) 57 ms - 20:01:33Z https://mcp.notion.com/mcp sent initialize result auth-required (HTTP 401) 61 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.notion.com/.well-known/oauth-protected-resource/mcp", scope="default" | | Protected resource metadata | mcp.notion.com | | Authorization server metadata | mcp.notion.com | | Registration endpoint | https://mcp.notion.com/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.notion.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.notion.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.notion.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Notion. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: notion.so/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/notion-so/index.md) ## Sources - [Ora score page for notion.so](https://ora.ai/score/notion.so?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Notion was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Notion website](https://notion.so), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Notion HQ MCP server | Agent MCP Directory" description: "Does Notion HQ have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/notionhq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Notion HQ MCP server | Agent MCP Directory > Does Notion HQ have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/notionhq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Notion HQ: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Notion HQ (notionhq.com), so the connector had nothing to connect to. Ora's cached score for notionhq.com is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Notion HQ (registry title: notionhq.com) | | --- | --- | | Domain | notionhq.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for notionhq.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Notion HQ. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for notionhq.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Notion HQ. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/notionhq-com/index.md) ## Sources - [Ora score page for notionhq.com](https://ora.ai/score/notionhq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Notion HQ was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Notion HQ website](https://notionhq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Notte MCP server | Agent MCP Directory" description: "Does Notte have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/notte-cc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Notte MCP server | Agent MCP Directory > Does Notte have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/notte-cc Site: Agent MCP Directory Last reviewed: 2026-11-05 # Notte: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Notte (notte.cc), so the connector had nothing to connect to. Ora's cached score for notte.cc is 89, grade A, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Notte (registry title: notte.cc) | | --- | --- | | Domain | notte.cc | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 89, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for notte.cc, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Notte. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for notte.cc, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Notte. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/notte-cc/index.md) ## Sources - [Ora score page for notte.cc](https://ora.ai/score/notte.cc?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Notte was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Notte website](https://notte.cc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Novadata MCP server | Agent MCP Directory" description: "Novadata: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/novadata-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Novadata MCP server | Agent MCP Directory > Novadata: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/novadata-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Novadata: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Novadata at mcp.novadata.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Novadata (registry title: Nova Amazon MCP Server) | | --- | --- | | Domain | novadata.io | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for novadata.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.novadata.io/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,135 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:35Z https://mcp.novadata.io/api/mcp sent initialize result auth-required (HTTP 401) 1354 ms - 20:03:47Z https://mcp.novadata.io/api/mcp sent initialize result auth-required (HTTP 401) 1135 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.novadata.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.novadata.io | | Authorization server metadata | auth.novadata.io | | Registration endpoint | https://auth.novadata.io/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.novadata.io/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.novadata.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.novadata.io/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Novadata. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/novadata-io/index.md) ## Sources - [Novadata website](https://novadata.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Noveum MCP server | Agent MCP Directory" description: "Noveum: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/noveum-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Noveum MCP server | Agent MCP Directory > Noveum: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/noveum-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Noveum: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Noveum at noveum.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Noveum (registry title: Orbit) | | --- | --- | | Domain | noveum.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 67, grade C; Ora scanned the domain on 10 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for noveum.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://noveum.ai/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,346 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:35Z https://noveum.ai/api/mcp sent initialize result auth-required (HTTP 401) 1458 ms - 20:03:47Z https://noveum.ai/api/mcp sent initialize result auth-required (HTTP 401) 1346 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://noveum.ai/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | noveum.ai | | Authorization server metadata | noveum.ai | | Registration endpoint | https://noveum.ai/api/oauth/register | ### The sign-in route, step by step 1. Request `https://noveum.ai/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://noveum.ai/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://noveum.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Noveum. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.noveum/noveum | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/noveum-ai/index.md) ## Sources - [Ora score page for noveum.ai](https://ora.ai/score/noveum.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 September 2026, read from GET /api/score) - [Where Noveum was found](https://github.com/mcp/Noveum/orbit), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=noveum), read 4 November 2026 - [Noveum website](https://noveum.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nslookup MCP server | Agent MCP Directory" description: "Nslookup has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nslookup-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nslookup MCP server | Agent MCP Directory > Nslookup has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/nslookup-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nslookup: MCP server, CLI and agent surfaces Yes: Nslookup runs a public MCP server at mcp.nslookup.io that listed 23 tools to a client with no credentials on 4 November 2026. Examples: dns\_lookup, dns\_record, dns\_propagation. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Nslookup (registry title: Venomseven Nslookup) | | --- | --- | | Domain | nslookup.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for nslookup.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.nslookup.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | nslookup 1.6.0 | | Capabilities | tools | | Tools | 23 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 554 ms over 1 attempt | ### Tools listed 23 tools - dns\_lookup - dns\_record - dns\_propagation - webservers - ssl\_certificate - bimi\_vmc - security\_scan - uptime\_check - uptime\_check\_multi - dns\_health - geo\_checker - rdap\_lookup - hosting\_report - domain\_scanner - dns\_change\_review - bimi\_check - status\_page - my\_overview - my\_monitors - my\_incidents - my\_uptime\_history - my\_dns\_changes - my\_certificates ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:34Z https://mcp.nslookup.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 655 ms - 20:03:47Z https://mcp.nslookup.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 554 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.nslookup.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Nslookup. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nslookup-io/index.md) ## Sources - [Nslookup website](https://nslookup.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nuanced MCP server | Agent MCP Directory" description: "Does Nuanced have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nuanced-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nuanced MCP server | Agent MCP Directory > Does Nuanced have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/nuanced-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nuanced: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Nuanced (nuanced.dev), so the connector had nothing to connect to. Ora's cached score for nuanced.dev is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Nuanced (registry title: nuanced.dev) | | --- | --- | | Domain | nuanced.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 3 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for nuanced.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Nuanced. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for nuanced.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Nuanced. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nuanced-dev/index.md) ## Sources - [Ora score page for nuanced.dev](https://ora.ai/score/nuanced.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 October 2026, read from GET /api/leaderboard) - [Where Nuanced was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Nuanced website](https://nuanced.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nullstone MCP server | Agent MCP Directory" description: "Does Nullstone have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nullstone-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nullstone MCP server | Agent MCP Directory > Does Nullstone have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/nullstone-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nullstone: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Nullstone (nullstone.io), so the connector had nothing to connect to. Ora's cached score for nullstone.io is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Nullstone (registry title: nullstone.io) | | --- | --- | | Domain | nullstone.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for nullstone.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Nullstone. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for nullstone.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Nullstone. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nullstone-io/index.md) ## Sources - [Ora score page for nullstone.io](https://ora.ai/score/nullstone.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Where Nullstone was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Nullstone website](https://nullstone.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nuxt MCP server | Agent MCP Directory" description: "Nuxt has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/nuxt-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nuxt MCP server | Agent MCP Directory > Nuxt has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/nuxt-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nuxt: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Nuxt (mcp.nuxt.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: ENOTFOUND. Ora's cached score for nuxt.com is 79, grade B, read on 5 November 2026. ## Fact sheet | Company | Nuxt | | --- | --- | | Domain | nuxt.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | 79, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for nuxt.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.nuxt.com/sse | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 3 ms over 1 attempt | | Result | ENOTFOUND | ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:58:34Z https://mcp.nuxt.com/sse sent initialize result no-answer 15 ms - 20:03:47Z https://mcp.nuxt.com/sse sent initialize result no-answer 3 ms - 20:03:47Z https://mcp.nuxt.com/mcp sent initialize result no-answer 2 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.nuxt.com/sse`. The connector could not tell what it wants: ENOTFOUND. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Nuxt. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: nuxt.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nuxt-com/index.md) ## Sources - [Ora score page for nuxt.com](https://ora.ai/score/nuxt.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Nuxt website](https://nuxt.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "NVIDIA MCP server | Agent MCP Directory" description: "NVIDIA: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nvidia-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # NVIDIA MCP server | Agent MCP Directory > NVIDIA: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/nvidia-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # NVIDIA: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for NVIDIA at api.copilot.nsight.ngc.nvidia.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | NVIDIA (registry title: NVIDIA CUDA Docs) | | --- | --- | | Domain | nvidia.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 362 on the list of 4 November 2026 | | Ora score | 77, grade B; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for nvidia.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,803 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs sent initialize result auth-required (HTTP 401) 1727 ms - 20:01:30Z https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs sent initialize result auth-required (HTTP 401) 1803 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.copilot.nsight.ngc.nvidia.com/.well-known/oauth-protected-resource/mcp/cuda-docs" | | Protected resource metadata | api.copilot.nsight.ngc.nvidia.com | | Authorization server metadata | api.copilot.nsight.ngc.nvidia.com | | Registration endpoint | https://api.copilot.nsight.ngc.nvidia.com/register | ### The sign-in route, step by step 1. Request `https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.copilot.nsight.ngc.nvidia.com/.well-known/oauth-protected-resource/mcp/cuda-docs` to find the authorization server. 3. Register a client at the registration endpoint `https://api.copilot.nsight.ngc.nvidia.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for NVIDIA. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.nvidia.ngc.nsight.copilot.api/cuda-docs | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nvidia-com/index.md) ## Sources - [Ora score page for nvidia.com](https://ora.ai/score/nvidia.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/score) - [Where NVIDIA was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.nvidia.ngc.nsight.copilot.api%2Fcuda-docs), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=nvidia), read 4 November 2026 - [NVIDIA website](https://nvidia.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Nyckel MCP server | Agent MCP Directory" description: "Does Nyckel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/nyckel-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Nyckel MCP server | Agent MCP Directory > Does Nyckel have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/nyckel-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nyckel: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Nyckel (nyckel.com), so the connector had nothing to connect to. Ora's cached score for nyckel.com is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Nyckel (registry title: nyckel.com) | | --- | --- | | Domain | nyckel.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for nyckel.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Nyckel. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for nyckel.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Nyckel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/nyckel-com/index.md) ## Sources - [Ora score page for nyckel.com](https://ora.ai/score/nyckel.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where Nyckel was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Nyckel website](https://nyckel.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Oakallow MCP server | Agent MCP Directory" description: "Oakallow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/oakallow-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Oakallow MCP server | Agent MCP Directory > Oakallow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/oakallow-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Oakallow: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Oakallow at api.oakallow.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Oakallow | | --- | --- | | Domain | oakallow.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for oakallow.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.oakallow.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 211 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:35Z https://api.oakallow.io/mcp sent initialize result auth-required (HTTP 401) 479 ms - 20:03:47Z https://api.oakallow.io/mcp sent initialize result auth-required (HTTP 401) 211 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://api.oakallow.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | api.oakallow.io | | Authorization server metadata | api.oakallow.io | | Registration endpoint | https://api.oakallow.io/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.oakallow.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.oakallow.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.oakallow.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Oakallow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/oakallow-io/index.md) ## Sources - [Oakallow website](https://oakallow.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Obolusfinanz MCP server | Agent MCP Directory" description: "Obolusfinanz has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/obolusfinanz-de site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Obolusfinanz MCP server | Agent MCP Directory > Obolusfinanz has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/obolusfinanz-de Site: Agent MCP Directory Last reviewed: 2026-11-05 # Obolusfinanz: MCP server, CLI and agent surfaces Yes: Obolusfinanz runs a public MCP server at www.obolusfinanz.de that listed 2 tools to a client with no credentials on 4 November 2026. Examples: berechne, taxcompare. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Obolusfinanz (registry title: Obolus) | | --- | --- | | Domain | obolusfinanz.de | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for obolusfinanz.de when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.obolusfinanz.de/api/mcp/public | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Obolus Finanz Payroll API 2.1.0 | | Capabilities | tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,266 ms over 1 attempt | ### Tools listed 2 tools - berechne - taxcompare ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:37Z https://www.obolusfinanz.de/api/mcp/public sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2290 ms - 20:03:49Z https://www.obolusfinanz.de/api/mcp/public sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2266 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.obolusfinanz.de/api/mcp/public` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Obolusfinanz. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/obolusfinanz-de/index.md) ## Sources - [Obolusfinanz website](https://obolusfinanz.de), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Octagon MCP server | Agent MCP Directory" description: "Octagon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/octagonai-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Octagon MCP server | Agent MCP Directory > Octagon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/octagonai-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Octagon: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Octagon at mcp.octagonagents.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Octagon | | --- | --- | | Domain | octagonai.co | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for octagonai.co when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.octagonagents.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,221 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:36Z https://mcp.octagonagents.com/mcp sent initialize result auth-required (HTTP 401) 1573 ms - 20:03:48Z https://mcp.octagonagents.com/mcp sent initialize result auth-required (HTTP 401) 1221 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.octagonai.co/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.octagonai.co | | Authorization server metadata | login.octagonai.co | | Registration endpoint | https://login.octagonai.co/oauth2/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.octagonagents.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.octagonai.co/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://login.octagonai.co/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Octagon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/octagonai-co/index.md) ## Sources - [Where Octagon was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Octagon website](https://octagonai.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Octoml MCP server | Agent MCP Directory" description: "Does Octoml have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/octoml-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Octoml MCP server | Agent MCP Directory > Does Octoml have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/octoml-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Octoml: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Octoml (octoml.ai), so the connector had nothing to connect to. Ora's cached score for octoml.ai is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Octoml (registry title: octoml.ai) | | --- | --- | | Domain | octoml.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 31 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for octoml.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Octoml. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for octoml.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Octoml. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/octoml-ai/index.md) ## Sources - [Ora score page for octoml.ai](https://ora.ai/score/octoml.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 August 2026, read from GET /api/leaderboard) - [Where Octoml was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Octoml website](https://octoml.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OctoPerf MCP server | Agent MCP Directory" description: "OctoPerf: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/octoperf-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OctoPerf MCP server | Agent MCP Directory > OctoPerf: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/octoperf-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OctoPerf: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for OctoPerf at api.octoperf.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | OctoPerf | | --- | --- | | Domain | octoperf.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 53, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for octoperf.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.octoperf.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 624 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:37Z https://api.octoperf.com/mcp sent initialize result auth-required (HTTP 401) 1114 ms - 20:03:49Z https://api.octoperf.com/mcp sent initialize result auth-required (HTTP 401) 624 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.octoperf.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.octoperf.com | | Authorization server metadata | api.octoperf.com | | Registration endpoint | https://api.octoperf.com/auth/connect/register | ### The sign-in route, step by step 1. Request `https://api.octoperf.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.octoperf.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.octoperf.com/auth/connect/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OctoPerf. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/octoperf-com/index.md) ## Sources - [Ora score page for octoperf.com](https://ora.ai/score/octoperf.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/score) - [OctoPerf website](https://octoperf.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Odigos MCP server | Agent MCP Directory" description: "Does Odigos have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/odigos-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Odigos MCP server | Agent MCP Directory > Does Odigos have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/odigos-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Odigos: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Odigos (odigos.io), so the connector had nothing to connect to. Ora's cached score for odigos.io is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Odigos (registry title: odigos.io) | | --- | --- | | Domain | odigos.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for odigos.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Odigos. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for odigos.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Odigos. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/odigos-io/index.md) ## Sources - [Ora score page for odigos.io](https://ora.ai/score/odigos.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Odigos was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Odigos website](https://odigos.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Offline Protocol MCP server | Agent MCP Directory" description: "Offline Protocol has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/offlineprotocol-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Offline Protocol MCP server | Agent MCP Directory > Offline Protocol has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/offlineprotocol-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Offline Protocol: MCP server, CLI and agent surfaces Yes: Offline Protocol runs a public MCP server at mcp.offlineprotocol.com that listed 15 tools to a client with no credentials on 4 November 2026. Examples: list\_packages, get\_package, search\_packages. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Offline Protocol (registry title: Offline Protocol (hosted)) | | --- | --- | | Domain | offlineprotocol.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for offlineprotocol.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.offlineprotocol.com/public/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | offline-protocol 0.3.1 | | Capabilities | tools, resources | | Tools | 15 | | Resources | 65 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,125 ms over 1 attempt | ### Tools listed 15 tools - list\_packages - get\_package - search\_packages - search\_capabilities - search\_workflows - search\_examples - search\_skills - list\_workflows - get\_workflow - list\_skills - get\_skill - resolve\_packages - get\_template - generate\_architecture - preview\_scaffold ### Connector log 4 connections on 4 November 2026, read-only methods only - 19:58:38Z https://mcp.offlineprotocol.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1724 ms - 19:58:39Z https://mcp.offlineprotocol.com/public/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1086 ms - 20:03:50Z https://mcp.offlineprotocol.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1400 ms - 20:03:51Z https://mcp.offlineprotocol.com/public/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1125 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.offlineprotocol.com/public/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Offline Protocol. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.offlineprotocol/hosted | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/offlineprotocol-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=offlineprotocol), read 4 November 2026 - [Offline Protocol website](https://offlineprotocol.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Okfindex MCP server | Agent MCP Directory" description: "Okfindex has an open MCP server with 107 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/okfindex-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Okfindex MCP server | Agent MCP Directory > Okfindex has an open MCP server with 107 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/okfindex-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Okfindex: MCP server, CLI and agent surfaces Yes: Okfindex runs a public MCP server at okfindex.com that listed 107 tools to a client with no credentials on 4 November 2026. Examples: api\_index, search\_bundles, get\_bundle. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Okfindex | | --- | --- | | Domain | okfindex.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for okfindex.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://okfindex.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | OKF Index fb0c5518 | | Capabilities | tools, prompts | | Tools | 107 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,202 ms over 1 attempt | ### Tools listed 107 tools; the first 40 names are recorded - api\_index - search\_bundles - get\_bundle - index\_stats - legislation\_status - search\_legislation - get\_legislation - get\_legislation\_part - list\_bases - create\_base - publish\_base - unpublish\_base - get\_base - get\_base\_usage - list\_base\_documents - get\_base\_connection - connect\_base\_source - disconnect\_base\_source - search\_base - add\_base\_document - replace\_base\_document - remove\_base\_document - get\_base\_document - read\_base\_markdown - read\_base\_original - read\_base\_image - read\_base\_index - read\_base\_concept - read\_base\_source - read\_base\_pdf\_source - read\_base\_docx\_source - read\_base\_doc\_source - export\_base - quote\_base\_document - list\_base\_conversions - get\_base\_conversion - remove\_base\_conversion - authorize\_base\_conversion - ask\_base\_question - get\_base\_answer ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:39Z https://okfindex.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2552 ms - 20:03:51Z https://okfindex.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2202 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://okfindex.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Okfindex. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: okfindex.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.okfindex/okfindex | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/okfindex-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=okfindex), read 4 November 2026 - [Okfindex website](https://okfindex.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Okibi MCP server | Agent MCP Directory" description: "Okibi has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/okibi-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Okibi MCP server | Agent MCP Directory > Okibi has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/okibi-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Okibi: MCP server, CLI and agent surfaces Yes: Okibi runs a public MCP server at porch.okibi.ai that listed 10 tools to a client with no credentials on 4 November 2026. Examples: create\_inbox, get\_inbox, list\_requests. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for okibi.ai is 35, grade D, read on 5 November 2026. ## Fact sheet | Company | Okibi (registry title: Porch) | | --- | --- | | Domain | okibi.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 35, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for okibi.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://porch.okibi.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | porch 0.1.0 | | Capabilities | resources, extensions, tools | | Tools | 10 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,421 ms over 1 attempt | ### Tools listed 10 tools - create\_inbox - get\_inbox - list\_requests - get\_request - wait\_for\_request - set\_response - create\_approval\_link - wait\_for\_approval - clear\_requests - delete\_inbox ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:38Z https://porch.okibi.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1605 ms - 20:03:50Z https://porch.okibi.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1421 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://porch.okibi.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Okibi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.okibi/porch | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/okibi-ai/index.md) ## Sources - [Ora score page for okibi.ai](https://ora.ai/score/okibi.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/score) - [Where Okibi was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.okibi%2Fporch), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=okibi), read 4 November 2026 - [Okibi website](https://okibi.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Okteto MCP server | Agent MCP Directory" description: "Does Okteto have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/okteto-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Okteto MCP server | Agent MCP Directory > Does Okteto have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/okteto-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Okteto: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Okteto (okteto.com), so the connector had nothing to connect to. Ora's cached score for okteto.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Okteto (registry title: okteto.com) | | --- | --- | | Domain | okteto.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for okteto.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Okteto. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for okteto.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Okteto. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/okteto-com/index.md) ## Sources - [Ora score page for okteto.com](https://ora.ai/score/okteto.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Okteto was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Okteto website](https://okteto.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ollama MCP server | Agent MCP Directory" description: "Does Ollama have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ollama-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ollama MCP server | Agent MCP Directory > Does Ollama have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/ollama-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ollama: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ollama (ollama.com), so the connector had nothing to connect to. Ora's cached score for ollama.com is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ollama (registry title: ollama.com) | | --- | --- | | Domain | ollama.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 4,454 on the list of 4 November 2026 | | Ora score | 65, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ollama.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ollama. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ollama.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ollama. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ollama-com/index.md) ## Sources - [Ora score page for ollama.com](https://ora.ai/score/ollama.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/score) - [Where Ollama was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ollama website](https://ollama.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Omnara MCP server | Agent MCP Directory" description: "Omnara: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/omnara-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Omnara MCP server | Agent MCP Directory > Omnara: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/omnara-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Omnara: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Omnara at app.omnara.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Omnara | | --- | --- | | Domain | omnara.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 84, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for omnara.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.omnara.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,331 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:38Z https://app.omnara.com/mcp sent initialize result auth-required (HTTP 401) 1482 ms - 20:03:50Z https://app.omnara.com/mcp sent initialize result auth-required (HTTP 401) 1331 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.omnara.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | app.omnara.com | | Authorization server metadata | app.omnara.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://app.omnara.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.omnara.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Omnara. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.omnara/omnara | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/omnara-com/index.md) ## Sources - [Ora score page for omnara.com](https://ora.ai/score/omnara.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=omnara), read 4 November 2026 - [Omnara website](https://omnara.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Omnidim MCP server | Agent MCP Directory" description: "Omnidim: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/omnidim-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Omnidim MCP server | Agent MCP Directory > Omnidim: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/omnidim-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Omnidim: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Omnidim at mcp.omnidim.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Omnidim | | --- | --- | | Domain | omnidim.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 79, grade B; Ora scanned the domain on 12 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for omnidim.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.omnidim.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,616 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:40Z https://mcp.omnidim.io/mcp sent initialize result auth-required (HTTP 401) 2715 ms - 20:03:52Z https://mcp.omnidim.io/mcp sent initialize result auth-required (HTTP 401) 2616 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp.omnidim.io" | | Protected resource metadata | mcp.omnidim.io | | Authorization server metadata | mcp.omnidim.io | | Registration endpoint | https://mcp.omnidim.io/register | ### The sign-in route, step by step 1. Request `https://mcp.omnidim.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.omnidim.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.omnidim.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Omnidim. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: omnidim.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/omnidim-io/index.md) ## Sources - [Ora score page for omnidim.io](https://ora.ai/score/omnidim.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 October 2026, read from GET /api/score) - [Where Omnidim was found](https://github.com/mcp/Omnidim/omnidim-mcp-server), read 4 November 2026 - [Omnidim website](https://omnidim.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Omnistrate MCP server | Agent MCP Directory" description: "Does Omnistrate have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/omnistrate-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Omnistrate MCP server | Agent MCP Directory > Does Omnistrate have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/omnistrate-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Omnistrate: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Omnistrate (omnistrate.com), so the connector had nothing to connect to. Ora's cached score for omnistrate.com is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Omnistrate (registry title: omnistrate.com) | | --- | --- | | Domain | omnistrate.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for omnistrate.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Omnistrate. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for omnistrate.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Omnistrate. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/omnistrate-com/index.md) ## Sources - [Ora score page for omnistrate.com](https://ora.ai/score/omnistrate.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Omnistrate was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Omnistrate website](https://omnistrate.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OneContext MCP server | Agent MCP Directory" description: "OneContext: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/onecontext-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OneContext MCP server | Agent MCP Directory > OneContext: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/onecontext-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # OneContext: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for OneContext at rag-mcp-2.whatsmcp.workers.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | OneContext | | --- | --- | | Domain | onecontext.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for onecontext.ai when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://rag-mcp-2.whatsmcp.workers.dev/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 326 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:38Z https://rag-mcp-2.whatsmcp.workers.dev/sse sent initialize result auth-required (HTTP 401) 566 ms - 20:03:50Z https://rag-mcp-2.whatsmcp.workers.dev/sse sent initialize result auth-required (HTTP 401) 326 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token" | | Authorization server metadata | rag-mcp-2.whatsmcp.workers.dev | | Registration endpoint | https://rag-mcp-2.whatsmcp.workers.dev/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://rag-mcp-2.whatsmcp.workers.dev/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://rag-mcp-2.whatsmcp.workers.dev/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OneContext. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/onecontext-ai/index.md) ## Sources - [Where OneContext was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [OneContext website](https://onecontext.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Onenote MCP server | Agent MCP Directory" description: "Does Onenote have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/onenote-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Onenote MCP server | Agent MCP Directory > Does Onenote have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/onenote-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Onenote: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Onenote (onenote.com), so the connector had nothing to connect to. Ora's cached score for onenote.com is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Onenote (registry title: onenote.com) | | --- | --- | | Domain | onenote.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 3,624 on the list of 4 November 2026 | | Ora score | 43, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for onenote.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Onenote. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for onenote.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Onenote. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/onenote-com/index.md) ## Sources - [Ora score page for onenote.com](https://ora.ai/score/onenote.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/score) - [Where Onenote was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Onenote website](https://onenote.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ONES MCP server | Agent MCP Directory" description: "ONES: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ones-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ONES MCP server | Agent MCP Directory > ONES: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ones-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ONES: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ONES at us.ones.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ONES | | --- | --- | | Domain | ones.com | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 59, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ones.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://us.ones.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,500 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:39Z https://us.ones.com/mcp sent initialize result auth-required (HTTP 401) 1472 ms - 20:03:52Z https://us.ones.com/mcp sent initialize result auth-required (HTTP 401) 1500 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer FAKESECRET_g3h4i5j6k7l8m9n0o1p2="https://us.ones.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | us.ones.com | | Authorization server metadata | us.ones.com | | Registration endpoint | https://us.ones.com/mcp/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://us.ones.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://us.ones.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://us.ones.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ONES. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.ones/ones | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ones-com/index.md) ## Sources - [Ora score page for ones.com](https://ora.ai/score/ones.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ones), read 4 November 2026 - [ONES website](https://ones.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OneSchema MCP server | Agent MCP Directory" description: "OneSchema: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/oneschema-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OneSchema MCP server | Agent MCP Directory > OneSchema: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/oneschema-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # OneSchema: MCP server, CLI and agent surfaces Not counted. The endpoint listed for OneSchema at api.oneschema.co asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | OneSchema (registry title: OneSchema MCP Server) | | --- | --- | | Domain | oneschema.co | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 56, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for oneschema.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.oneschema.co/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,556 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:40Z https://api.oneschema.co/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1851 ms - 20:03:52Z https://api.oneschema.co/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1556 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://api.oneschema.co/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OneSchema. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.oneschema/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/oneschema-co/index.md) ## Sources - [Ora score page for oneschema.co](https://ora.ai/score/oneschema.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where OneSchema was found](https://registry.modelcontextprotocol.io/v0/servers?search=co.oneschema%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=oneschema), read 4 November 2026 - [OneSchema website](https://oneschema.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Onlook MCP server | Agent MCP Directory" description: "Onlook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/onlook-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Onlook MCP server | Agent MCP Directory > Onlook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/onlook-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Onlook: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Onlook; the connector's guess at mcp.onlook.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Onlook (registry title: onlook.com) | | --- | --- | | Domain | onlook.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 67, grade C; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for onlook.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.onlook.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,818 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:41Z https://mcp.onlook.com/mcp sent initialize result auth-required (HTTP 401) 2387 ms - 20:03:52Z https://mcp.onlook.com/mcp sent initialize result auth-required (HTTP 401) 1818 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.onlook.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.onlook.com | | Authorization server metadata | mcp.onlook.com | | Registration endpoint | https://mcp.onlook.com/register | ### The sign-in route, step by step 1. Request `https://mcp.onlook.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.onlook.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.onlook.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Onlook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/onlook-com/index.md) ## Sources - [Ora score page for onlook.com](https://ora.ai/score/onlook.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 October 2026, read from GET /api/leaderboard) - [Where Onlook was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Onlook website](https://onlook.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpenAccountants MCP server | Agent MCP Directory" description: "OpenAccountants has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/openaccountants-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpenAccountants MCP server | Agent MCP Directory > OpenAccountants has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/openaccountants-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenAccountants: MCP server, CLI and agent surfaces Yes: OpenAccountants runs a public MCP server at www.openaccountants.com that listed 15 tools to a client with no credentials on 4 November 2026. Examples: start, search\_skills, get\_skill. It speaks streamable-http, protocol 2025-03-26. Ora's cached score for openaccountants.com is 64, grade C, read on 5 November 2026. ## Fact sheet | Company | OpenAccountants | | --- | --- | | Domain | openaccountants.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 64, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for openaccountants.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.openaccountants.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | openaccountants-mcp 1.4.0 | | Capabilities | tools, prompts | | Tools | 15 | | Resources | 0 | | Prompts | 13 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,557 ms over 1 attempt | ### Tools listed 15 tools - start - search\_skills - get\_skill - search\_rules - list\_skills - get\_skill\_sections - get\_deadlines - list\_rule\_facets - start\_help - list\_jurisdictions - list\_verifiers - get\_quote - validate\_vat\_number - check\_audit\_exemption - share\_with\_openaccountants ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:42Z https://www.openaccountants.com/api/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2514 ms - 20:03:53Z https://www.openaccountants.com/api/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 1557 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.openaccountants.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OpenAccountants. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openaccountants-com/index.md) ## Sources - [Ora score page for openaccountants.com](https://ora.ai/score/openaccountants.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/score) - [Where OpenAccountants was found](https://github.com/mcp/openaccountants/openaccountants), read 4 November 2026 - [OpenAccountants website](https://openaccountants.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpenAI MCP server | Agent MCP Directory" description: "Does OpenAI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/openai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpenAI MCP server | Agent MCP Directory > Does OpenAI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/openai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenAI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for OpenAI (openai.com), so the connector had nothing to connect to. A CLI is on record: @openai/codex on npm. Ora's cached score for openai.com is 58, grade C, read on 5 November 2026. ## Fact sheet | Company | OpenAI | | --- | --- | | Domain | openai.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 129 on the list of 4 November 2026 | | Ora score | 58, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for openai.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for OpenAI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for openai.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | @openai/codex on npm (page) | | --- | --- | | Exists | yes | | Latest version | 0.166.0 | | Last publish | 29 October 2026 | | Command names | codex | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: raw.githubusercontent.com (YAML, via vendor docs). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openai-com/index.md) ## Sources - [Ora score page for openai.com](https://ora.ai/score/openai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where OpenAI was found](https://platform.openai.com/docs/mcp), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Openfoundry MCP server | Agent MCP Directory" description: "Does Openfoundry have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/openfoundry-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Openfoundry MCP server | Agent MCP Directory > Does Openfoundry have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/openfoundry-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Openfoundry: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Openfoundry (openfoundry.ai), so the connector had nothing to connect to. Ora's cached score for openfoundry.ai is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Openfoundry (registry title: openfoundry.ai) | | --- | --- | | Domain | openfoundry.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 6 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for openfoundry.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Openfoundry. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for openfoundry.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Openfoundry. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openfoundry-ai/index.md) ## Sources - [Ora score page for openfoundry.ai](https://ora.ai/score/openfoundry.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 October 2026, read from GET /api/leaderboard) - [Where Openfoundry was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Openfoundry website](https://openfoundry.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Openlayer MCP server | Agent MCP Directory" description: "Openlayer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/openlayer-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Openlayer MCP server | Agent MCP Directory > Openlayer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/openlayer-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Openlayer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Openlayer at mcp.openlayer.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Openlayer | | --- | --- | | Domain | openlayer.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 82, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for openlayer.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.openlayer.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 3,445 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:44Z https://mcp.openlayer.com/mcp sent initialize result auth-required (HTTP 401) 3906 ms - 20:03:55Z https://mcp.openlayer.com/mcp sent initialize result auth-required (HTTP 401) 3445 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.openlayer.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.openlayer.com | | Authorization server metadata | api.openlayer.com | | Registration endpoint | https://api.openlayer.com/v1/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.openlayer.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.openlayer.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.openlayer.com/v1/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Openlayer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.openlayer/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openlayer-com/index.md) ## Sources - [Ora score page for openlayer.com](https://ora.ai/score/openlayer.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Openlayer was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.openlayer%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=openlayer), read 4 November 2026 - [Openlayer website](https://openlayer.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpenMesh MCP server | Agent MCP Directory" description: "OpenMesh has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/openmesh-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpenMesh MCP server | Agent MCP Directory > OpenMesh has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/openmesh-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenMesh: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for OpenMesh (api.openmesh.dev), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: ENOTFOUND. The row is kept so the claim is visible and can be re-checked next edition. ## Fact sheet | Company | OpenMesh | | --- | --- | | Domain | openmesh.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for openmesh.dev when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.openmesh.dev/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 5 ms over 1 attempt | | Result | ENOTFOUND | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:41Z https://api.openmesh.dev/mcp sent initialize result no-answer 72 ms - 20:03:52Z https://api.openmesh.dev/mcp sent initialize result no-answer 5 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.openmesh.dev/mcp`. The connector could not tell what it wants: ENOTFOUND. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OpenMesh. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openmesh-dev/index.md) ## Sources - [Where OpenMesh was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpenReplay MCP server | Agent MCP Directory" description: "Does OpenReplay have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/openreplay-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpenReplay MCP server | Agent MCP Directory > Does OpenReplay have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/openreplay-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenReplay: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for OpenReplay (openreplay.com), so the connector had nothing to connect to. Ora's cached score for openreplay.com is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | OpenReplay | | --- | --- | | Domain | openreplay.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for openreplay.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for OpenReplay. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for openreplay.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for OpenReplay. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openreplay-com/index.md) ## Sources - [Ora score page for openreplay.com](https://ora.ai/score/openreplay.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where OpenReplay was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [OpenReplay website](https://openreplay.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Opentext MCP server | Agent MCP Directory" description: "Does Opentext have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/opentext-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Opentext MCP server | Agent MCP Directory > Does Opentext have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/opentext-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Opentext: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Opentext (opentext.com), so the connector had nothing to connect to. Ora's cached score for opentext.com is 30, grade D, read on 5 November 2026. The company was added from the GitHub MCP Registry. ## Fact sheet | Company | Opentext (registry title: Opentext Sdp Remote) | | --- | --- | | Domain | opentext.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | None found | | Tranco rank | 7,482 on the list of 4 November 2026 | | Ora score | 30, grade D; Ora scanned the domain on 4 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for opentext.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Opentext. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for opentext.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (com.opentext/sdp-remote-mcp) | | GitHub MCP Registry | Listed | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Opentext. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.opentext/sdp-remote-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/opentext-com/index.md) ## Sources - [Ora score page for opentext.com](https://ora.ai/score/opentext.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=opentext), read 4 November 2026 - [Opentext website](https://opentext.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpenWork MCP server | Agent MCP Directory" description: "OpenWork: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/openworklabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpenWork MCP server | Agent MCP Directory > OpenWork: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/openworklabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenWork: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for OpenWork at api.openworklabs.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | OpenWork (registry title: OpenWork MCP Gateway) | | --- | --- | | Domain | openworklabs.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 81, grade B; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for openworklabs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.openworklabs.com/mcp/agent | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,117 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:42Z https://api.openworklabs.com/mcp/agent sent initialize result auth-required (HTTP 401) 1275 ms - 20:03:54Z https://api.openworklabs.com/mcp/agent sent initialize result auth-required (HTTP 401) 1117 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.openworklabs.com/.well-known/oauth-protected-resource/mcp/agent", scope="mcp:read mcp:write offline_access" | | Protected resource metadata | api.openworklabs.com | | Authorization server metadata | app.openworklabs.com | | Registration endpoint | https://app.openworklabs.com/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.openworklabs.com/mcp/agent` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.openworklabs.com/.well-known/oauth-protected-resource/mcp/agent` to find the authorization server. 3. Register a client at the registration endpoint `https://app.openworklabs.com/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OpenWork. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: openworklabs.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.openworklabs/openwork | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openworklabs-com/index.md) ## Sources - [Ora score page for openworklabs.com](https://ora.ai/score/openworklabs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where OpenWork was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.openworklabs%2Fopenwork), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=openworklabs), read 4 November 2026 - [OpenWork website](https://openworklabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpenZeppelin MCP server | Agent MCP Directory" description: "OpenZeppelin has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/openzeppelin-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpenZeppelin MCP server | Agent MCP Directory > OpenZeppelin has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/openzeppelin-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenZeppelin: MCP server, CLI and agent surfaces Yes: OpenZeppelin runs a public MCP server at mcp.openzeppelin.com that listed 9 tools to a client with no credentials on 4 November 2026. Examples: cairo-erc20, cairo-erc721, cairo-erc1155. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for openzeppelin.com is 68, grade C, read on 5 November 2026. ## Fact sheet | Company | OpenZeppelin | | --- | --- | | Domain | openzeppelin.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 68, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for openzeppelin.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.openzeppelin.com/contracts/cairo/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | OpenZeppelin Cairo Contracts MCP Server 0.7.2 | | Capabilities | tools, resources, instructions | | Tools | 9 | | Resources | 9 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,241 ms over 1 attempt | ### Tools listed 9 tools - cairo-erc20 - cairo-erc721 - cairo-erc1155 - cairo-erc6909 - cairo-account - cairo-multisig - cairo-governor - cairo-vesting - cairo-custom ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:43Z https://mcp.openzeppelin.com/contracts/cairo/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1407 ms - 20:03:54Z https://mcp.openzeppelin.com/contracts/cairo/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1241 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.openzeppelin.com/contracts/cairo/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OpenZeppelin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/openzeppelin-com/index.md) ## Sources - [Ora score page for openzeppelin.com](https://ora.ai/score/openzeppelin.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where OpenZeppelin was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [OpenZeppelin website](https://openzeppelin.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Opsgenie MCP server | Agent MCP Directory" description: "Does Opsgenie have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/opsgenie-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Opsgenie MCP server | Agent MCP Directory > Does Opsgenie have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/opsgenie-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Opsgenie: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Opsgenie (opsgenie.com), so the connector had nothing to connect to. Ora's cached score for opsgenie.com is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Opsgenie (registry title: opsgenie.com) | | --- | --- | | Domain | opsgenie.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 3,583 on the list of 4 November 2026 | | Ora score | 60, grade C; Ora scanned the domain on 4 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for opsgenie.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Opsgenie. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for opsgenie.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Opsgenie. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/opsgenie-com/index.md) ## Sources - [Ora score page for opsgenie.com](https://ora.ai/score/opsgenie.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 October 2026, read from GET /api/score) - [Where Opsgenie was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Opsgenie website](https://opsgenie.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Opslane MCP server | Agent MCP Directory" description: "Does Opslane have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/opslane-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Opslane MCP server | Agent MCP Directory > Does Opslane have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/opslane-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Opslane: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Opslane (opslane.com), so the connector had nothing to connect to. Ora's cached score for opslane.com is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Opslane (registry title: opslane.com) | | --- | --- | | Domain | opslane.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 2 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for opslane.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Opslane. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for opslane.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Opslane. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/opslane-com/index.md) ## Sources - [Ora score page for opslane.com](https://ora.ai/score/opslane.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 October 2026, read from GET /api/leaderboard) - [Where Opslane was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Opslane website](https://opslane.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpsLevel MCP server | Agent MCP Directory" description: "OpsLevel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/opslevel-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpsLevel MCP server | Agent MCP Directory > OpsLevel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/opslevel-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpsLevel: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for OpsLevel at app.opslevel.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | OpsLevel | | --- | --- | | Domain | opslevel.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for opslevel.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.opslevel.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,144 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:43Z https://app.opslevel.com/mcp sent initialize result auth-required (HTTP 401) 1570 ms - 20:03:54Z https://app.opslevel.com/mcp sent initialize result auth-required (HTTP 401) 1144 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Doorkeeper", error="invalid_token", error_description="The access token is invalid", resource_metadata="https://app.opslevel.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | app.opslevel.com | | Authorization server metadata | app.opslevel.com | | Registration endpoint | https://app.opslevel.com/oauth/register | ### The sign-in route, step by step 1. Request `https://app.opslevel.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.opslevel.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.opslevel.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OpsLevel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.opslevel/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/opslevel-com/index.md) ## Sources - [Ora score page for opslevel.com](https://ora.ai/score/opslevel.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=opslevel), read 4 November 2026 - [OpsLevel website](https://opslevel.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Opsramp MCP server | Agent MCP Directory" description: "Does Opsramp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/opsramp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Opsramp MCP server | Agent MCP Directory > Does Opsramp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/opsramp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Opsramp: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Opsramp (opsramp.com), so the connector had nothing to connect to. Ora's cached score for opsramp.com is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Opsramp (registry title: opsramp.com) | | --- | --- | | Domain | opsramp.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for opsramp.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Opsramp. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for opsramp.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Opsramp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/opsramp-com/index.md) ## Sources - [Ora score page for opsramp.com](https://ora.ai/score/opsramp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Opsramp was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Optionsahoy MCP server | Agent MCP Directory" description: "Optionsahoy has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/optionsahoy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Optionsahoy MCP server | Agent MCP Directory > Optionsahoy has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/optionsahoy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Optionsahoy: MCP server, CLI and agent surfaces Yes: Optionsahoy runs a public MCP server at optionsahoy.com that listed 8 tools to a client with no credentials on 4 November 2026. Examples: amt\_iso\_optimize, nso\_calculate, rsu\_sell\_vs\_hold. It speaks streamable-http, protocol 2024-11-05. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Optionsahoy (registry title: AlvisoOculus Optionsahoy) | | --- | --- | | Domain | optionsahoy.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for optionsahoy.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://optionsahoy.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | OptionsAhoy 1.11.1 | | Capabilities | tools, resources, prompts | | Tools | 8 | | Resources | 9 | | Prompts | 8 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 244 ms over 1 attempt | ### Tools listed 8 tools - amt\_iso\_optimize - nso\_calculate - rsu\_sell\_vs\_hold - concentration\_analyze - protective\_put\_price - qsbs\_check - equity\_funding\_plan - rsu\_lot\_optimize ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:43Z https://optionsahoy.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 714 ms - 20:03:53Z https://optionsahoy.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 244 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://optionsahoy.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Optionsahoy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: optionsahoy.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: io.github.AlvisoOculus/optionsahoy-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/optionsahoy-com/index.md) ## Sources - [Where Optionsahoy was found](https://github.com/mcp/AlvisoOculus/optionsahoy-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=optionsahoy), read 4 November 2026 - [Optionsahoy website](https://optionsahoy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OpusClip MCP server | Agent MCP Directory" description: "OpusClip: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/opus-pro site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OpusClip MCP server | Agent MCP Directory > OpusClip: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/opus-pro Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpusClip: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for OpusClip at mcp.opus.pro answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | OpusClip | | --- | --- | | Domain | opus.pro | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 69, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for opus.pro, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.opus.pro/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 874 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:43Z https://mcp.opus.pro/mcp sent initialize result auth-required (HTTP 401) 852 ms - 20:03:54Z https://mcp.opus.pro/mcp sent initialize result auth-required (HTTP 401) 874 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", resource_metadata="https://mcp.opus.pro/mcp/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.opus.pro | | Authorization server metadata | focused-horizon-38.authkit.app | | Registration endpoint | https://focused-horizon-38.authkit.app/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.opus.pro/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.opus.pro/mcp/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://focused-horizon-38.authkit.app/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OpusClip. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/opus-pro/index.md) ## Sources - [Ora score page for opus.pro](https://ora.ai/score/opus.pro?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/score) - [OpusClip website](https://opus.pro), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ora MCP server | Agent MCP Directory" description: "Ora has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ora-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ora MCP server | Agent MCP Directory > Ora has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ora-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ora: MCP server, CLI and agent surfaces Yes: Ora runs a public MCP server at ora.ai that listed 18 tools to a client with no credentials on 4 November 2026. Examples: scan\_domain, get\_score, get\_leaderboard. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for ora.ai is 95, grade A+, read on 5 November 2026. ## Fact sheet | Company | Ora | | --- | --- | | Domain | ora.ai | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 95, grade A+; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ora.ai, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ora.ai/api/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | ora 1.38.0 | | Capabilities | tools, resources | | Tools | 18 | | Resources | 7 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,248 ms over 1 attempt | | Documentation | ora.ai | ### Tools listed 18 tools - scan\_domain - get\_score - get\_leaderboard - discover\_products - search\_capabilities - get\_verification\_challenge - submit\_feedback - send\_feedback - submit\_check\_feedback - get\_feedback - list\_skills - get\_skill - list\_checks - run\_checks - ask - run\_journey - get\_journey\_run - generate\_agent\_files ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:44Z https://ora.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1587 ms - 20:03:55Z https://ora.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1248 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://ora.ai/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ora. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: ora.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: ora.ai/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: ora.ai/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | ## About this row Ora is a row like every other company here. Its own discovery file at `ora.ai/.well-known/mcp.json` names `https://ora.ai/api/mcp`, and the connector verified that endpoint by connecting. Ora's server is not in the official MCP Registry under its own namespace, and the Smithery address given for it returned 404 when read on 4 November 2026. Ora's own cached score for ora.ai is in the fact sheet. Ora is also the scanner this directory recommends for testing an MCP server. [Why, where it falls short and what else exists](https://agentmcpdirectory.com/test-your-mcp-server/); [the 18 tools above, described](https://agentmcpdirectory.com/ora-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ora-ai/index.md) ## Sources - [Ora MCP discovery file](https://ora.ai/.well-known/mcp.json?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ora score page for ora.ai](https://ora.ai/score/ora.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Ora website](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Orangescrum MCP server | Agent MCP Directory" description: "Orangescrum: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/orangescrum-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Orangescrum MCP server | Agent MCP Directory > Orangescrum: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/orangescrum-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Orangescrum: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Orangescrum at mcp.orangescrum.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Orangescrum (registry title: Orangescrum MCP Server) | | --- | --- | | Domain | orangescrum.com | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 81, grade B; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for orangescrum.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.orangescrum.com/mcp/partner | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,046 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:44Z https://mcp.orangescrum.com/mcp/partner sent initialize result auth-required (HTTP 401) 1354 ms - 20:03:55Z https://mcp.orangescrum.com/mcp/partner sent initialize result auth-required (HTTP 401) 1046 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="MCP", error="invalid_request", error_description="Bearer token required", resource_metadata="https://mcp.orangescrum.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.orangescrum.com | | Authorization server metadata | mcp.orangescrum.com | | Registration endpoint | https://mcp.orangescrum.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.orangescrum.com/mcp/partner` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.orangescrum.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.orangescrum.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Orangescrum. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.orangescrum.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.orangescrum/orangescrum-mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/orangescrum-com/index.md) ## Sources - [Ora score page for orangescrum.com](https://ora.ai/score/orangescrum.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=orangescrum), read 4 November 2026 - [Orangescrum website](https://orangescrum.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OrgGen AI MCP server | Agent MCP Directory" description: "OrgGen AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/orggen-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OrgGen AI MCP server | Agent MCP Directory > OrgGen AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/orggen-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # OrgGen AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for OrgGen AI at www.orggen.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | OrgGen AI | | --- | --- | | Domain | orggen.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for orggen.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.orggen.ai/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 712 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:44Z https://www.orggen.ai/api/mcp sent initialize result auth-required (HTTP 401) 925 ms - 20:03:54Z https://www.orggen.ai/api/mcp sent initialize result auth-required (HTTP 401) 712 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | www.orggen.ai | | Authorization server metadata | www.orggen.ai | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://www.orggen.ai/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.orggen.ai/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OrgGen AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.orggen/orggen | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/orggen-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=orggen), read 4 November 2026 - [OrgGen AI website](https://orggen.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Orthogonal MCP server | Agent MCP Directory" description: "Does Orthogonal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/orthogonal-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Orthogonal MCP server | Agent MCP Directory > Does Orthogonal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/orthogonal-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Orthogonal: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Orthogonal (orthogonal.com), so the connector had nothing to connect to. Ora's cached score for orthogonal.com is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Orthogonal (registry title: orthogonal.com) | | --- | --- | | Domain | orthogonal.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for orthogonal.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Orthogonal. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for orthogonal.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Orthogonal. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/orthogonal-com/index.md) ## Sources - [Ora score page for orthogonal.com](https://ora.ai/score/orthogonal.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Orthogonal was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Orthogonal website](https://orthogonal.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Osmosis MCP server | Agent MCP Directory" description: "Does Osmosis have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/osmosis-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Osmosis MCP server | Agent MCP Directory > Does Osmosis have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/osmosis-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Osmosis: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Osmosis (osmosis.ai), so the connector had nothing to connect to. Ora's cached score for osmosis.ai is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Osmosis (registry title: osmosis.ai) | | --- | --- | | Domain | osmosis.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 24 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for osmosis.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Osmosis. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for osmosis.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Osmosis. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/osmosis-ai/index.md) ## Sources - [Ora score page for osmosis.ai](https://ora.ai/score/osmosis.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 October 2026, read from GET /api/leaderboard) - [Where Osmosis was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Osmosis website](https://osmosis.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Otter.ai MCP server | Agent MCP Directory" description: "Otter.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/otter-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Otter.ai MCP server | Agent MCP Directory > Otter.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/otter-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Otter.ai: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Otter.ai at mcp.otter.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Otter.ai | | --- | --- | | Domain | otter.ai | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 7,654 on the list of 4 November 2026 | | Ora score | 57, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for otter.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.otter.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,532 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:15Z https://mcp.otter.ai/mcp sent initialize result auth-required (HTTP 401) 2293 ms - 20:01:54Z https://mcp.otter.ai/mcp sent initialize result auth-required (HTTP 401) 2532 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.otter.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.otter.ai | | Authorization server metadata | otter.ai | | Registration endpoint | https://otter.ai/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.otter.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.otter.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://otter.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Otter.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: otter.ai/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/otter-ai/index.md) ## Sources - [Ora score page for otter.ai](https://ora.ai/score/otter.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/score) - [Where Otter.ai was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Otter.ai website](https://otter.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Outlit MCP server | Agent MCP Directory" description: "Outlit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/outlit-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Outlit MCP server | Agent MCP Directory > Outlit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/outlit-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Outlit: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Outlit at mcp.outlit.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Outlit | | --- | --- | | Domain | outlit.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 85, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for outlit.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.outlit.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,012 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:46Z https://mcp.outlit.ai/mcp sent initialize result auth-required (HTTP 401) 1788 ms - 20:03:55Z https://mcp.outlit.ai/mcp sent initialize result auth-required (HTTP 401) 1012 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Outlit MCP requires an Authorization: Bearer token. Use the workspace MCP URL and complete OAuth in your MCP client. Legacy or headless clients that do not support OAuth must send their configured bearer credential.", resource_metadata="https://mcp.outlit.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.outlit.ai | | Authorization server metadata | clerk.outlit.ai | | Registration endpoint | https://clerk.outlit.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.outlit.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.outlit.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.outlit.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Outlit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: docs.outlit.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: outlit.ai/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Found: outlit.ai/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.outlit/outlit | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/outlit-ai/index.md) ## Sources - [Ora score page for outlit.ai](https://ora.ai/score/outlit.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Outlit was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.outlit%2Foutlit), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=outlit), read 4 November 2026 - [Outlit website](https://outlit.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Outset MCP server | Agent MCP Directory" description: "Outset: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/outset-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Outset MCP server | Agent MCP Directory > Outset: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/outset-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Outset: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Outset at api.outset.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Outset | | --- | --- | | Domain | outset.ai | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 51, grade C; Ora scanned the domain on 14 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for outset.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.outset.ai/mcp/ | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,062 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:45Z https://api.outset.ai/mcp/ sent initialize result auth-required (HTTP 401) 1154 ms - 20:03:56Z https://api.outset.ai/mcp/ sent initialize result auth-required (HTTP 401) 1062 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Outset", resource_metadata="https://api.outset.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | api.outset.ai | | Authorization server metadata | api.outset.ai | | Registration endpoint | https://api.outset.ai/users/oauth/register/ | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.outset.ai/mcp/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.outset.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.outset.ai/users/oauth/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Outset. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.outset/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/outset-ai/index.md) ## Sources - [Ora score page for outset.ai](https://ora.ai/score/outset.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 September 2026, read from GET /api/leaderboard) - [Where Outset was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.outset%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=outset), read 4 November 2026 - [Outset website](https://outset.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OutSystems MCP server | Agent MCP Directory" description: "Does OutSystems have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/outsystems-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OutSystems MCP server | Agent MCP Directory > Does OutSystems have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/outsystems-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OutSystems: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for OutSystems (outsystems.com), so the connector had nothing to connect to. Ora's cached score for outsystems.com is 63, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | OutSystems (registry title: outsystems.com) | | --- | --- | | Domain | outsystems.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for outsystems.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for OutSystems. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for outsystems.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for OutSystems. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/outsystems-com/index.md) ## Sources - [Ora score page for outsystems.com](https://ora.ai/score/outsystems.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where OutSystems was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [OutSystems website](https://outsystems.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OVHcloud MCP server | Agent MCP Directory" description: "Does OVHcloud have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ovhcloud-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OVHcloud MCP server | Agent MCP Directory > Does OVHcloud have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/ovhcloud-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OVHcloud: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for OVHcloud (ovhcloud.com), so the connector had nothing to connect to. Ora's cached score for ovhcloud.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | OVHcloud | | --- | --- | | Domain | ovhcloud.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 1,098 on the list of 4 November 2026 | | Ora score | 58, grade C; Ora scanned the domain on 1 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ovhcloud.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for OVHcloud. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ovhcloud.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | Listed (com.ovhcloud.eu.mcp/api) | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for OVHcloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.ovhcloud.eu.mcp/api | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ovhcloud-com/index.md) ## Sources - [Ora score page for ovhcloud.com](https://ora.ai/score/ovhcloud.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 September 2026, read from GET /api/score) - [Where OVHcloud was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.ovhcloud.eu.mcp%2Fapi), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ovhcloud), read 4 November 2026 - [OVHcloud website](https://ovhcloud.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "OwlCAD MCP server | Agent MCP Directory" description: "OwlCAD: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/owlcad-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # OwlCAD MCP server | Agent MCP Directory > OwlCAD: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/owlcad-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # OwlCAD: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for OwlCAD at mcp.owlcad.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | OwlCAD | | --- | --- | | Domain | owlcad.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for owlcad.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.owlcad.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 559 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:45Z https://mcp.owlcad.com sent initialize result auth-required (HTTP 401) 998 ms - 20:03:55Z https://mcp.owlcad.com sent initialize result auth-required (HTTP 401) 559 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="owlcad", resource_metadata="https://mcp.owlcad.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.owlcad.com | | Authorization server metadata | mcp.owlcad.com | | Registration endpoint | https://mcp.owlcad.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.owlcad.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.owlcad.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.owlcad.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for OwlCAD. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: owlcad.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.owlcad/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/owlcad-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=owlcad), read 4 November 2026 - [OwlCAD website](https://owlcad.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Oximy MCP server | Agent MCP Directory" description: "Oximy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/oximy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Oximy MCP server | Agent MCP Directory > Oximy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/oximy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Oximy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Oximy; the connector's guess at mcp.oximy.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Oximy (registry title: oximy.com) | | --- | --- | | Domain | oximy.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 44, grade D; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for oximy.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.oximy.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,092 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:46Z https://mcp.oximy.com/mcp sent initialize result auth-required (HTTP 401) 1533 ms - 20:03:56Z https://mcp.oximy.com/mcp sent initialize result auth-required (HTTP 401) 1092 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.oximy.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.oximy.com | | Authorization server metadata | clerk.oximy.com | | Registration endpoint | https://clerk.oximy.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.oximy.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.oximy.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.oximy.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Oximy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/oximy-com/index.md) ## Sources - [Ora score page for oximy.com](https://ora.ai/score/oximy.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/leaderboard) - [Where Oximy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Oximy website](https://oximy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Paddle MCP server | Agent MCP Directory" description: "Paddle: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/paddle-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Paddle MCP server | Agent MCP Directory > Paddle: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/paddle-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Paddle: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Paddle at mcp.paddle.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Paddle | | --- | --- | | Domain | paddle.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 69, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for paddle.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.paddle.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 201 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:45Z https://mcp.paddle.com/mcp sent initialize result auth-required (HTTP 401) 510 ms - 20:03:55Z https://mcp.paddle.com/mcp sent initialize result auth-required (HTTP 401) 201 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="unauthorized", error_description="Authorization needed", resource_metadata="https://mcp.paddle.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.paddle.com | | Authorization server metadata | id.paddle.com | | Registration endpoint | https://id.paddle.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.paddle.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.paddle.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://id.paddle.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Paddle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.paddle/mcp, com.paddle/mcp-sandbox | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/paddle-com/index.md) ## Sources - [Ora score page for paddle.com](https://ora.ai/score/paddle.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Paddle was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.paddle%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=paddle), read 4 November 2026 - [Paddle website](https://paddle.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Padlet MCP server | Agent MCP Directory" description: "Padlet: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/padlet-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Padlet MCP server | Agent MCP Directory > Padlet: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/padlet-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Padlet: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Padlet at mcp.padlet.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Padlet | | --- | --- | | Domain | padlet.com | | Category | Education (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,732 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 2 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for padlet.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.padlet.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 624 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:59Z https://mcp.padlet.com/ sent initialize result auth-required (HTTP 401) 619 ms - 20:01:35Z https://mcp.padlet.com/ sent initialize result auth-required (HTTP 401) 624 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="padlet_mcp", error="invalid_token", error_description="Authorization header with Bearer token is required", as_uri="https://mcp.padlet.com/.well-known/oauth-authorization-server", resource_metadata="https://mcp.padlet.com/.well-known/oauth-protected-resource", resource="https://mcp.padlet.com" | | Protected resource metadata | mcp.padlet.com | | Authorization server metadata | mcp.padlet.com | | Registration endpoint | https://mcp.padlet.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.padlet.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.padlet.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.padlet.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Padlet. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: padlet.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: padlet.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: padlet.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.padlet/padlet | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/padlet-com/index.md) ## Sources - [Ora score page for padlet.com](https://ora.ai/score/padlet.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=padlet), read 4 November 2026 - [Padlet website](https://padlet.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pageaudit MCP server | Agent MCP Directory" description: "Pageaudit has an open MCP server with 62 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pageaudit-online site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pageaudit MCP server | Agent MCP Directory > Pageaudit has an open MCP server with 62 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pageaudit-online Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pageaudit: MCP server, CLI and agent surfaces Yes: Pageaudit runs a public MCP server at pageaudit.online that listed 62 tools to a client with no credentials on 4 November 2026. Examples: list\_sites, add\_site, get\_site. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Pageaudit | | --- | --- | | Domain | pageaudit.online | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for pageaudit.online when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://pageaudit.online/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | PageAudit fb0c5518 | | Capabilities | tools, prompts | | Tools | 62 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,318 ms over 1 attempt | ### Tools listed 62 tools; the first 40 names are recorded - list\_sites - add\_site - get\_site - search\_console - track\_search\_queries - connect\_search\_console - sync\_search\_console - disconnect\_search\_console - prompt\_allowance - generate\_fix\_prompt - generate\_domain\_fix\_prompt - generate\_site\_fix\_prompt - get\_fix\_prompt - list\_audit\_fix\_prompts - list\_domain\_fix\_prompts - list\_site\_fix\_prompts - weekly\_site\_report - save\_weekly\_site\_report - weekly\_site\_report\_history - ai\_search\_visibility - ai\_search\_history - save\_ai\_search\_queries - journeys - configure\_journeys - connection\_review - review\_connection - cancel\_connection\_review - domain\_portfolio - preview\_domain\_alerts - apply\_domain\_alerts - domain\_status - check\_domain - set\_domain\_expiry - configure\_domain\_dns - configure\_domain\_monitor - domain\_history - acknowledge\_domain\_event - audit\_site - check\_ai\_access - api\_index ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:47Z https://pageaudit.online/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2491 ms - 20:03:58Z https://pageaudit.online/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2318 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://pageaudit.online/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pageaudit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: pageaudit.online (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pageaudit-online/index.md) ## Sources - [Pageaudit website](https://pageaudit.online), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PageProofer MCP server | Agent MCP Directory" description: "PageProofer: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/pageproofer-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PageProofer MCP server | Agent MCP Directory > PageProofer: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/pageproofer-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PageProofer: MCP server, CLI and agent surfaces Not counted. The endpoint listed for PageProofer at app.pageproofer.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | PageProofer | | --- | --- | | Domain | pageproofer.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for pageproofer.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.pageproofer.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,917 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:47Z https://app.pageproofer.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 2049 ms - 20:03:58Z https://app.pageproofer.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1917 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | Bearer realm="mcp", error="invalid_token" | ### The sign-in route, step by step 1. Request `https://app.pageproofer.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PageProofer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pageproofer/pageproofer | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pageproofer-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pageproofer), read 4 November 2026 - [PageProofer website](https://pageproofer.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PagerDuty MCP server | Agent MCP Directory" description: "Does PagerDuty have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pagerduty-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PagerDuty MCP server | Agent MCP Directory > Does PagerDuty have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pagerduty-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PagerDuty: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for PagerDuty (pagerduty.com), so the connector had nothing to connect to. Ora's cached score for pagerduty.com is 71, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | PagerDuty | | --- | --- | | Domain | pagerduty.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 71, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pagerduty.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for PagerDuty. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pagerduty.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for PagerDuty. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pagerduty-com/index.md) ## Sources - [Ora score page for pagerduty.com](https://ora.ai/score/pagerduty.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where PagerDuty was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [PagerDuty website](https://pagerduty.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pageree MCP server | Agent MCP Directory" description: "Pageree: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM." canonical: https://agentmcpdirectory.com/directory/pageree-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pageree MCP server | Agent MCP Directory > Pageree: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM. Source: https://agentmcpdirectory.com/directory/pageree-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pageree: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Pageree at mcp.pageree.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Pageree | | --- | --- | | Domain | pageree.com | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for pageree.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.pageree.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 473 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:46Z https://mcp.pageree.com/ sent initialize result auth-required (HTTP 401) 798 ms - 20:03:57Z https://mcp.pageree.com/ sent initialize result auth-required (HTTP 401) 473 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.pageree.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.pageree.com | | Authorization server metadata | mcp.pageree.com | | Registration endpoint | https://mcp.pageree.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.pageree.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.pageree.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.pageree.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pageree. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pageree/landing-pages | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pageree-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pageree), read 4 November 2026 - [Pageree website](https://pageree.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PagerTree MCP server | Agent MCP Directory" description: "Does PagerTree have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pagertree-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PagerTree MCP server | Agent MCP Directory > Does PagerTree have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pagertree-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PagerTree: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for PagerTree (pagertree.com), so the connector had nothing to connect to. Ora's cached score for pagertree.com is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | PagerTree (registry title: pagertree.com) | | --- | --- | | Domain | pagertree.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 7 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pagertree.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for PagerTree. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pagertree.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for PagerTree. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pagertree-com/index.md) ## Sources - [Ora score page for pagertree.com](https://ora.ai/score/pagertree.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 August 2026, read from GET /api/leaderboard) - [Where PagerTree was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [PagerTree website](https://pagertree.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PaidSync.ai MCP server | Agent MCP Directory" description: "PaidSync.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/paidsync-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PaidSync.ai MCP server | Agent MCP Directory > PaidSync.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/paidsync-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # PaidSync.ai: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for PaidSync.ai at mcp.paidsync.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | PaidSync.ai | | --- | --- | | Domain | paidsync.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for paidsync.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.paidsync.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,011 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:47Z https://mcp.paidsync.ai/mcp sent initialize result auth-required (HTTP 401) 1180 ms - 20:03:57Z https://mcp.paidsync.ai/mcp sent initialize result auth-required (HTTP 401) 1011 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.paidsync.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.paidsync.ai | | Authorization server metadata | api.paidsync.ai | | Registration endpoint | https://api.paidsync.ai/register | ### The sign-in route, step by step 1. Request `https://mcp.paidsync.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.paidsync.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.paidsync.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PaidSync.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: paidsync.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/paidsync-ai/index.md) ## Sources - [PaidSync.ai website](https://paidsync.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PakBus MCP server | Agent MCP Directory" description: "PakBus has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pakbus-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PakBus MCP server | Agent MCP Directory > PakBus has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pakbus-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # PakBus: MCP server, CLI and agent surfaces Yes: PakBus runs a public MCP server at pakbus.app that listed 6 tools to a client with no credentials on 4 November 2026. Examples: list\_cities, find\_places, plan\_journey. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | PakBus | | --- | --- | | Domain | pakbus.app | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for pakbus.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://pakbus.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | pakbus 1.0.0 | | Capabilities | tools, resources | | Tools | 6 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 170 ms over 1 attempt | ### Tools listed 6 tools - list\_cities - find\_places - plan\_journey - place\_departures - service\_notices - route\_details ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:47Z https://pakbus.app/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 396 ms - 20:03:57Z https://pakbus.app/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 170 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://pakbus.app/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PakBus. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.pakbus/pakbus | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pakbus-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pakbus), read 4 November 2026 - [PakBus website](https://pakbus.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Palenca MCP server | Agent MCP Directory" description: "Does Palenca have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/palenca-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Palenca MCP server | Agent MCP Directory > Does Palenca have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/palenca-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Palenca: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Palenca (palenca.com), so the connector had nothing to connect to. Ora's cached score for palenca.com is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Palenca (registry title: palenca.com) | | --- | --- | | Domain | palenca.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for palenca.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Palenca. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for palenca.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Palenca. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/palenca-com/index.md) ## Sources - [Ora score page for palenca.com](https://ora.ai/score/palenca.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Palenca was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Palisade MCP server | Agent MCP Directory" description: "Palisade: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/palisade-email site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Palisade MCP server | Agent MCP Directory > Palisade: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/palisade-email Site: Agent MCP Directory Last reviewed: 2026-11-05 # Palisade: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Palisade at api.palisade.email answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Palisade | | --- | --- | | Domain | palisade.email | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 87, grade A; Ora scanned the domain on 11 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for palisade.email, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.palisade.email/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,410 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:48Z https://api.palisade.email/mcp sent initialize result auth-required (HTTP 401) 1598 ms - 20:03:58Z https://api.palisade.email/mcp sent initialize result auth-required (HTTP 401) 1410 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.palisade.email/.well-known/oauth-protected-resource" | | Protected resource metadata | api.palisade.email | | Authorization server metadata | accounts.palisade.email | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.palisade.email/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.palisade.email/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Palisade. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: email.palisade/palisade | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/palisade-email/index.md) ## Sources - [Ora score page for palisade.email](https://ora.ai/score/palisade.email?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=palisade), read 4 November 2026 - [Palisade website](https://palisade.email), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pally MCP server | Agent MCP Directory" description: "Pally: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pally-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pally MCP server | Agent MCP Directory > Pally: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pally-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pally: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Pally at agent.pally.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Pally | | --- | --- | | Domain | pally.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 50, grade C; Ora scanned the domain on 7 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pally.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agent.pally.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,238 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:48Z https://agent.pally.com/mcp sent initialize result auth-required (HTTP 401) 1319 ms - 20:03:58Z https://agent.pally.com/mcp sent initialize result auth-required (HTTP 401) 1238 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://agent.pally.com/.well-known/oauth-protected-resource" | | Protected resource metadata | agent.pally.com | | Authorization server metadata | agent.pally.com | | Registration endpoint | https://agent.pally.com/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://agent.pally.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://agent.pally.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://agent.pally.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pally. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pally/pally | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pally-com/index.md) ## Sources - [Ora score page for pally.com](https://ora.ai/score/pally.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 September 2026, read from GET /api/leaderboard) - [Where Pally was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.pally%2Fpally), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pally), read 4 November 2026 - [Pally website](https://pally.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PandaDoc MCP server | Agent MCP Directory" description: "PandaDoc: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Legal & Compliance." canonical: https://agentmcpdirectory.com/directory/pandadoc-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PandaDoc MCP server | Agent MCP Directory > PandaDoc: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Legal & Compliance. Source: https://agentmcpdirectory.com/directory/pandadoc-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PandaDoc: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for PandaDoc at mcp.pandadoc.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | PandaDoc (registry title: PandaDoc MCP Server) | | --- | --- | | Domain | pandadoc.com | | Category | Legal & Compliance (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 78, grade B; Ora scanned the domain on 14 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pandadoc.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.pandadoc.com/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,516 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:49Z https://mcp.pandadoc.com/v1/mcp sent initialize result auth-required (HTTP 401) 1603 ms - 20:03:58Z https://mcp.pandadoc.com/v1/mcp sent initialize result auth-required (HTTP 401) 1516 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.pandadoc.com/.well-known/oauth-protected-resource/v1/mcp" | | Protected resource metadata | mcp.pandadoc.com | | Authorization server metadata | mcp.pandadoc.com | | Registration endpoint | https://mcp.pandadoc.com/register | ### The sign-in route, step by step 1. Request `https://mcp.pandadoc.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.pandadoc.com/.well-known/oauth-protected-resource/v1/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.pandadoc.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PandaDoc. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pandadoc.mcp/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pandadoc-com/index.md) ## Sources - [Ora score page for pandadoc.com](https://ora.ai/score/pandadoc.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 October 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pandadoc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pangolin MCP server | Agent MCP Directory" description: "Does Pangolin have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pangolin-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pangolin MCP server | Agent MCP Directory > Does Pangolin have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pangolin-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pangolin: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Pangolin (pangolin.net), so the connector had nothing to connect to. Ora's cached score for pangolin.net is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Pangolin (registry title: pangolin.net) | | --- | --- | | Domain | pangolin.net | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pangolin.net, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Pangolin. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pangolin.net, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Pangolin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pangolin-net/index.md) ## Sources - [Ora score page for pangolin.net](https://ora.ai/score/pangolin.net?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Pangolin was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Pangolin website](https://pangolin.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pantheon MCP server | Agent MCP Directory" description: "Pantheon: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pantheon-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pantheon MCP server | Agent MCP Directory > Pantheon: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pantheon-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pantheon: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Pantheon; the connector's guess at mcp.pantheon.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Pantheon | | --- | --- | | Domain | pantheon.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 61, grade C; Ora scanned the domain on 25 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pantheon.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.pantheon.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,116 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:48Z https://mcp.pantheon.io/mcp sent initialize result auth-required (HTTP 401) 657 ms - 20:03:59Z https://mcp.pantheon.io/mcp sent initialize result auth-required (HTTP 401) 1116 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="missing bearer token", resource_metadata="https://mcp.pantheon.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.pantheon.io | | Authorization server metadata | mcp.pantheon.io | ### The sign-in route, step by step 1. Request `https://mcp.pantheon.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://mcp.pantheon.io/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pantheon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pantheon-io/index.md) ## Sources - [Ora score page for pantheon.io](https://ora.ai/score/pantheon.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 September 2026, read from GET /api/leaderboard) - [Where Pantheon was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Pantheon website](https://pantheon.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Parad1gm MCP server | Agent MCP Directory" description: "Parad1gm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/parad1gm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Parad1gm MCP server | Agent MCP Directory > Parad1gm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/parad1gm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Parad1gm: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Parad1gm at prism.parad1gm.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Parad1gm (registry title: Prism by Parad1gm: Contract Deadlines and Critical Dates) | | --- | --- | | Domain | parad1gm.com | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for parad1gm.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://prism.parad1gm.com/api/prism-mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,129 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:49Z https://prism.parad1gm.com/api/prism-mcp sent initialize result auth-required (HTTP 401) 1302 ms - 20:03:59Z https://prism.parad1gm.com/api/prism-mcp sent initialize result auth-required (HTTP 401) 1129 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://prism.parad1gm.com/.well-known/oauth-protected-resource/api/prism-mcp" | | Protected resource metadata | prism.parad1gm.com | | Authorization server metadata | prism.parad1gm.com | | Registration endpoint | https://prism.parad1gm.com/api/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://prism.parad1gm.com/api/prism-mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://prism.parad1gm.com/.well-known/oauth-protected-resource/api/prism-mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://prism.parad1gm.com/api/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Parad1gm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.parad1gm/prism | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/parad1gm-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=parad1gm), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ParadeDB MCP server | Agent MCP Directory" description: "Does ParadeDB have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/paradedb-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ParadeDB MCP server | Agent MCP Directory > Does ParadeDB have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/paradedb-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ParadeDB: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for ParadeDB (paradedb.com), so the connector had nothing to connect to. Ora's cached score for paradedb.com is 76, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | ParadeDB (registry title: paradedb.com) | | --- | --- | | Domain | paradedb.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 76, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for paradedb.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for ParadeDB. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for paradedb.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for ParadeDB. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: paradedb.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/paradedb-com/index.md) ## Sources - [Ora score page for paradedb.com](https://ora.ai/score/paradedb.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where ParadeDB was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ParadeDB website](https://paradedb.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Parallel MCP server | Agent MCP Directory" description: "Parallel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/parallel-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Parallel MCP server | Agent MCP Directory > Parallel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/parallel-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Parallel: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Parallel at task-mcp.parallel.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Parallel (registry title: Parallel Web Systems) | | --- | --- | | Domain | parallel.ai | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 90, grade A; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for parallel.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://task-mcp.parallel.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 561 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:48Z https://task-mcp.parallel.ai/mcp sent initialize result auth-required (HTTP 401) 632 ms - 20:03:59Z https://task-mcp.parallel.ai/mcp sent initialize result auth-required (HTTP 401) 561 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="main", resource_metadata="https://task-mcp.parallel.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | task-mcp.parallel.ai | | Authorization server metadata | platform.parallel.ai | | Registration endpoint | https://platform.parallel.ai/getKeys/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://task-mcp.parallel.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://task-mcp.parallel.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://platform.parallel.ai/getKeys/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Parallel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: parallel.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.parallel/search-mcp, ai.parallel/task-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/parallel-ai/index.md) ## Sources - [Ora score page for parallel.ai](https://ora.ai/score/parallel.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/leaderboard) - [Where Parallel was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=parallel), read 4 November 2026 - [Parallel website](https://parallel.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Parea MCP server | Agent MCP Directory" description: "Does Parea have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/parea-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Parea MCP server | Agent MCP Directory > Does Parea have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/parea-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Parea: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Parea (parea.ai), so the connector had nothing to connect to. Ora's cached score for parea.ai is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Parea (registry title: parea.ai) | | --- | --- | | Domain | parea.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 11 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for parea.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Parea. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for parea.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Parea. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/parea-ai/index.md) ## Sources - [Ora score page for parea.ai](https://ora.ai/score/parea.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 September 2026, read from GET /api/leaderboard) - [Where Parea was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Parse MCP server | Agent MCP Directory" description: "Does Parse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/parse-bot site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Parse MCP server | Agent MCP Directory > Does Parse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/parse-bot Site: Agent MCP Directory Last reviewed: 2026-11-05 # Parse: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Parse (parse.bot), so the connector had nothing to connect to. Ora's cached score for parse.bot is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Parse (registry title: parse.bot) | | --- | --- | | Domain | parse.bot | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for parse.bot, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Parse. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for parse.bot, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Parse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/parse-bot/index.md) ## Sources - [Ora score page for parse.bot](https://ora.ai/score/parse.bot?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Parse was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Parse website](https://parse.bot), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Parse.ly MCP server | Agent MCP Directory" description: "Parse.ly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/parsely-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Parse.ly MCP server | Agent MCP Directory > Parse.ly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/parsely-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Parse.ly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Parse.ly at dash.parsely.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Parse.ly (registry title: Parse.ly MCP) | | --- | --- | | Domain | parsely.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,281 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for parsely.com when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://dash.parsely.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 931 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:02Z https://dash.parsely.com/mcp sent initialize result auth-required (HTTP 401) 803 ms - 20:01:38Z https://dash.parsely.com/mcp sent initialize result auth-required (HTTP 401) 931 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://dash.parsely.com/.well-known/oauth-protected-resource/mcp", scope="mcp" | | Protected resource metadata | dash.parsely.com | | Authorization server metadata | dash.parsely.com | | Registration endpoint | https://dash.parsely.com/o/register/ | ### The sign-in route, step by step 1. Request `https://dash.parsely.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://dash.parsely.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://dash.parsely.com/o/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Parse.ly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: parsely.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.parsely.dash/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/parsely-com/index.md) ## Sources - [Where Parse.ly was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.parsely.dash%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=parsely), read 4 November 2026 - [Parse.ly website](https://parsely.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PatchDesign.AI MCP server | Agent MCP Directory" description: "PatchDesign.AI has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/patchdesign-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PatchDesign.AI MCP server | Agent MCP Directory > PatchDesign.AI has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/patchdesign-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # PatchDesign.AI: MCP server, CLI and agent surfaces Yes: PatchDesign.AI runs a public MCP server at patchdesign.ai that listed 5 tools to a client with no credentials on 4 November 2026. Examples: quote\_patch, design\_patch, edit\_patch. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | PatchDesign.AI | | --- | --- | | Domain | patchdesign.ai | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for patchdesign.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://patchdesign.ai/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | patchdesign-ai 1.0.1 | | Capabilities | tools, resources | | Tools | 5 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,222 ms over 1 attempt | ### Tools listed 5 tools - quote\_patch - design\_patch - edit\_patch - order\_link - sign\_in\_link ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:52Z https://patchdesign.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 3339 ms - 20:04:01Z https://patchdesign.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 2222 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://patchdesign.ai/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PatchDesign.AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.patchdesign/patch-designer | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/patchdesign-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=patchdesign), read 4 November 2026 - [PatchDesign.AI website](https://patchdesign.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pathrule MCP server | Agent MCP Directory" description: "Pathrule: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/pathrule-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pathrule MCP server | Agent MCP Directory > Pathrule: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/pathrule-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pathrule: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Pathrule at cloud.pathrule.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Pathrule | | --- | --- | | Domain | pathrule.io | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for pathrule.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://cloud.pathrule.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 169 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:49Z https://cloud.pathrule.io/mcp sent initialize result auth-required (HTTP 401) 581 ms - 20:03:59Z https://cloud.pathrule.io/mcp sent initialize result auth-required (HTTP 401) 169 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://cloud.pathrule.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | cloud.pathrule.io | | Authorization server metadata | cloud.pathrule.io | | Registration endpoint | https://cloud.pathrule.io/oauth/register | ### The sign-in route, step by step 1. Request `https://cloud.pathrule.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://cloud.pathrule.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://cloud.pathrule.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pathrule. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pathrule-io/index.md) ## Sources - [Pathrule website](https://pathrule.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PAVE MCP server | Agent MCP Directory" description: "PAVE: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pavecfi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PAVE MCP server | Agent MCP Directory > PAVE: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pavecfi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PAVE: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for PAVE at api.pavecfi.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | PAVE | | --- | --- | | Domain | pavecfi.com | | Category | Travel & Hospitality (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for pavecfi.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.pavecfi.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 965 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:50Z https://api.pavecfi.com/mcp sent initialize result auth-required (HTTP 401) 1486 ms - 20:04:00Z https://api.pavecfi.com/mcp sent initialize result auth-required (HTTP 401) 965 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.pavecfi.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.pavecfi.com | | Authorization server metadata | hkynbkffqrucmuzjsdto.supabase.co | | Registration endpoint | https://hkynbkffqrucmuzjsdto.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://api.pavecfi.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.pavecfi.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://hkynbkffqrucmuzjsdto.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PAVE. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pavecfi/pave | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pavecfi-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pavecfi), read 4 November 2026 - [PAVE website](https://pavecfi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Payload MCP server | Agent MCP Directory" description: "Does Payload have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/payloadcms-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Payload MCP server | Agent MCP Directory > Does Payload have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/payloadcms-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Payload: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Payload (payloadcms.com), so the connector had nothing to connect to. Ora's cached score for payloadcms.com is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Payload (registry title: payloadcms.com) | | --- | --- | | Domain | payloadcms.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for payloadcms.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Payload. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for payloadcms.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Payload. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/payloadcms-com/index.md) ## Sources - [Ora score page for payloadcms.com](https://ora.ai/score/payloadcms.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Payload was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Payload website](https://payloadcms.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PayPal MCP server | Agent MCP Directory" description: "PayPal: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/paypal-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PayPal MCP server | Agent MCP Directory > PayPal: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/paypal-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PayPal: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for PayPal at mcp.paypal.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | PayPal | | --- | --- | | Domain | paypal.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 174 on the list of 4 November 2026 | | Ora score | 70, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for paypal.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.paypal.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 101 ms over 1 attempt | | Documentation | developer.paypal.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:52Z https://mcp.paypal.com/mcp sent initialize result auth-required (HTTP 401) 180 ms - 20:01:27Z https://mcp.paypal.com/mcp sent initialize result auth-required (HTTP 401) 101 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.paypal.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.paypal.com | | Authorization server metadata | mcp.paypal.com | | Registration endpoint | https://mcp.paypal.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.paypal.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.paypal.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.paypal.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PayPal. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.paypal.mcp/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/paypal-com/index.md) ## Sources - [PayPal MCP documentation](https://developer.paypal.com/tools/mcp-server/), read 4 November 2026 - [Ora score page for paypal.com](https://ora.ai/score/paypal.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=paypal), read 4 November 2026 - [PayPal website](https://paypal.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Paytm MCP server | Agent MCP Directory" description: "Paytm has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/paytm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Paytm MCP server | Agent MCP Directory > Paytm has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/paytm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Paytm: MCP server, CLI and agent surfaces Yes: Paytm runs a public MCP server at travel.paytm.com that listed 10 tools to a client with no credentials on 4 November 2026. Examples: search\_flights, get\_flight\_details, get\_flight\_review. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for paytm.com is 52, grade C, read on 5 November 2026. ## Fact sheet | Company | Paytm (registry title: Paytm Travel) | | --- | --- | | Domain | paytm.com | | Category | Travel & Hospitality (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 7,788 on the list of 4 November 2026 | | Ora score | 52, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for paytm.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://travel.paytm.com/mcp/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Paytm Travel 3.4.11 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 10 | | Resources | 7 | | Prompts | 5 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,604 ms over 1 attempt | ### Tools listed 10 tools - search\_flights - get\_flight\_details - get\_flight\_review - combine\_roundtrip\_fare - fare\_calendar - get\_fare\_family - relay\_pulse\_batch - search\_buses - get\_bus\_ai\_summaries - get\_bus\_details ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:14Z https://travel.paytm.com/mcp/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1567 ms - 20:01:53Z https://travel.paytm.com/mcp/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1604 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://travel.paytm.com/mcp/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Paytm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.paytm.travel/discovery | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/paytm-com/index.md) ## Sources - [Ora score page for paytm.com](https://ora.ai/score/paytm.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Where Paytm was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.paytm.travel%2Fdiscovery), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=paytm), read 4 November 2026 - [Paytm website](https://paytm.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Locus MCP server | Agent MCP Directory" description: "Locus: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/paywithlocus-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Locus MCP server | Agent MCP Directory > Locus: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/paywithlocus-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Locus: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Locus at api.paywithlocus.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Locus | | --- | --- | | Domain | paywithlocus.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 84, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for paywithlocus.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.paywithlocus.com/api/credits/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 739 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:50Z https://api.paywithlocus.com/api/credits/mcp sent initialize result auth-required (HTTP 401) 1526 ms - 20:04:00Z https://api.paywithlocus.com/api/credits/mcp sent initialize result auth-required (HTTP 401) 739 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.paywithlocus.com/.well-known/oauth-protected-resource/api/credits/mcp", scope="mcp:read mcp:execute" | | Protected resource metadata | api.paywithlocus.com | | Authorization server metadata | api.paywithlocus.com | | Registration endpoint | https://api.paywithlocus.com/api/credits/mcp/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.paywithlocus.com/api/credits/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.paywithlocus.com/.well-known/oauth-protected-resource/api/credits/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.paywithlocus.com/api/credits/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Locus. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: paywithlocus.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: paywithlocus.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: paywithlocus.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.paywithlocus/locus | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/paywithlocus-com/index.md) ## Sources - [Ora score page for paywithlocus.com](https://ora.ai/score/paywithlocus.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Locus was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.paywithlocus%2Flocus), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=paywithlocus), read 4 November 2026 - [Locus website](https://paywithlocus.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Peek.com MCP server | Agent MCP Directory" description: "Peek.com has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/peek-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Peek.com MCP server | Agent MCP Directory > Peek.com has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/peek-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Peek.com: MCP server, CLI and agent surfaces Yes: Peek.com runs a public MCP server at mcp.peek.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: experience\_availability, experience\_details, list\_tags. It speaks streamable-http, protocol 2025-03-26. Ora's cached score for peek.com is 39, grade D, read on 5 November 2026. ## Fact sheet | Company | Peek.com | | --- | --- | | Domain | peek.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 39, grade D; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for peek.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.peek.com | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | Experiences MCP 1.0.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,153 ms over 1 attempt | ### Tools listed 6 tools - experience\_availability - experience\_details - list\_tags - render\_activity\_tiles - search\_experiences - search\_regions ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:50Z https://mcp.peek.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1491 ms - 20:04:00Z https://mcp.peek.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1153 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.peek.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Peek.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.peek/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/peek-com/index.md) ## Sources - [Ora score page for peek.com](https://ora.ai/score/peek.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/score) - [Where Peek.com was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=peek), read 4 November 2026 - [Peek.com website](https://peek.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PensionHunter MCP server | Agent MCP Directory" description: "PensionHunter has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pensionhunter-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PensionHunter MCP server | Agent MCP Directory > PensionHunter has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pensionhunter-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # PensionHunter: MCP server, CLI and agent surfaces Yes: PensionHunter runs a public MCP server at mcp.pensionhunter.ai that listed 11 tools to a client with no credentials on 4 November 2026. Examples: list\_covered\_countries, country\_pension\_facts, check\_work\_history. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | PensionHunter | | --- | --- | | Domain | pensionhunter.ai | | Category | Security (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for pensionhunter.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.pensionhunter.ai | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | pensionhunter 1.14.0 | | Capabilities | tools | | Tools | 11 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 2,223 ms over 1 attempt | ### Tools listed 11 tools - list\_covered\_countries - country\_pension\_facts - check\_work\_history - resolve\_employer - authority\_answer - deadline\_check - create\_order\_link - gpfr\_info - gpfr\_register - gpfr\_status - gpfr\_fund\_count ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:53Z https://mcp.pensionhunter.ai sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2948 ms - 20:04:01Z https://mcp.pensionhunter.ai sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2223 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.pensionhunter.ai` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PensionHunter. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.pensionhunter/pensionhunter | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pensionhunter-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pensionhunter), read 4 November 2026 - [PensionHunter website](https://pensionhunter.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pexafy MCP server | Agent MCP Directory" description: "Pexafy has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pexafy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pexafy MCP server | Agent MCP Directory > Pexafy has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pexafy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pexafy: MCP server, CLI and agent surfaces Yes: Pexafy runs a public MCP server at mcp.pexafy.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: search\_photos, search\_photos\_by\_image, get\_photo\_file\_by\_photo\_id. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Pexafy (registry title: Pexafy Stock Photos) | | --- | --- | | Domain | pexafy.com | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for pexafy.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.pexafy.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | pexafy 1.0.2 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 5 | | Resources | 1 | | Prompts | 1 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 839 ms over 1 attempt | ### Tools listed 5 tools - search\_photos - search\_photos\_by\_image - get\_photo\_file\_by\_photo\_id - get\_grid\_selected\_photos - connect\_account ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:51Z https://mcp.pexafy.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 963 ms - 20:04:00Z https://mcp.pexafy.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 839 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.pexafy.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pexafy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pexafy/pexafy-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pexafy-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pexafy), read 4 November 2026 - [Pexafy website](https://pexafy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PgDog MCP server | Agent MCP Directory" description: "Does PgDog have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pgdog-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PgDog MCP server | Agent MCP Directory > Does PgDog have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pgdog-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # PgDog: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for PgDog (pgdog.dev), so the connector had nothing to connect to. Ora's cached score for pgdog.dev is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | PgDog (registry title: pgdog.dev) | | --- | --- | | Domain | pgdog.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pgdog.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for PgDog. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pgdog.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for PgDog. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pgdog-dev/index.md) ## Sources - [Ora score page for pgdog.dev](https://ora.ai/score/pgdog.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where PgDog was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [PgDog website](https://pgdog.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Picsart MCP server | Agent MCP Directory" description: "Picsart: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media." canonical: https://agentmcpdirectory.com/directory/picsart-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Picsart MCP server | Agent MCP Directory > Picsart: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media. Source: https://agentmcpdirectory.com/directory/picsart-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Picsart: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Picsart at api.picsart.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Picsart (registry title: Picsart GenAI) | | --- | --- | | Domain | picsart.com | | Category | Gaming & Media (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,374 on the list of 4 November 2026 | | Ora score | 72, grade B; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for picsart.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.picsart.com/gen-ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 424 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:05Z https://api.picsart.com/gen-ai/mcp sent initialize result auth-required (HTTP 401) 393 ms - 20:01:42Z https://api.picsart.com/gen-ai/mcp sent initialize result auth-required (HTTP 401) 424 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required for this tool", resource_metadata="https://api.picsart.com/gen-ai/.well-known/oauth-protected-resource" | | Protected resource metadata | api.picsart.com | | Authorization server metadata | auth.picsart.com | | Registration endpoint | https://auth.picsart.com/api/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.picsart.com/gen-ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.picsart.com/gen-ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.picsart.com/api/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Picsart. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.picsart.api/gen-ai | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/picsart-com/index.md) ## Sources - [Ora score page for picsart.com](https://ora.ai/score/picsart.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/score) - [Where Picsart was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.picsart.api%2Fgen-ai), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=picsart), read 4 November 2026 - [Picsart website](https://picsart.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PicSee MCP server | Agent MCP Directory" description: "PicSee has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/picsee-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PicSee MCP server | Agent MCP Directory > PicSee has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/picsee-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # PicSee: MCP server, CLI and agent surfaces Yes: PicSee runs a public MCP server at api.picsee.io that listed 1 tool to a client with no credentials on 4 November 2026. Examples: create\_short\_link. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | PicSee (registry title: PicSee Short Link) | | --- | --- | | Domain | picsee.io | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for picsee.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.picsee.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | PicSee Short Link MCP 3.1.0 | | Capabilities | tools | | Tools | 1 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,346 ms over 1 attempt | ### Tools listed 1 tool - create\_short\_link ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:52Z https://api.picsee.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1530 ms - 20:04:01Z https://api.picsee.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1346 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.picsee.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PicSee. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/picsee-io/index.md) ## Sources - [PicSee website](https://picsee.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pingram MCP server | Agent MCP Directory" description: "Does Pingram have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pingram-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pingram MCP server | Agent MCP Directory > Does Pingram have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pingram-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pingram: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Pingram (pingram.io), so the connector had nothing to connect to. Ora's cached score for pingram.io is 88, grade A, read on 5 November 2026. The company was added from the GitHub MCP Registry. ## Fact sheet | Company | Pingram | | --- | --- | | Domain | pingram.io | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | None found | | Ora score | 88, grade A; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for pingram.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Pingram. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pingram.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | Listed | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Pingram. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pingram-io/index.md) ## Sources - [Ora score page for pingram.io](https://ora.ai/score/pingram.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/score) - [Pingram website](https://pingram.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pipeboard MCP server | Agent MCP Directory" description: "Pipeboard: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/pipeboard-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pipeboard MCP server | Agent MCP Directory > Pipeboard: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/pipeboard-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pipeboard: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Pipeboard at snap-ads.mcp.pipeboard.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Pipeboard | | --- | --- | | Domain | pipeboard.co | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 70, grade B; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for pipeboard.co, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://snap-ads.mcp.pipeboard.co/ | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 973 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:52Z https://snap-ads.mcp.pipeboard.co/ sent initialize result auth-required (HTTP 401) 1033 ms - 20:04:01Z https://snap-ads.mcp.pipeboard.co/ sent initialize result auth-required (HTTP 401) 973 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="MCP", resource_metadata="https://snap-ads.mcp.pipeboard.co/.well-known/oauth-protected-resource?platform=snap-ads" | | Protected resource metadata | snap-ads.mcp.pipeboard.co | | Authorization server metadata | snap-ads.mcp.pipeboard.co | | Registration endpoint | https://pipeboard.co/oauth/register?platform=snap-ads | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://snap-ads.mcp.pipeboard.co/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://snap-ads.mcp.pipeboard.co/.well-known/oauth-protected-resource?platform=snap-ads` to find the authorization server. 3. Register a client at the registration endpoint `https://pipeboard.co/oauth/register?platform=snap-ads` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pipeboard. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.pipeboard/google-ads-mcp, co.pipeboard/meta-ads-mcp, co.pipeboard/snap-ads-mcp and 1 more | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pipeboard-co/index.md) ## Sources - [Ora score page for pipeboard.co](https://ora.ai/score/pipeboard.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/score) - [Where Pipeboard was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pipeboard), read 4 November 2026 - [Pipeboard website](https://pipeboard.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pipefy MCP server | Agent MCP Directory" description: "Does Pipefy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pipefy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pipefy MCP server | Agent MCP Directory > Does Pipefy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pipefy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pipefy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Pipefy (pipefy.com), so the connector had nothing to connect to. Ora's cached score for pipefy.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Pipefy (registry title: pipefy.com) | | --- | --- | | Domain | pipefy.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pipefy.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Pipefy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pipefy.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Pipefy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pipefy-com/index.md) ## Sources - [Ora score page for pipefy.com](https://ora.ai/score/pipefy.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Pipefy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Pipefy website](https://pipefy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pipekit MCP server | Agent MCP Directory" description: "Does Pipekit have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pipekit-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pipekit MCP server | Agent MCP Directory > Does Pipekit have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pipekit-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pipekit: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Pipekit (pipekit.io), so the connector had nothing to connect to. Ora's cached score for pipekit.io is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Pipekit (registry title: pipekit.io) | | --- | --- | | Domain | pipekit.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 12 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pipekit.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Pipekit. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pipekit.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Pipekit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pipekit-io/index.md) ## Sources - [Ora score page for pipekit.io](https://ora.ai/score/pipekit.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 October 2026, read from GET /api/leaderboard) - [Where Pipekit was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Pipekit website](https://pipekit.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pith MCP server | Agent MCP Directory" description: "Pith: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pith-day site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pith MCP server | Agent MCP Directory > Pith: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pith-day Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pith: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Pith at pith.day answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Pith (registry title: Pith: Instagram publishing) | | --- | --- | | Domain | pith.day | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for pith.day when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://pith.day/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 741 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:53Z https://pith.day/api/mcp sent initialize result auth-required (HTTP 401) 1360 ms - 20:04:01Z https://pith.day/api/mcp sent initialize result auth-required (HTTP 401) 741 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://pith.day/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | pith.day | | Authorization server metadata | pith.day | | Registration endpoint | https://pith.day/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://pith.day/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://pith.day/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://pith.day/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pith. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pith-day/index.md) ## Sources - [Where Pith was found](https://github.com/mcp/pith-day/pith-mcp), read 4 November 2026 - [Pith website](https://pith.day), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pixelesq MCP server | Agent MCP Directory" description: "Pixelesq: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/pixelesq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pixelesq MCP server | Agent MCP Directory > Pixelesq: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/pixelesq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pixelesq: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Pixelesq at mcp.pixelesq.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Pixelesq | | --- | --- | | Domain | pixelesq.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 48, grade C; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for pixelesq.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.pixelesq.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 127 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:52Z https://mcp.pixelesq.app/mcp sent initialize result auth-required (HTTP 401) 662 ms - 20:04:01Z https://mcp.pixelesq.app/mcp sent initialize result auth-required (HTTP 401) 127 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.pixelesq.app/.well-known/oauth-protected-resource/mcp", scope="projects:read content:read content:write publish analytics:read" | | Protected resource metadata | mcp.pixelesq.app | | Authorization server metadata | mcp.pixelesq.app | | Registration endpoint | https://mcp.pixelesq.app/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.pixelesq.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.pixelesq.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.pixelesq.app/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pixelesq. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pixelesq/pixelesq | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pixelesq-com/index.md) ## Sources - [Ora score page for pixelesq.com](https://ora.ai/score/pixelesq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pixelesq), read 4 November 2026 - [Pixelesq website](https://pixelesq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PixelFlow MCP server | Agent MCP Directory" description: "PixelFlow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/pixelflow-so site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PixelFlow MCP server | Agent MCP Directory > PixelFlow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/pixelflow-so Site: Agent MCP Directory Last reviewed: 2026-11-05 # PixelFlow: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for PixelFlow at api.pixelflow.so answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | PixelFlow | | --- | --- | | Domain | pixelflow.so | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for pixelflow.so when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.pixelflow.so/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,215 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:53Z https://api.pixelflow.so/mcp sent initialize result auth-required (HTTP 401) 1514 ms - 20:04:02Z https://api.pixelflow.so/mcp sent initialize result auth-required (HTTP 401) 1215 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="mcp", resource_metadata="https://api.pixelflow.so/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.pixelflow.so | | Authorization server metadata | api.pixelflow.so | | Registration endpoint | https://api.pixelflow.so/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.pixelflow.so/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.pixelflow.so/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.pixelflow.so/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PixelFlow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pixelflow-so/index.md) ## Sources - [PixelFlow website](https://pixelflow.so), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Plaid MCP server | Agent MCP Directory" description: "Plaid: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/plaid-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Plaid MCP server | Agent MCP Directory > Plaid: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/plaid-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Plaid: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Plaid at api.dashboard.plaid.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Plaid | | --- | --- | | Domain | plaid.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for plaid.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.dashboard.plaid.com/mcp/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,317 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:53Z https://api.dashboard.plaid.com/mcp/sse sent initialize result auth-required (HTTP 401) 1578 ms - 20:04:03Z https://api.dashboard.plaid.com/mcp/sse sent initialize result auth-required (HTTP 401) 1317 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Authorization server metadata | api.dashboard.plaid.com | | Registration endpoint | https://api.dashboard.plaid.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.dashboard.plaid.com/mcp/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://api.dashboard.plaid.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Plaid. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/plaid-com/index.md) ## Sources - [Ora score page for plaid.com](https://ora.ai/score/plaid.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Plaid was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Plaid website](https://plaid.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Plane MCP server | Agent MCP Directory" description: "Plane has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/plane-so site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Plane MCP server | Agent MCP Directory > Plane has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/plane-so Site: Agent MCP Directory Last reviewed: 2026-11-05 # Plane: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Plane; the connector tried mcp.plane.so as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | Plane (registry title: plane.so) | | --- | --- | | Domain | plane.so | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 78, grade B; Ora scanned the domain on 18 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for plane.so, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.plane.so/mcp | | --- | --- | | How it was found | mcp.plane.so was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 949 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:53Z https://mcp.plane.so/mcp sent initialize result no-answer (HTTP 404) 980 ms - 20:04:02Z https://mcp.plane.so/mcp sent initialize result no-answer (HTTP 404) 949 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.plane.so/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Plane. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: plane.so (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | A JSON answer came back, but its keys do not match the file type, so it is not counted. | | A2A agent card | Found: plane.so/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: plane.so/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/plane-so/index.md) ## Sources - [Ora score page for plane.so](https://ora.ai/score/plane.so?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 September 2026, read from GET /api/leaderboard) - [Where Plane was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Plane website](https://plane.so), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PlanetScale MCP server | Agent MCP Directory" description: "Does PlanetScale have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/planetscale-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PlanetScale MCP server | Agent MCP Directory > Does PlanetScale have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/planetscale-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PlanetScale: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for PlanetScale (planetscale.com), so the connector had nothing to connect to. Ora's cached score for planetscale.com is 79, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | PlanetScale | | --- | --- | | Domain | planetscale.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 79, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for planetscale.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for PlanetScale. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for planetscale.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for PlanetScale. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/planetscale-com/index.md) ## Sources - [Ora score page for planetscale.com](https://ora.ai/score/planetscale.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where PlanetScale was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [PlanetScale website](https://planetscale.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Platform.sh MCP server | Agent MCP Directory" description: "Does Platform.sh have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/platform-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Platform.sh MCP server | Agent MCP Directory > Does Platform.sh have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/platform-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Platform.sh: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Platform.sh (platform.sh), so the connector had nothing to connect to. Ora's cached score for platform.sh is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Platform.sh | | --- | --- | | Domain | platform.sh | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for platform.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Platform.sh. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for platform.sh, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Platform.sh. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/platform-sh/index.md) ## Sources - [Ora score page for platform.sh](https://ora.ai/score/platform.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/leaderboard) - [Where Platform.sh was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Platform.sh website](https://platform.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ploomber MCP server | Agent MCP Directory" description: "Does Ploomber have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ploomber-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ploomber MCP server | Agent MCP Directory > Does Ploomber have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/ploomber-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ploomber: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ploomber (ploomber.io), so the connector had nothing to connect to. Ora's cached score for ploomber.io is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ploomber (registry title: ploomber.io) | | --- | --- | | Domain | ploomber.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ploomber.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ploomber. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ploomber.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ploomber. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ploomber-io/index.md) ## Sources - [Ora score page for ploomber.io](https://ora.ai/score/ploomber.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Ploomber was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Plori MCP server | Agent MCP Directory" description: "Plori: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/plori-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Plori MCP server | Agent MCP Directory > Plori: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/plori-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Plori: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Plori at api.plori.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Plori | | --- | --- | | Domain | plori.ai | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 74, grade B; Ora scanned the domain on 5 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for plori.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.plori.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,152 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:54Z https://api.plori.ai/mcp sent initialize result auth-required (HTTP 401) 1447 ms - 20:04:03Z https://api.plori.ai/mcp sent initialize result auth-required (HTTP 401) 1152 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.plori.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.plori.ai | | Authorization server metadata | api.plori.ai | | Registration endpoint | https://api.plori.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://api.plori.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.plori.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.plori.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Plori. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: plori.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.plori/plori | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/plori-ai/index.md) ## Sources - [Ora score page for plori.ai](https://ora.ai/score/plori.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=plori), read 4 November 2026 - [Plori website](https://plori.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "POEditor MCP server | Agent MCP Directory" description: "POEditor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/poeditor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # POEditor MCP server | Agent MCP Directory > POEditor: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/poeditor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # POEditor: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for POEditor at mcp.poeditor.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | POEditor | | --- | --- | | Domain | poeditor.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for poeditor.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.poeditor.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 884 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:55Z https://mcp.poeditor.com/mcp sent initialize result auth-required (HTTP 401) 1795 ms - 20:04:03Z https://mcp.poeditor.com/mcp sent initialize result auth-required (HTTP 401) 884 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.poeditor.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.poeditor.com | | Authorization server metadata | poeditor.com | | Registration endpoint | https://poeditor.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.poeditor.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.poeditor.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://poeditor.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for POEditor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/poeditor-com/index.md) ## Sources - [POEditor website](https://poeditor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Polar Signals MCP server | Agent MCP Directory" description: "Polar Signals: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/polarsignals-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Polar Signals MCP server | Agent MCP Directory > Polar Signals: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/polarsignals-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Polar Signals: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Polar Signals at api.polarsignals.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Polar Signals | | --- | --- | | Domain | polarsignals.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for polarsignals.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.polarsignals.com/api/mcp/ | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 565 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:54Z https://api.polarsignals.com/api/mcp/ sent initialize result auth-required (HTTP 401) 901 ms - 20:04:03Z https://api.polarsignals.com/api/mcp/ sent initialize result auth-required (HTTP 401) 565 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.polarsignals.com/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | api.polarsignals.com | | Authorization server metadata | api.polarsignals.com | | Registration endpoint | https://api.polarsignals.com/api/oauth/register | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.polarsignals.com/api/mcp/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.polarsignals.com/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.polarsignals.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Polar Signals. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/polarsignals-com/index.md) ## Sources - [Where Polar Signals was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Polar Signals website](https://polarsignals.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Poly MCP server | Agent MCP Directory" description: "Poly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/poly-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Poly MCP server | Agent MCP Directory > Poly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/poly-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Poly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Poly; the connector's guess at mcp.poly.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Poly (registry title: poly.app) | | --- | --- | | Domain | poly.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 39, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for poly.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.poly.app/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,807 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:56Z https://mcp.poly.app/mcp sent initialize result auth-required (HTTP 401) 2782 ms - 20:04:04Z https://mcp.poly.app/mcp sent initialize result auth-required (HTTP 401) 1807 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.poly.app/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.poly.app | | Authorization server metadata | poly.app | | Registration endpoint | https://poly.app/api/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.poly.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.poly.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://poly.app/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Poly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: poly.app/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/poly-app/index.md) ## Sources - [Ora score page for poly.app](https://ora.ai/score/poly.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Poly was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Poly website](https://poly.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pontofato MCP server | Agent MCP Directory" description: "Pontofato has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pontofato-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pontofato MCP server | Agent MCP Directory > Pontofato has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pontofato-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pontofato: MCP server, CLI and agent surfaces Yes: Pontofato runs a public MCP server at pontofato.com that listed 23 tools to a client with no credentials on 4 November 2026. Examples: api\_index, health, cep. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Pontofato | | --- | --- | | Domain | pontofato.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for pontofato.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://pontofato.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | PontoFato fb0c5518 | | Capabilities | tools, prompts | | Tools | 23 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 3,760 ms over 1 attempt | ### Tools listed 23 tools - api\_index - health - cep - proximo - buscar - unidades - empresas - raio - vizinhanca - contact - consulta\_cadastro - consulta\_endereco - consulta\_sugerir - consulta\_cnpj - consulta\_cep - consulta\_planos - consulta\_comprar - sugerir - api\_access - api\_access\_buy - pricing - billing - get\_api\_x402\_cnpj\_by\_cnpj ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:57Z https://pontofato.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2507 ms - 20:04:06Z https://pontofato.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 3760 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://pontofato.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pontofato. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: pontofato.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.pontofato/pontofato | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pontofato-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=pontofato), read 4 November 2026 - [Pontofato website](https://pontofato.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Porkbun MCP server | Agent MCP Directory" description: "Porkbun: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/porkbun-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Porkbun MCP server | Agent MCP Directory > Porkbun: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/porkbun-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Porkbun: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Porkbun at mcp.porkbun.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Porkbun (registry title: Porkbun (official)) | | --- | --- | | Domain | porkbun.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 902 on the list of 4 November 2026 | | Ora score | 55, grade C; Ora scanned the domain on 8 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for porkbun.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.porkbun.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,315 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.porkbun.com/mcp sent initialize result auth-required (HTTP 401) 2274 ms - 20:01:33Z https://mcp.porkbun.com/mcp sent initialize result auth-required (HTTP 401) 2315 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.porkbun.com/.well-known/oauth-protected-resource", scope="api offline_access" | | Protected resource metadata | mcp.porkbun.com | | Authorization server metadata | porkbun.com | | Registration endpoint | https://porkbun.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.porkbun.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.porkbun.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://porkbun.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Porkbun. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: porkbun.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.porkbun/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/porkbun-com/index.md) ## Sources - [Ora score page for porkbun.com](https://ora.ai/score/porkbun.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 September 2026, read from GET /api/score) - [Where Porkbun was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.porkbun%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=porkbun), read 4 November 2026 - [Porkbun website](https://porkbun.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Port IO MCP server | Agent MCP Directory" description: "Port IO: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/port-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Port IO MCP server | Agent MCP Directory > Port IO: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/port-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Port IO: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Port IO at mcp.port.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Port IO | | --- | --- | | Domain | port.io | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 65, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for port.io, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.port.io/v1 | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 754 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:55Z https://mcp.port.io/v1 sent initialize result auth-required (HTTP 401) 769 ms - 20:04:03Z https://mcp.port.io/v1 sent initialize result auth-required (HTTP 401) 754 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.port.io | | Authorization server metadata | mcp.port.io | | Registration endpoint | https://mcp.port.io/v1/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.port.io/v1` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.port.io/.well-known/oauth-protected-resource/v1` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.port.io/v1/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Port IO. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/port-io/index.md) ## Sources - [Ora score page for port.io](https://ora.ai/score/port.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Port IO was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Port IO website](https://port.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Portainer MCP server | Agent MCP Directory" description: "Does Portainer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/portainer-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Portainer MCP server | Agent MCP Directory > Does Portainer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/portainer-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Portainer: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Portainer (portainer.io), so the connector had nothing to connect to. Ora's cached score for portainer.io is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Portainer (registry title: portainer.io) | | --- | --- | | Domain | portainer.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for portainer.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Portainer. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for portainer.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Portainer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/portainer-io/index.md) ## Sources - [Ora score page for portainer.io](https://ora.ai/score/portainer.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where Portainer was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Portainer website](https://portainer.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Porter MCP server | Agent MCP Directory" description: "Does Porter have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/porter-run site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Porter MCP server | Agent MCP Directory > Does Porter have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/porter-run Site: Agent MCP Directory Last reviewed: 2026-11-05 # Porter: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Porter (porter.run), so the connector had nothing to connect to. Ora's cached score for porter.run is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Porter | | --- | --- | | Domain | porter.run | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for porter.run, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Porter. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for porter.run, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Porter. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/porter-run/index.md) ## Sources - [Ora score page for porter.run](https://ora.ai/score/porter.run?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Porter was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Porter website](https://porter.run), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PostData MCP server | Agent MCP Directory" description: "PostData has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/postdata-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PostData MCP server | Agent MCP Directory > PostData has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/postdata-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # PostData: MCP server, CLI and agent surfaces Yes: PostData runs a public MCP server at api.postdata.cloud that listed 6 tools to a client with no credentials on 4 November 2026. Examples: new\_device\_name, publish\_reading, get\_latest. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | PostData | | --- | --- | | Domain | postdata.cloud | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for postdata.cloud when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.postdata.cloud/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | postdata 2.3.2 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 152 ms over 1 attempt | ### Tools listed 6 tools - new\_device\_name - publish\_reading - get\_latest - get\_history - wait\_for\_reading - list\_recent\_devices ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:55Z https://api.postdata.cloud/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 496 ms - 20:04:03Z https://api.postdata.cloud/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 152 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.postdata.cloud/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PostData. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: cloud.postdata/postdata | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/postdata-cloud/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=postdata), read 4 November 2026 - [PostData website](https://postdata.cloud), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Postel MCP server | Agent MCP Directory" description: "Postel has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/postel-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Postel MCP server | Agent MCP Directory > Postel has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/postel-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Postel: MCP server, CLI and agent surfaces Yes: Postel runs a public MCP server at www.postel.app that listed 17 tools to a client with no credentials on 4 November 2026. Examples: search-viral-tweets, list-posts, get-post. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Postel | | --- | --- | | Domain | postel.app | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for postel.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.postel.app/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | postel 1.0.0 | | Capabilities | tools | | Tools | 17 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,094 ms over 1 attempt | ### Tools listed 17 tools - search-viral-tweets - list-posts - get-post - create-post - update-post - delete-post - schedule-post - publish-post - create-posts - attach-media - generate-post - refine-post - list-brands - get-brand-sources - get-x-profiles - get-schedule - get-usage ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:56Z https://www.postel.app/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 789 ms - 20:04:04Z https://www.postel.app/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1094 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.postel.app/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Postel. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.postel/postel | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/postel-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=postel), read 4 November 2026 - [Postel website](https://postel.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Posteverywhere MCP server | Agent MCP Directory" description: "Posteverywhere: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/posteverywhere-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Posteverywhere MCP server | Agent MCP Directory > Posteverywhere: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/posteverywhere-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Posteverywhere: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Posteverywhere at mcp.posteverywhere.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Posteverywhere | | --- | --- | | Domain | posteverywhere.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 92, grade A; Ora scanned the domain on 14 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for posteverywhere.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.posteverywhere.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 760 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:56Z https://mcp.posteverywhere.ai/mcp sent initialize result auth-required (HTTP 401) 1001 ms - 20:04:04Z https://mcp.posteverywhere.ai/mcp sent initialize result auth-required (HTTP 401) 760 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="PostEverywhere MCP", resource_metadata="https://mcp.posteverywhere.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.posteverywhere.ai | | Authorization server metadata | app.posteverywhere.ai | | Registration endpoint | https://app.posteverywhere.ai/api/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.posteverywhere.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.posteverywhere.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.posteverywhere.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Posteverywhere. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.posteverywhere/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/posteverywhere-ai/index.md) ## Sources - [Ora score page for posteverywhere.ai](https://ora.ai/score/posteverywhere.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=posteverywhere), read 4 November 2026 - [Posteverywhere website](https://posteverywhere.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PostHog MCP server | Agent MCP Directory" description: "PostHog: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/posthog-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PostHog MCP server | Agent MCP Directory > PostHog: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/posthog-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PostHog: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for PostHog at mcp.posthog.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | PostHog | | --- | --- | | Domain | posthog.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,022 on the list of 4 November 2026 | | Ora score | 86, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for posthog.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.posthog.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 195 ms over 1 attempt | | Documentation | posthog.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.posthog.com/mcp sent initialize result auth-required (HTTP 401) 160 ms - 20:01:33Z https://mcp.posthog.com/mcp sent initialize result auth-required (HTTP 401) 195 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.posthog.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.posthog.com | | Authorization server metadata | oauth.posthog.com | | Registration endpoint | https://oauth.posthog.com/oauth/register/ | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.posthog.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.posthog.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://oauth.posthog.com/oauth/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PostHog. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: posthog.com (JSON, via the shared crawl). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/posthog-com/index.md) ## Sources - [PostHog MCP documentation](https://posthog.com/docs/model-context-protocol), read 4 November 2026 - [Ora score page for posthog.com](https://ora.ai/score/posthog.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [PostHog website](https://posthog.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Postman MCP server | Agent MCP Directory" description: "Postman: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/postman-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Postman MCP server | Agent MCP Directory > Postman: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/postman-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Postman: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Postman at mcp.postman.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Postman (registry title: Postman MCP Server) | | --- | --- | | Domain | postman.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,383 on the list of 4 November 2026 | | Ora score | 80, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for postman.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.postman.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 12,795 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:02Z https://mcp.postman.com/mcp sent initialize result auth-required (HTTP 401) 822 ms - 20:01:50Z https://mcp.postman.com/mcp sent initialize result auth-required (HTTP 401) 12795 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.postman.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.postman.com | | Authorization server metadata | mcp.postman.com | | Registration endpoint | https://mcp.postman.com/register | ### The sign-in route, step by step 1. Request `https://mcp.postman.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.postman.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.postman.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Postman. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: postman.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.postman/postman-mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/postman-com/index.md) ## Sources - [Ora score page for postman.com](https://ora.ai/score/postman.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=postman), read 4 November 2026 - [Postman website](https://postman.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Posy MCP server | Agent MCP Directory" description: "Posy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/posy-page site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Posy MCP server | Agent MCP Directory > Posy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/posy-page Site: Agent MCP Directory Last reviewed: 2026-11-05 # Posy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Posy at posy.page answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Posy | | --- | --- | | Domain | posy.page | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for posy.page when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://posy.page/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,174 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:57Z https://posy.page/api/mcp sent initialize result auth-required (HTTP 401) 1373 ms - 20:04:04Z https://posy.page/api/mcp sent initialize result auth-required (HTTP 401) 1174 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", scope="page:write", resource_metadata="https://posy.page/.well-known/oauth-protected-resource" | | Protected resource metadata | posy.page | | Authorization server metadata | posy.page | | Registration endpoint | https://posy.page/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://posy.page/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://posy.page/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://posy.page/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Posy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: posy.page (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/posy-page/index.md) ## Sources - [Where Posy was found](https://github.com/mcp/Himanshu-Sangshetti/posy), read 4 November 2026 - [Posy website](https://posy.page), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Powmcp MCP server | Agent MCP Directory" description: "Powmcp has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/powmcp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Powmcp MCP server | Agent MCP Directory > Powmcp has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/powmcp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Powmcp: MCP server, CLI and agent surfaces Yes: Powmcp runs a public MCP server at powmcp.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: ebook\_check, ebook\_compare. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Powmcp (registry title: Caption File Check) | | --- | --- | | Domain | powmcp.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for powmcp.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://powmcp.com/epub-check/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | epub-check 0.5.3 | | Capabilities | tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,046 ms over 1 attempt | ### Tools listed 2 tools - ebook\_check - ebook\_compare ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:57Z https://powmcp.com/epub-check/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1410 ms - 20:04:04Z https://powmcp.com/epub-check/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1046 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://powmcp.com/epub-check/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Powmcp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.powmcp/caption-file-check, com.powmcp/epub-check, com.powmcp/ssl-certificate-check | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/powmcp-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=powmcp), read 4 November 2026 - [Powmcp website](https://powmcp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Praxim MCP server | Agent MCP Directory" description: "Does Praxim have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/praxim-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Praxim MCP server | Agent MCP Directory > Does Praxim have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/praxim-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Praxim: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Praxim (praxim.ai), so the connector had nothing to connect to. Ora's cached score for praxim.ai is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Praxim (registry title: praxim.ai) | | --- | --- | | Domain | praxim.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for praxim.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Praxim. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for praxim.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Praxim. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/praxim-ai/index.md) ## Sources - [Ora score page for praxim.ai](https://ora.ai/score/praxim.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/leaderboard) - [Where Praxim was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Praxim website](https://praxim.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Precip MCP server | Agent MCP Directory" description: "Precip: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/precip-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Precip MCP server | Agent MCP Directory > Precip: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/precip-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Precip: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Precip at api.precip.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Precip | | --- | --- | | Domain | precip.ai | | Category | Climate & Energy (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 38, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for precip.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.precip.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 452 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:57Z https://api.precip.ai/mcp sent initialize result auth-required (HTTP 401) 797 ms - 20:04:05Z https://api.precip.ai/mcp sent initialize result auth-required (HTTP 401) 452 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Precip MCP", resource_metadata="https://api.precip.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.precip.ai | | Authorization server metadata | ent-api.precip.ai | | Registration endpoint | https://ent-api.precip.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://api.precip.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.precip.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://ent-api.precip.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Precip. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.precip/weather | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/precip-ai/index.md) ## Sources - [Ora score page for precip.ai](https://ora.ai/score/precip.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Precip was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.precip%2Fweather), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=precip), read 4 November 2026 - [Precip website](https://precip.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Predictionmarketspicks MCP server | Agent MCP Directory" description: "Predictionmarketspicks has an open MCP server with 40 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/predictionmarketspicks-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Predictionmarketspicks MCP server | Agent MCP Directory > Predictionmarketspicks has an open MCP server with 40 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/predictionmarketspicks-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Predictionmarketspicks: MCP server, CLI and agent surfaces Yes: Predictionmarketspicks runs a public MCP server at predictionmarketspicks.com that listed 40 tools to a client with no credentials on 4 November 2026. Examples: fed\_rate\_odds, calculate\_ev, kelly\_size. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Predictionmarketspicks (registry title: Prediction Markets Quant) | | --- | --- | | Domain | predictionmarketspicks.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for predictionmarketspicks.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://predictionmarketspicks.com/api/mcp/mcp?via=registry | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | predictionmarketspicks 1.30.0 | | Capabilities | tools, resources, prompts | | Tools | 40 | | Resources | 5 | | Prompts | 11 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 3,911 ms over 1 attempt | ### Tools listed 40 tools - fed\_rate\_odds - calculate\_ev - kelly\_size - bayes\_update - convert\_probability - stress\_test\_strategy - base\_rate\_gap - combo\_edge - nfl\_power\_ratings - nfl\_win\_probability - find\_arbitrage - market\_pulse - commodity\_edge - edge\_alerts - nfl\_edge - nfl\_prop\_edge - nhl\_edge - nfl\_prop\_board - nba\_prop\_board - nba\_game\_board - nba\_injury\_impact - nfl\_ladder - ladder\_arb - fifteen\_min\_board - weather\_board - track\_record - my\_league - start\_sit - waiver\_targets - perps\_board - perp\_liquidation - senate\_map - race\_odds - best\_price - player\_outlook - explain\_player - explain\_game - explain\_prop - explain\_ladder - sleepers\_and\_busts ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:00Z https://predictionmarketspicks.com/api/mcp/mcp?via=registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3785 ms - 20:04:08Z https://predictionmarketspicks.com/api/mcp/mcp?via=registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3911 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://predictionmarketspicks.com/api/mcp/mcp?via=registry` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Predictionmarketspicks. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.predictionmarketspicks/commodities, com.predictionmarketspicks/crypto, com.predictionmarketspicks/elections and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/predictionmarketspicks-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=predictionmarketspicks), read 4 November 2026 - [Predictionmarketspicks website](https://predictionmarketspicks.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PredictLeads MCP server | Agent MCP Directory" description: "PredictLeads: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/predictleads-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PredictLeads MCP server | Agent MCP Directory > PredictLeads: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/predictleads-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PredictLeads: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for PredictLeads at mcp.predictleads.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | PredictLeads | | --- | --- | | Domain | predictleads.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 42, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for predictleads.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.predictleads.com/ | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 482 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:57Z https://mcp.predictleads.com/ sent initialize result auth-required (HTTP 401) 871 ms - 20:04:05Z https://mcp.predictleads.com/ sent initialize result auth-required (HTTP 401) 482 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.predictleads.com/.well-known/oauth-protected-resource", scope="api__read api__write" | | Protected resource metadata | mcp.predictleads.com | | Authorization server metadata | oauth.predictleads.com | | Registration endpoint | https://oauth.predictleads.com/registration | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.predictleads.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.predictleads.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://oauth.predictleads.com/registration` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PredictLeads. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: predictleads.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.predictleads/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/predictleads-com/index.md) ## Sources - [Ora score page for predictleads.com](https://ora.ai/score/predictleads.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where PredictLeads was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.predictleads%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=predictleads), read 4 November 2026 - [PredictLeads website](https://predictleads.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Prembly MCP server | Agent MCP Directory" description: "Prembly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security." canonical: https://agentmcpdirectory.com/directory/prembly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Prembly MCP server | Agent MCP Directory > Prembly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security. Source: https://agentmcpdirectory.com/directory/prembly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Prembly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Prembly at mcp.prembly.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Prembly (registry title: Prembly MCP Server) | | --- | --- | | Domain | prembly.com | | Category | Security (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 47, grade D; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for prembly.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.prembly.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,667 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:00Z https://mcp.prembly.com/mcp sent initialize result auth-required (HTTP 401) 2459 ms - 20:04:06Z https://mcp.prembly.com/mcp sent initialize result auth-required (HTTP 401) 1667 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.prembly.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.prembly.com | | Authorization server metadata | backend.prembly.com | | Registration endpoint | https://backend.prembly.com/api/v1/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.prembly.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.prembly.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://backend.prembly.com/api/v1/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Prembly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.prembly/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/prembly-com/index.md) ## Sources - [Ora score page for prembly.com](https://ora.ai/score/prembly.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where Prembly was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.prembly%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=prembly), read 4 November 2026 - [Prembly website](https://prembly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PreShiftIQ MCP server | Agent MCP Directory" description: "PreShiftIQ has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/preshiftiq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PreShiftIQ MCP server | Agent MCP Directory > PreShiftIQ has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/preshiftiq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PreShiftIQ: MCP server, CLI and agent surfaces Yes: PreShiftIQ runs a public MCP server at mcp.preshiftiq.com that listed 13 tools to a client with no credentials on 4 November 2026. Examples: describe\_platform, list\_verticals, get\_public\_catalog. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | PreShiftIQ | | --- | --- | | Domain | preshiftiq.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for preshiftiq.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.preshiftiq.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | shiftiq-mcp 0.2.0+5069d34a.dedf8ff0 | | Capabilities | tools, resources, prompts, completions, extensions | | Tools | 13 | | Resources | 4 | | Prompts | 2 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,791 ms over 1 attempt | ### Tools listed 13 tools - describe\_platform - list\_verticals - get\_public\_catalog - explain\_matching - how\_we\_are\_paid - start\_assessment - search - fetch - answer\_question - my\_assessment\_status - my\_matches - my\_scorecard\_status - my\_clients ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:59Z https://mcp.preshiftiq.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2026 ms - 20:04:06Z https://mcp.preshiftiq.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1791 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.preshiftiq.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PreShiftIQ. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.preshiftiq/shiftiq-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/preshiftiq-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=preshiftiq), read 4 November 2026 - [PreShiftIQ website](https://preshiftiq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Primitive MCP server | Agent MCP Directory" description: "Primitive has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/primitive-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Primitive MCP server | Agent MCP Directory > Primitive has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/primitive-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Primitive: MCP server, CLI and agent surfaces Yes: Primitive runs a public MCP server at www.primitive.dev that listed 14 tools to a client with no credentials on 4 November 2026. Examples: getAccount, getInboxStatus, getOutboundStatus. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for primitive.dev is 96, grade A+, read on 5 November 2026. ## Fact sheet | Company | Primitive (registry title: primitive.dev) | | --- | --- | | Domain | primitive.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 96, grade A+; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for primitive.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.primitive.dev/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | primitive 0.3.0 | | Capabilities | tools, resources, prompts | | Tools | 14 | | Resources | 1 | | Prompts | 2 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,781 ms over 1 attempt | ### Tools listed 14 tools - getAccount - getInboxStatus - getOutboundStatus - listEmails - searchEmails - getEmail - replyToEmail - sendEmail - listSentEmails - getSentEmail - awaitReply - getConversation - getEmailAttachment - createEmailAddress ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:59Z https://www.primitive.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1635 ms - 20:04:06Z https://www.primitive.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1781 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.primitive.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Primitive. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.primitive.dev (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: primitive.dev/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: primitive.dev/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Found: primitive.dev/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: primitive.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.primitive/email | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Yes: primitivedotdev/primitive | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/primitive-dev/index.md) ## Sources - [Ora score page for primitive.dev](https://ora.ai/score/primitive.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Where Primitive was found](https://registry.modelcontextprotocol.io/v0/servers?search=dev.primitive%2Femail), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=primitive), read 4 November 2026 - [Primitive website](https://primitive.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PrintFriendly MCP server | Agent MCP Directory" description: "PrintFriendly: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/printfriendly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PrintFriendly MCP server | Agent MCP Directory > PrintFriendly: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/printfriendly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PrintFriendly: MCP server, CLI and agent surfaces Not counted. The endpoint listed for PrintFriendly at mcp.printfriendly.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | PrintFriendly | | --- | --- | | Domain | printfriendly.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for printfriendly.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.printfriendly.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,820 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:59Z https://mcp.printfriendly.com sent initialize result auth-required-no-oauth (HTTP 401) 1976 ms - 20:04:06Z https://mcp.printfriendly.com sent initialize result auth-required-no-oauth (HTTP 401) 1820 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | ApiKey realm="PrintFriendly API", header="X-API-Key" | ### The sign-in route, step by step 1. Request `https://mcp.printfriendly.com` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PrintFriendly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.printfriendly.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.printfriendly/printfriendly | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/printfriendly-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=printfriendly), read 4 November 2026 - [PrintFriendly website](https://printfriendly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Prisma MCP server | Agent MCP Directory" description: "Prisma: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/prisma-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Prisma MCP server | Agent MCP Directory > Prisma: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/prisma-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Prisma: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Prisma at mcp.prisma.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Prisma | | --- | --- | | Domain | prisma.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 82, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for prisma.io, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.prisma.io/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,446 ms over 1 attempt | | Documentation | www.prisma.io | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:59Z https://mcp.prisma.io/mcp sent initialize result auth-required (HTTP 401) 1562 ms - 20:04:06Z https://mcp.prisma.io/mcp sent initialize result auth-required (HTTP 401) 1446 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.prisma.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.prisma.io | | Authorization server metadata | auth.prisma.io | | Registration endpoint | https://auth.prisma.io/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.prisma.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.prisma.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.prisma.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | prisma on npm (page) | | --- | --- | | Exists | yes | | Latest version | 8.0.0-rc.30 | | Last publish | 3 November 2026 | | Command names | prisma | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.prisma.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: prisma.io/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/prisma-io/index.md) ## Sources - [Prisma MCP documentation](https://www.prisma.io/docs/postgres/integrations/mcp-server), read 4 November 2026 - [Ora score page for prisma.io](https://ora.ai/score/prisma.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Prisma website](https://prisma.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Probativegrowth MCP server | Agent MCP Directory" description: "Probativegrowth has an open MCP server with 24 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/probativegrowth-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Probativegrowth MCP server | Agent MCP Directory > Probativegrowth has an open MCP server with 24 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/probativegrowth-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Probativegrowth: MCP server, CLI and agent surfaces Yes: Probativegrowth runs a public MCP server at probativegrowth.com that listed 24 tools to a client with no credentials on 4 November 2026. Examples: list\_datasets, cite, data\_lookup. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Probativegrowth (registry title: Probative legal-marketing data) | | --- | --- | | Domain | probativegrowth.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for probativegrowth.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://probativegrowth.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | com.probativegrowth/legal-marketing-data 1.5.1 | | Capabilities | tools, resources, prompts, completions, extensions | | Tools | 24 | | Resources | 184 | | Prompts | 6 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 254 ms over 1 attempt | ### Tools listed 24 tools - list\_datasets - cite - data\_lookup - data\_search - get\_benchmark - get\_state\_rules - whats\_new - list\_mdl\_dockets - get\_rule - search - check\_ad\_elements - get\_ad\_filing\_requirements - search\_ethics\_opinions - get\_spanish\_demand\_supply - calculate\_fee\_cap - compare\_states - list\_rule\_changes - get\_attorney\_fee\_caps - get\_ad\_platform\_policies - search\_rules - get\_ca\_court\_filings - data\_compare - fetch - get\_state\_market\_brief ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:59Z https://probativegrowth.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1056 ms - 20:04:06Z https://probativegrowth.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 254 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://probativegrowth.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Probativegrowth. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.probativegrowth/legal-marketing-data, com.probativegrowth/legal-markets | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/probativegrowth-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=probativegrowth), read 4 November 2026 - [Probativegrowth website](https://probativegrowth.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Process Street MCP server | Agent MCP Directory" description: "Process Street: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/process-st site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Process Street MCP server | Agent MCP Directory > Process Street: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/process-st Site: Agent MCP Directory Last reviewed: 2026-11-05 # Process Street: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Process Street at mcp.process.st answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Process Street | | --- | --- | | Domain | process.st | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 59, grade C; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for process.st, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.process.st/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,187 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:01Z https://mcp.process.st/ sent initialize result auth-required (HTTP 401) 2318 ms - 20:04:08Z https://mcp.process.st/ sent initialize result auth-required (HTTP 401) 2187 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="The access token expired or is invalid", resource_metadata="https://mcp.process.st/.well-known/oauth-protected-resource", scope="default" | | Protected resource metadata | mcp.process.st | | Authorization server metadata | auth.process.st | | Registration endpoint | https://auth.process.st/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.process.st/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.process.st/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.process.st/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Process Street. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/process-st/index.md) ## Sources - [Ora score page for process.st](https://ora.ai/score/process.st?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/score) - [Where Process Street was found](https://github.com/mcp/process-street/process-street-mcp), read 4 November 2026 - [Process Street website](https://process.st), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Processmaker MCP server | Agent MCP Directory" description: "Does Processmaker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/processmaker-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Processmaker MCP server | Agent MCP Directory > Does Processmaker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/processmaker-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Processmaker: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Processmaker (processmaker.com), so the connector had nothing to connect to. Ora's cached score for processmaker.com is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Processmaker (registry title: processmaker.com) | | --- | --- | | Domain | processmaker.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for processmaker.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Processmaker. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for processmaker.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Processmaker. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/processmaker-com/index.md) ## Sources - [Ora score page for processmaker.com](https://ora.ai/score/processmaker.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Processmaker was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Processmaker website](https://processmaker.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Projectx MCP server | Agent MCP Directory" description: "Does Projectx have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/projectx-cloud site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Projectx MCP server | Agent MCP Directory > Does Projectx have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/projectx-cloud Site: Agent MCP Directory Last reviewed: 2026-11-05 # Projectx: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Projectx (projectx.cloud), so the connector had nothing to connect to. Ora's cached score for projectx.cloud is 36, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Projectx (registry title: projectx.cloud) | | --- | --- | | Domain | projectx.cloud | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 36, grade D; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for projectx.cloud, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Projectx. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for projectx.cloud, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Projectx. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/projectx-cloud/index.md) ## Sources - [Ora score page for projectx.cloud](https://ora.ai/score/projectx.cloud?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/leaderboard) - [Where Projectx was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Projectx website](https://projectx.cloud), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ProLevelMax MCP server | Agent MCP Directory" description: "ProLevelMax: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/prolevelmax-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ProLevelMax MCP server | Agent MCP Directory > ProLevelMax: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/prolevelmax-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ProLevelMax: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ProLevelMax at prolevelmax.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ProLevelMax | | --- | --- | | Domain | prolevelmax.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for prolevelmax.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://prolevelmax.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,966 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:02Z https://prolevelmax.com/mcp sent initialize result auth-required (HTTP 401) 2359 ms - 20:04:09Z https://prolevelmax.com/mcp sent initialize result auth-required (HTTP 401) 1966 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://prolevelmax.com/.well-known/oauth-protected-resource/mcp", scope="mcp" | | Protected resource metadata | prolevelmax.com | | Authorization server metadata | prolevelmax.com | | Registration endpoint | https://prolevelmax.com/oauth/register | ### The sign-in route, step by step 1. Request `https://prolevelmax.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://prolevelmax.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://prolevelmax.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ProLevelMax. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: prolevelmax.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.prolevelmax/prolevelmax | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/prolevelmax-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=prolevelmax), read 4 November 2026 - [ProLevelMax website](https://prolevelmax.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Prominara MCP server | Agent MCP Directory" description: "Prominara: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/prominara-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Prominara MCP server | Agent MCP Directory > Prominara: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/prominara-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Prominara: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Prominara at mcp.prominara.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Prominara | | --- | --- | | Domain | prominara.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 52, grade C; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for prominara.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.prominara.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 942 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:02Z https://mcp.prominara.com sent initialize result auth-required (HTTP 401) 1425 ms - 20:04:08Z https://mcp.prominara.com sent initialize result auth-required (HTTP 401) 942 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", scope="read", resource_metadata="https://mcp.prominara.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.prominara.com | | Authorization server metadata | prominara.com | | Registration endpoint | https://prominara.com/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.prominara.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.prominara.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://prominara.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Prominara. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.prominara/prominara | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/prominara-com/index.md) ## Sources - [Ora score page for prominara.com](https://ora.ai/score/prominara.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=prominara), read 4 November 2026 - [Prominara website](https://prominara.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Prompeteer MCP server | Agent MCP Directory" description: "Prompeteer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/prompeteer-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Prompeteer MCP server | Agent MCP Directory > Prompeteer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/prompeteer-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Prompeteer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Prompeteer at prompeteer.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Prompeteer | | --- | --- | | Domain | prompeteer.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 75, grade B; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for prompeteer.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://prompeteer.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 749 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:02Z https://prompeteer.ai/mcp sent initialize result auth-required (HTTP 401) 1909 ms - 20:04:09Z https://prompeteer.ai/mcp sent initialize result auth-required (HTTP 401) 749 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://prompeteer.ai/.well-known/oauth-protected-resource/mcp", scope="mcp:read mcp:write mcp:generate memory:read memory:write" | | Protected resource metadata | prompeteer.ai | | Authorization server metadata | prompeteer.ai | | Registration endpoint | https://prompeteer.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://prompeteer.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://prompeteer.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://prompeteer.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Prompeteer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/prompeteer-ai/index.md) ## Sources - [Ora score page for prompeteer.ai](https://ora.ai/score/prompeteer.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/score) - [Where Prompeteer was found](https://github.com/mcp/prompeteer/prompeteer-mcp), read 4 November 2026 - [Prompeteer website](https://prompeteer.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Promptless MCP server | Agent MCP Directory" description: "Does Promptless have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/promptless-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Promptless MCP server | Agent MCP Directory > Does Promptless have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/promptless-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Promptless: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Promptless (promptless.ai), so the connector had nothing to connect to. Ora's cached score for promptless.ai is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Promptless (registry title: promptless.ai) | | --- | --- | | Domain | promptless.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for promptless.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Promptless. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for promptless.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Promptless. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/promptless-ai/index.md) ## Sources - [Ora score page for promptless.ai](https://ora.ai/score/promptless.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Promptless was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Promptless website](https://promptless.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "PropelAuth MCP server | Agent MCP Directory" description: "PropelAuth has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/propelauth-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # PropelAuth MCP server | Agent MCP Directory > PropelAuth has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/propelauth-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # PropelAuth: MCP server, CLI and agent surfaces Yes: PropelAuth runs a public MCP server at mcp.propelauth.com, found by guessing the subdomain, and it listed 11 tools to a client with no credentials on 4 November 2026. Examples: integrate\_propelauth\_frontend, integrate\_propelauth\_backend, integrate\_propelauth\_fullstack. It speaks streamable-http, protocol 2025-11-25. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | PropelAuth (registry title: propelauth.com) | | --- | --- | | Domain | propelauth.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 58, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for propelauth.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.propelauth.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | propelauth_mcp 3.4.0 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 11 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,294 ms over 1 attempt | ### Tools listed 11 tools - integrate\_propelauth\_frontend - integrate\_propelauth\_backend - integrate\_propelauth\_fullstack - integrate\_propelauth\_oauth - propelauth\_custom\_ui - propelauth\_backend\_api - migrate\_to\_propelauth\_frontend - migrate\_to\_propelauth\_backend - migrate\_to\_propelauth\_fullstack - migrate\_to\_propelauth\_users - propelauth\_troubleshooting ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:03Z https://mcp.propelauth.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1552 ms - 20:04:09Z https://mcp.propelauth.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1294 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.propelauth.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for PropelAuth. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/propelauth-com/index.md) ## Sources - [Ora score page for propelauth.com](https://ora.ai/score/propelauth.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/score) - [Where PropelAuth was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [PropelAuth website](https://propelauth.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ptpge MCP server | Agent MCP Directory" description: "Ptpge has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ptpge-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ptpge MCP server | Agent MCP Directory > Ptpge has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ptpge-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ptpge: MCP server, CLI and agent surfaces Yes: Ptpge runs a public MCP server at mcp.ptpge.org that listed 13 tools to a client with no credentials on 4 November 2026. Examples: ptpge\_search\_terms, ptpge\_get\_term, ptpge\_get\_version. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Ptpge | | --- | --- | | Domain | ptpge.org | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for ptpge.org when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.ptpge.org/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | ptpge-mcp 0.42.2 | | Capabilities | tools | | Tools | 13 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 452 ms over 1 attempt | ### Tools listed 13 tools - ptpge\_search\_terms - ptpge\_get\_term - ptpge\_get\_version - ptpge\_browse - ptpge\_get\_product\_envelope - ptpge\_validate\_config - ptpge\_resolve\_color\_notation - ptpge\_fingerprint - ptpge\_expand\_fingerprint - ptpge\_check\_domain - ptpge\_find\_vendors - ptpge\_find\_suppliers - ptpge\_validate\_document ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:02Z https://mcp.ptpge.org/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 639 ms - 20:04:09Z https://mcp.ptpge.org/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 452 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.ptpge.org/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ptpge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ptpge-org/index.md) ## Sources - [Ptpge website](https://ptpge.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Publora MCP server | Agent MCP Directory" description: "Publora: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/publora-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Publora MCP server | Agent MCP Directory > Publora: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/publora-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Publora: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Publora at mcp.publora.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Publora | | --- | --- | | Domain | publora.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 75, grade B; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for publora.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.publora.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 922 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:02Z https://mcp.publora.com/mcp sent initialize result auth-required (HTTP 401) 1015 ms - 20:04:09Z https://mcp.publora.com/mcp sent initialize result auth-required (HTTP 401) 922 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.publora.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.publora.com | | Authorization server metadata | mcp.publora.com | | Registration endpoint | https://mcp.publora.com/register | ### The sign-in route, step by step 1. Request `https://mcp.publora.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.publora.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.publora.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Publora. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.publora/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/publora-com/index.md) ## Sources - [Ora score page for publora.com](https://ora.ai/score/publora.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=publora), read 4 November 2026 - [Publora website](https://publora.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pulumi MCP server | Agent MCP Directory" description: "Does Pulumi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pulumi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pulumi MCP server | Agent MCP Directory > Does Pulumi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pulumi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pulumi: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Pulumi (pulumi.com), so the connector had nothing to connect to. Ora's cached score for pulumi.com is 80, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Pulumi | | --- | --- | | Domain | pulumi.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 80, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pulumi.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Pulumi. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pulumi.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Pulumi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pulumi-com/index.md) ## Sources - [Ora score page for pulumi.com](https://ora.ai/score/pulumi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Pulumi was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Pulumi website](https://pulumi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pushary MCP server | Agent MCP Directory" description: "Pushary has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pushary-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pushary MCP server | Agent MCP Directory > Pushary has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/pushary-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pushary: MCP server, CLI and agent surfaces Yes: Pushary runs a public MCP server at pushary.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: schedule\_reminder, send\_notification, ask\_user. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for pushary.com is 79, grade B, read on 5 November 2026. ## Fact sheet | Company | Pushary (registry title: Pushary: human-in-the-loop for AI agents) | | --- | --- | | Domain | pushary.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 79, grade B; Ora scanned the domain on 7 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for pushary.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://pushary.com/api/mcp/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Pushary 1.0.0 | | Capabilities | tools, resources | | Tools | 6 | | Resources | 5 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 881 ms over 1 attempt | ### Tools listed 6 tools - schedule\_reminder - send\_notification - ask\_user - propose\_scope - wait\_for\_answer - cancel\_question ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:03Z https://pushary.com/api/mcp/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1145 ms - 20:04:09Z https://pushary.com/api/mcp/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 881 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://pushary.com/api/mcp/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pushary. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pushary-com/index.md) ## Sources - [Ora score page for pushary.com](https://ora.ai/score/pushary.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 October 2026, read from GET /api/score) - [Pushary website](https://pushary.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pylon MCP server | Agent MCP Directory" description: "Does Pylon have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/pylonump-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pylon MCP server | Agent MCP Directory > Does Pylon have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/pylonump-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pylon: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Pylon (pylonump.com), so the connector had nothing to connect to. Ora's cached score for pylonump.com is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Pylon (registry title: pylonump.com) | | --- | --- | | Domain | pylonump.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for pylonump.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Pylon. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for pylonump.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Pylon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/pylonump-com/index.md) ## Sources - [Ora score page for pylonump.com](https://ora.ai/score/pylonump.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Pylon was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Pylon website](https://pylonump.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Qualityclouds (qualityclouds.ai) MCP server | Agent MCP Directory" description: "Qualityclouds (qualityclouds.ai): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/qualityclouds-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Qualityclouds (qualityclouds.ai) MCP server | Agent MCP Directory > Qualityclouds (qualityclouds.ai): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/qualityclouds-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Qualityclouds: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Qualityclouds at api.qualityclouds.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Qualityclouds (registry title: Norma by Quality Clouds) | | --- | --- | | Domain | qualityclouds.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for qualityclouds.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.qualityclouds.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 783 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:03Z https://api.qualityclouds.ai/mcp sent initialize result auth-required (HTTP 401) 1026 ms - 20:04:10Z https://api.qualityclouds.ai/mcp sent initialize result auth-required (HTTP 401) 783 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://api.qualityclouds.ai/.well-known/oauth-protected-resource/mcp/" | | Protected resource metadata | api.qualityclouds.ai | | Authorization server metadata | account.qualityclouds.com | | Registration endpoint | https://account.qualityclouds.com/realms/ai-production/clients-registrations/openid-connect | ### The sign-in route, step by step 1. Request `https://api.qualityclouds.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.qualityclouds.ai/.well-known/oauth-protected-resource/mcp/` to find the authorization server. 3. Register a client at the registration endpoint `https://account.qualityclouds.com/realms/ai-production/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Qualityclouds. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.qualityclouds/norma | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/qualityclouds-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=qualityclouds), read 4 November 2026 - [Qualityclouds website](https://qualityclouds.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Qualityclouds (qualityclouds.com) MCP server | Agent MCP Directory" description: "Qualityclouds (qualityclouds.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/qualityclouds-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Qualityclouds (qualityclouds.com) MCP server | Agent MCP Directory > Qualityclouds (qualityclouds.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/qualityclouds-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Qualityclouds: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Qualityclouds at mcp.qualityclouds.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Qualityclouds (registry title: LiveCheck AI) | | --- | --- | | Domain | qualityclouds.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for qualityclouds.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.qualityclouds.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 605 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:04Z https://mcp.qualityclouds.com/mcp sent initialize result auth-required (HTTP 401) 813 ms - 20:04:10Z https://mcp.qualityclouds.com/mcp sent initialize result auth-required (HTTP 401) 605 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer scope="scan", resource_metadata="https://mcp.qualityclouds.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.qualityclouds.com | | Authorization server metadata | mcp.qualityclouds.com | | Registration endpoint | https://mcp.qualityclouds.com/register | ### The sign-in route, step by step 1. Request `https://mcp.qualityclouds.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.qualityclouds.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.qualityclouds.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Qualityclouds. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.qualityclouds/mcp-server-qualityclouds | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/qualityclouds-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=qualityclouds), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Quantstruct MCP server | Agent MCP Directory" description: "Does Quantstruct have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/quantstruct-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Quantstruct MCP server | Agent MCP Directory > Does Quantstruct have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/quantstruct-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Quantstruct: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Quantstruct (quantstruct.com), so the connector had nothing to connect to. Ora's cached score for quantstruct.com is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Quantstruct (registry title: quantstruct.com) | | --- | --- | | Domain | quantstruct.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for quantstruct.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Quantstruct. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for quantstruct.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Quantstruct. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/quantstruct-com/index.md) ## Sources - [Ora score page for quantstruct.com](https://ora.ai/score/quantstruct.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Quantstruct was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Quantstruct website](https://quantstruct.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Queryvary MCP server | Agent MCP Directory" description: "Does Queryvary have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/queryvary-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Queryvary MCP server | Agent MCP Directory > Does Queryvary have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/queryvary-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Queryvary: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Queryvary (queryvary.com), so the connector had nothing to connect to. Ora's cached score for queryvary.com is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Queryvary (registry title: queryvary.com) | | --- | --- | | Domain | queryvary.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for queryvary.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Queryvary. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for queryvary.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Queryvary. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/queryvary-com/index.md) ## Sources - [Ora score page for queryvary.com](https://ora.ai/score/queryvary.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Queryvary was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Quicknode MCP server | Agent MCP Directory" description: "Quicknode: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/quicknode-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Quicknode MCP server | Agent MCP Directory > Quicknode: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/quicknode-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Quicknode: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Quicknode at mcp.quicknode.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Quicknode | | --- | --- | | Domain | quicknode.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 90, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for quicknode.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.quicknode.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 975 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:04Z https://mcp.quicknode.com/mcp sent initialize result auth-required (HTTP 401) 911 ms - 20:04:11Z https://mcp.quicknode.com/mcp sent initialize result auth-required (HTTP 401) 975 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header" | | Protected resource metadata | mcp.quicknode.com | | Authorization server metadata | mcp.quicknode.com | | Registration endpoint | https://mcp.quicknode.com/register | ### The sign-in route, step by step 1. Request `https://mcp.quicknode.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.quicknode.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.quicknode.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Quicknode. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.quicknode.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: quicknode.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/quicknode-com/index.md) ## Sources - [Ora score page for quicknode.com](https://ora.ai/score/quicknode.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Quicknode website](https://quicknode.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Quill MCP server | Agent MCP Directory" description: "Does Quill have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/quill-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Quill MCP server | Agent MCP Directory > Does Quill have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/quill-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Quill: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Quill (quill.co), so the connector had nothing to connect to. Ora's cached score for quill.co is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Quill (registry title: quill.co) | | --- | --- | | Domain | quill.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for quill.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Quill. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for quill.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Quill. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/quill-co/index.md) ## Sources - [Ora score page for quill.co](https://ora.ai/score/quill.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Quill was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Quill website](https://quill.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Quillm MCP server | Agent MCP Directory" description: "Quillm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/quillm-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Quillm MCP server | Agent MCP Directory > Quillm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/quillm-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Quillm: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Quillm at quillm.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Quillm | | --- | --- | | Domain | quillm.ai | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for quillm.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://quillm.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 829 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:04Z https://quillm.ai/mcp sent initialize result auth-required (HTTP 401) 806 ms - 20:04:11Z https://quillm.ai/mcp sent initialize result auth-required (HTTP 401) 829 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://quillm.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | quillm.ai | | Authorization server metadata | quillm.ai | | Registration endpoint | https://quillm.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://quillm.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://quillm.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://quillm.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Quillm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.quillm/quillm | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/quillm-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=quillm), read 4 November 2026 - [Quillm website](https://quillm.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Quorum AI MCP server | Agent MCP Directory" description: "Quorum AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/quorum-dog site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Quorum AI MCP server | Agent MCP Directory > Quorum AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/quorum-dog Site: Agent MCP Directory Last reviewed: 2026-11-05 # Quorum AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Quorum AI at www.quorum.dog answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Quorum AI | | --- | --- | | Domain | quorum.dog | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for quorum.dog when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.quorum.dog/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 938 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:05Z https://www.quorum.dog/mcp sent initialize result auth-required (HTTP 401) 1630 ms - 20:04:11Z https://www.quorum.dog/mcp sent initialize result auth-required (HTTP 401) 938 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.quorum.dog/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | www.quorum.dog | | Authorization server metadata | lfndqkssdggwepekivks.supabase.co | | Registration endpoint | https://lfndqkssdggwepekivks.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://www.quorum.dog/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.quorum.dog/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://lfndqkssdggwepekivks.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Quorum AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.quorum.dog (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/quorum-dog/index.md) ## Sources - [Quorum AI website](https://quorum.dog), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Radar Cnpj MCP server | Agent MCP Directory" description: "Radar Cnpj has an open MCP server with 32 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/radar-cnpj-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Radar Cnpj MCP server | Agent MCP Directory > Radar Cnpj has an open MCP server with 32 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/radar-cnpj-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Radar Cnpj: MCP server, CLI and agent surfaces Yes: Radar Cnpj runs a public MCP server at radar-cnpj.com that listed 32 tools to a client with no credentials on 4 November 2026. Examples: search\_construction, api\_index, health. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Radar Cnpj | | --- | --- | | Domain | radar-cnpj.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for radar-cnpj.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://radar-cnpj.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Radar CNPJ fb0c5518 | | Capabilities | tools, prompts | | Tools | 32 | | Resources | 0 | | Prompts | 5 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,308 ms over 1 attempt | ### Tools listed 32 tools - search\_construction - api\_index - health - get\_cnpj - reveal\_cnpj - sintonia\_seal - dossier\_cnpj - search - suggest - ref - avaliar - local - contact - list\_watches - add\_watch - reactivate\_watches - consulta\_cadastro - consulta\_endereco - consulta\_sugerir - consulta\_cnpj - consulta\_cep - consulta\_planos - consulta\_comprar - consulta\_lote - api\_access - api\_access\_buy - list\_plans - buy\_plan - cancel\_plan - pricing - billing - get\_api\_x402\_cnpj\_by\_cnpj ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:06Z https://radar-cnpj.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2670 ms - 20:04:12Z https://radar-cnpj.com/mcp sent initialize, notifications/initialized, tools/list, prompts/list result verified (HTTP 200) 2308 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://radar-cnpj.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Radar Cnpj. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: radar-cnpj.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.radar-cnpj/radar-cnpj | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/radar-cnpj-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=radar-cnpj), read 4 November 2026 - [Radar Cnpj website](https://radar-cnpj.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Railway MCP server | Agent MCP Directory" description: "Railway: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/railway-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Railway MCP server | Agent MCP Directory > Railway: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/railway-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Railway: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Railway at mcp.railway.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Railway | | --- | --- | | Domain | railway.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 89, grade A; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for railway.com, a vendor-published score) | | Company found through | the vendor's own documentation; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.railway.com/ | | --- | --- | | How it was found | listed in the vendor's own documentation; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 726 ms over 1 attempt | | Documentation | docs.railway.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:05Z https://mcp.railway.com/ sent initialize result auth-required (HTTP 401) 829 ms - 20:04:11Z https://mcp.railway.com/ sent initialize result auth-required (HTTP 401) 726 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.railway.com/.well-known/oauth-protected-resource", scope="workspace:member" | | Protected resource metadata | mcp.railway.com | | Authorization server metadata | backboard.railway.com | | Registration endpoint | https://backboard.railway.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.railway.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.railway.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://backboard.railway.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @railway/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 5.71.0 | | Last publish | 19 October 2026 | | Command names | railway | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: railway.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.railway/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/railway-com/index.md) ## Sources - [Railway MCP documentation](https://docs.railway.com/reference/mcp-server), read 4 November 2026 - [Ora score page for railway.com](https://ora.ai/score/railway.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=railway), read 4 November 2026 - [Railway website](https://railway.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rainforest QA MCP server | Agent MCP Directory" description: "Does Rainforest QA have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rainforestqa-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rainforest QA MCP server | Agent MCP Directory > Does Rainforest QA have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/rainforestqa-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rainforest QA: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rainforest QA (rainforestqa.com), so the connector had nothing to connect to. Ora's cached score for rainforestqa.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rainforest QA (registry title: rainforestqa.com) | | --- | --- | | Domain | rainforestqa.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rainforestqa.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rainforest QA. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rainforestqa.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rainforest QA. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rainforestqa-com/index.md) ## Sources - [Ora score page for rainforestqa.com](https://ora.ai/score/rainforestqa.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where Rainforest QA was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rainforest QA website](https://rainforestqa.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ramp MCP server | Agent MCP Directory" description: "Ramp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ramp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ramp MCP server | Agent MCP Directory > Ramp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/ramp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ramp: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Ramp at ramp-mcp-remote.ramp.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Ramp | | --- | --- | | Domain | ramp.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 68, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ramp.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ramp-mcp-remote.ramp.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 842 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:05Z https://ramp-mcp-remote.ramp.com/mcp sent initialize result auth-required (HTTP 401) 911 ms - 20:04:11Z https://ramp-mcp-remote.ramp.com/mcp sent initialize result auth-required (HTTP 401) 842 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://ramp-mcp-remote.ramp.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | ramp-mcp-remote.ramp.com | | Authorization server metadata | ramp-mcp-remote.ramp.com | | Registration endpoint | https://ramp-mcp-remote.ramp.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://ramp-mcp-remote.ramp.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://ramp-mcp-remote.ramp.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://ramp-mcp-remote.ramp.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ramp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ramp-com/index.md) ## Sources - [Ora score page for ramp.com](https://ora.ai/score/ramp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Ramp was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Ramp website](https://ramp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rampify MCP server | Agent MCP Directory" description: "Rampify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/rampify-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rampify MCP server | Agent MCP Directory > Rampify: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/rampify-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rampify: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rampify at www.rampify.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Rampify | | --- | --- | | Domain | rampify.dev | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for rampify.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.rampify.dev/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,043 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:05Z https://www.rampify.dev/api/mcp sent initialize result auth-required (HTTP 401) 1074 ms - 20:04:12Z https://www.rampify.dev/api/mcp sent initialize result auth-required (HTTP 401) 1043 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.rampify.dev/.well-known/oauth-protected-resource" | | Protected resource metadata | www.rampify.dev | | Authorization server metadata | www.rampify.dev | | Registration endpoint | https://www.rampify.dev/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://www.rampify.dev/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.rampify.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.rampify.dev/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rampify. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.rampify/rampify-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rampify-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=rampify), read 4 November 2026 - [Rampify website](https://rampify.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rancher MCP server | Agent MCP Directory" description: "Does Rancher have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rancher-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rancher MCP server | Agent MCP Directory > Does Rancher have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/rancher-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rancher: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rancher (rancher.com), so the connector had nothing to connect to. Ora's cached score for rancher.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rancher (registry title: rancher.com) | | --- | --- | | Domain | rancher.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 6 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rancher.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rancher. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rancher.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rancher. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rancher-com/index.md) ## Sources - [Ora score page for rancher.com](https://ora.ai/score/rancher.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 August 2026, read from GET /api/leaderboard) - [Where Rancher was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rancher website](https://rancher.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Random Labs MCP server | Agent MCP Directory" description: "Does Random Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/randomlabs-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Random Labs MCP server | Agent MCP Directory > Does Random Labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/randomlabs-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Random Labs: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Random Labs (randomlabs.ai), so the connector had nothing to connect to. Ora's cached score for randomlabs.ai is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Random Labs (registry title: randomlabs.ai) | | --- | --- | | Domain | randomlabs.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for randomlabs.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Random Labs. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for randomlabs.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Random Labs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/randomlabs-ai/index.md) ## Sources - [Ora score page for randomlabs.ai](https://ora.ai/score/randomlabs.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where Random Labs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Random Labs website](https://randomlabs.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rankability MCP server | Agent MCP Directory" description: "Rankability: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/rankability-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rankability MCP server | Agent MCP Directory > Rankability: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/rankability-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rankability: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rankability at app.rankability.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Rankability | | --- | --- | | Domain | rankability.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 63, grade C; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for rankability.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.rankability.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,371 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:07Z https://app.rankability.com/mcp sent initialize result auth-required (HTTP 401) 1502 ms - 20:04:12Z https://app.rankability.com/mcp sent initialize result auth-required (HTTP 401) 1371 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://app.rankability.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | app.rankability.com | | Authorization server metadata | app.rankability.com | | Registration endpoint | https://app.rankability.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://app.rankability.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.rankability.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.rankability.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rankability. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rankability-com/index.md) ## Sources - [Ora score page for rankability.com](https://ora.ai/score/rankability.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [Rankability website](https://rankability.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rapid7 MCP server | Agent MCP Directory" description: "Does Rapid7 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rapid7-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rapid7 MCP server | Agent MCP Directory > Does Rapid7 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/rapid7-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rapid7: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rapid7 (rapid7.com), so the connector had nothing to connect to. Ora's cached score for rapid7.com is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rapid7 (registry title: rapid7.com) | | --- | --- | | Domain | rapid7.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 1,787 on the list of 4 November 2026 | | Ora score | 62, grade C; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for rapid7.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rapid7. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rapid7.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rapid7. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rapid7-com/index.md) ## Sources - [Ora score page for rapid7.com](https://ora.ai/score/rapid7.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/score) - [Where Rapid7 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rapid7 website](https://rapid7.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rapier MCP server | Agent MCP Directory" description: "Rapier has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rapier-website site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rapier MCP server | Agent MCP Directory > Rapier has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/rapier-website Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rapier: MCP server, CLI and agent surfaces Yes: Rapier runs a public MCP server at mcp.rapier.website that listed 6 tools to a client with no credentials on 4 November 2026. Examples: open, read, edit. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Rapier (registry title: Rapier - Markdown Editor & Art) | | --- | --- | | Domain | rapier.website | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for rapier.website when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.rapier.website/door/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | rapier 1.2.55+worker.39d5c5cd-7940-4f3d-8ff0-dc829ef72e02 | | Capabilities | prompts, tools, resources, extensions | | Tools | 6 | | Resources | 100 | | Prompts | 4 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 196 ms over 1 attempt | ### Tools listed 6 tools - open - read - edit - undo - show - export ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:06Z https://mcp.rapier.website/door/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 769 ms - 20:04:11Z https://mcp.rapier.website/door/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 196 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.rapier.website/door/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rapier. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rapier-website/index.md) ## Sources - [Rapier website](https://rapier.website), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Raygun MCP server | Agent MCP Directory" description: "Raygun: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/raygun-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Raygun MCP server | Agent MCP Directory > Raygun: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/raygun-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Raygun: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Raygun at api.raygun.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Raygun | | --- | --- | | Domain | raygun.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 59, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for raygun.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.raygun.com/v3/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 800 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:06Z https://api.raygun.com/v3/mcp sent initialize result auth-required (HTTP 401) 966 ms - 20:04:12Z https://api.raygun.com/v3/mcp sent initialize result auth-required (HTTP 401) 800 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.raygun.com/.well-known/oauth-protected-resource/v3/mcp" | | Protected resource metadata | api.raygun.com | | Authorization server metadata | api.raygun.com | | Registration endpoint | https://api.raygun.com/v3/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.raygun.com/v3/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.raygun.com/.well-known/oauth-protected-resource/v3/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.raygun.com/v3/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Raygun. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/raygun-com/index.md) ## Sources - [Ora score page for raygun.com](https://ora.ai/score/raygun.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Raygun was found](https://github.com/mcp/MindscapeHQ/mcp-server-raygun), read 4 November 2026 - [Raygun website](https://raygun.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Read AI MCP server | Agent MCP Directory" description: "Read AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/read-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Read AI MCP server | Agent MCP Directory > Read AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/read-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Read AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Read AI at api.read.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Read AI | | --- | --- | | Domain | read.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 52, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for read.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.read.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,428 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:07Z https://api.read.ai/mcp sent initialize result auth-required (HTTP 401) 1390 ms - 20:04:13Z https://api.read.ai/mcp sent initialize result auth-required (HTTP 401) 1428 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer scope="mcp:execute", resource_metadata="https://api.read.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.read.ai | | Authorization server metadata | authn.read.ai | | Registration endpoint | https://api.read.ai/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://api.read.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.read.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.read.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Read AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/read-ai/index.md) ## Sources - [Ora score page for read.ai](https://ora.ai/score/read.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Where Read AI was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Read AI website](https://read.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Readdle MCP server | Agent MCP Directory" description: "Does Readdle have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/readdle-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Readdle MCP server | Agent MCP Directory > Does Readdle have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/readdle-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Readdle: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Readdle (readdle.com), so the connector had nothing to connect to. Ora's cached score for readdle.com is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Readdle (registry title: readdle.com) | | --- | --- | | Domain | readdle.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for readdle.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Readdle. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for readdle.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Readdle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/readdle-com/index.md) ## Sources - [Ora score page for readdle.com](https://ora.ai/score/readdle.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Readdle was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Readdle website](https://readdle.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ReadMe MCP server | Agent MCP Directory" description: "Does ReadMe have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/readme-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ReadMe MCP server | Agent MCP Directory > Does ReadMe have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/readme-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ReadMe: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for ReadMe (readme.com), so the connector had nothing to connect to. Ora's cached score for readme.com is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | ReadMe (registry title: readme.com) | | --- | --- | | Domain | readme.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for readme.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for ReadMe. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for readme.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for ReadMe. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/readme-com/index.md) ## Sources - [Ora score page for readme.com](https://ora.ai/score/readme.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where ReadMe was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ReadMe website](https://readme.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Realeyes MCP server | Agent MCP Directory" description: "Realeyes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/realeyes-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Realeyes MCP server | Agent MCP Directory > Realeyes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/realeyes-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Realeyes: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Realeyes at verifeye-mcp-server.realeyes.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Realeyes (registry title: VerifEye) | | --- | --- | | Domain | realeyes.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for realeyes.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://verifeye-mcp-server.realeyes.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 959 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:09Z https://verifeye-mcp-server.realeyes.ai/mcp sent initialize result auth-required (HTTP 401) 2993 ms - 20:04:13Z https://verifeye-mcp-server.realeyes.ai/mcp sent initialize result auth-required (HTTP 401) 959 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | verifeye-mcp-server.realeyes.ai | | Authorization server metadata | verifeye-console.realeyes.ai | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://verifeye-mcp-server.realeyes.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://verifeye-mcp-server.realeyes.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Realeyes. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.realeyes/verifeye | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/realeyes-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=realeyes), read 4 November 2026 - [Realeyes website](https://realeyes.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Recall.ai MCP server | Agent MCP Directory" description: "Does Recall.ai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/recall-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Recall.ai MCP server | Agent MCP Directory > Does Recall.ai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/recall-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Recall.ai: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Recall.ai (recall.ai), so the connector had nothing to connect to. Ora's cached score for recall.ai is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Recall.ai | | --- | --- | | Domain | recall.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for recall.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Recall.ai. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for recall.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Recall.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/recall-ai/index.md) ## Sources - [Ora score page for recall.ai](https://ora.ai/score/recall.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Recall.ai was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Recall.ai website](https://recall.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Redis MCP server | Agent MCP Directory" description: "Redis has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/redis-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Redis MCP server | Agent MCP Directory > Redis has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/redis-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Redis: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Redis; the connector tried mcp.redis.io as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 530, GET HTTP 530 text/html; charset=utf-8). ## Fact sheet | Company | Redis | | --- | --- | | Domain | redis.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Tranco rank | 2,951 on the list of 4 November 2026 | | Ora score | 62, grade C; Ora scanned the domain on 3 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for redis.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.redis.io/mcp | | --- | --- | | How it was found | mcp.redis.io was tried as a guess and did not answer | | HTTP status | 530 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 119 ms over 2 attempts | | Result | no MCP answer (POST HTTP 530, GET HTTP 530 text/html; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:00Z https://mcp.redis.io/mcp sent initialize result no-answer (HTTP 530) 82 ms - 20:01:36Z https://mcp.redis.io/mcp sent initialize result no-answer (HTTP 530) 119 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.redis.io/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 530, GET HTTP 530 text/html; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Redis. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/redis-io/index.md) ## Sources - [Ora score page for redis.io](https://ora.ai/score/redis.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 October 2026, read from GET /api/leaderboard) - [Where Redis was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Redis website](https://redis.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Redpanda MCP server | Agent MCP Directory" description: "Redpanda has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/redpanda-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Redpanda MCP server | Agent MCP Directory > Redpanda has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/redpanda-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Redpanda: MCP server, CLI and agent surfaces Yes: Redpanda runs a public MCP server at docs.redpanda.com that listed 11 tools to a client with no credentials on 4 November 2026. Examples: ask\_redpanda\_question, list\_api\_reference\_pages, search\_api\_reference. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for redpanda.com is 68, grade C, read on 5 November 2026. ## Fact sheet | Company | Redpanda (registry title: redpanda.com) | | --- | --- | | Domain | redpanda.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 68, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for redpanda.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://docs.redpanda.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Redpanda Docs MCP 1.5.0 | | Capabilities | tools | | Tools | 11 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,244 ms over 1 attempt | ### Tools listed 11 tools - ask\_redpanda\_question - list\_api\_reference\_pages - search\_api\_reference - get\_api\_reference\_content - give\_feedback - get\_config\_property - list\_config\_properties - get\_connect\_component - list\_connect\_components - get\_rpk\_command - list\_rpk\_commands ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:08Z https://docs.redpanda.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1274 ms - 20:04:14Z https://docs.redpanda.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1244 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://docs.redpanda.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Redpanda. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.redpanda/docs-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/redpanda-com/index.md) ## Sources - [Ora score page for redpanda.com](https://ora.ai/score/redpanda.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/score) - [Where Redpanda was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.redpanda%2Fdocs-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=redpanda), read 4 November 2026 - [Redpanda website](https://redpanda.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Refine MCP server | Agent MCP Directory" description: "Does Refine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/refine-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Refine MCP server | Agent MCP Directory > Does Refine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/refine-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Refine: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Refine (refine.dev), so the connector had nothing to connect to. Ora's cached score for refine.dev is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Refine (registry title: refine.dev) | | --- | --- | | Domain | refine.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for refine.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Refine. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for refine.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Refine. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/refine-dev/index.md) ## Sources - [Ora score page for refine.dev](https://ora.ai/score/refine.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Refine was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Refine website](https://refine.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Reflect MCP server | Agent MCP Directory" description: "Does Reflect have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/reflect-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Reflect MCP server | Agent MCP Directory > Does Reflect have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/reflect-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Reflect: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Reflect (reflect.app), so the connector had nothing to connect to. Ora's cached score for reflect.app is 46, grade D, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Reflect (registry title: reflect.app) | | --- | --- | | Domain | reflect.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 24 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for reflect.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Reflect. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for reflect.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Reflect. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: reflect.app (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/reflect-app/index.md) ## Sources - [Ora score page for reflect.app](https://ora.ai/score/reflect.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 October 2026, read from GET /api/leaderboard) - [Where Reflect was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Reflect website](https://reflect.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Reflex MCP server | Agent MCP Directory" description: "Does Reflex have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/reflex-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Reflex MCP server | Agent MCP Directory > Does Reflex have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/reflex-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Reflex: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Reflex (reflex.dev), so the connector had nothing to connect to. Ora's cached score for reflex.dev is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Reflex (registry title: reflex.dev) | | --- | --- | | Domain | reflex.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 5 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for reflex.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Reflex. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for reflex.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Reflex. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/reflex-dev/index.md) ## Sources - [Ora score page for reflex.dev](https://ora.ai/score/reflex.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 October 2026, read from GET /api/leaderboard) - [Where Reflex was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Reflex website](https://reflex.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "RegAI MCP server | Agent MCP Directory" description: "RegAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/regai-tw site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # RegAI MCP server | Agent MCP Directory > RegAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/regai-tw Site: Agent MCP Directory Last reviewed: 2026-11-05 # RegAI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for RegAI at mcp.regai.tw answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | RegAI (registry title: RegAI Legal MCP (Taiwan)) | | --- | --- | | Domain | regai.tw | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for regai.tw when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.regai.tw/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,137 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:09Z https://mcp.regai.tw/mcp sent initialize result auth-required (HTTP 401) 1969 ms - 20:04:14Z https://mcp.regai.tw/mcp sent initialize result auth-required (HTTP 401) 1137 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.regai.tw/.well-known/oauth-protected-resource", scope="mcp" | | Protected resource metadata | mcp.regai.tw | | Authorization server metadata | regai.tw | | Registration endpoint | https://regai.tw/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.regai.tw/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.regai.tw/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://regai.tw/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for RegAI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/regai-tw/index.md) ## Sources - [RegAI website](https://regai.tw), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "RegEvidenceHub MCP server | Agent MCP Directory" description: "RegEvidenceHub has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/regevidencehub-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # RegEvidenceHub MCP server | Agent MCP Directory > RegEvidenceHub has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/regevidencehub-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # RegEvidenceHub: MCP server, CLI and agent surfaces Yes: RegEvidenceHub runs a public MCP server at works.regevidencehub.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: sponsor\_change\_checker\_info, list\_supported\_change\_events, licensing\_source\_status. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | RegEvidenceHub (registry title: RegEvidenceHub Sponsor) | | --- | --- | | Domain | regevidencehub.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for regevidencehub.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://works.regevidencehub.com/ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | UK Sponsor Change Checker 0.1.2 | | Capabilities | experimental, prompts, resources, tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 855 ms over 1 attempt | ### Tools listed 4 tools - sponsor\_change\_checker\_info - list\_supported\_change\_events - licensing\_source\_status - assess\_change\_impact ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:09Z https://works.regevidencehub.com/ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1205 ms - 20:04:14Z https://works.regevidencehub.com/ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 855 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://works.regevidencehub.com/ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for RegEvidenceHub. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/regevidencehub-com/index.md) ## Sources - [Where RegEvidenceHub was found](https://github.com/mcp/ChanghuLiu/england-works-watch), read 4 November 2026 - [RegEvidenceHub website](https://regevidencehub.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Reka MCP server | Agent MCP Directory" description: "Reka has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/reka-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Reka MCP server | Agent MCP Directory > Reka has an open MCP server with 17 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/reka-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Reka: MCP server, CLI and agent surfaces Yes: Reka runs a public MCP server at mcp.reka.ai that listed 17 tools to a client with no credentials on 4 November 2026. Examples: upload\_video, list\_videos, get\_video. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for reka.ai is 77, grade B, read on 5 November 2026. ## Fact sheet | Company | Reka | | --- | --- | | Domain | reka.ai | | Category | AI & ML (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 77, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for reka.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.reka.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | reka-vision 0.1.10 | | Capabilities | experimental, prompts, resources, tools | | Tools | 17 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 915 ms over 1 attempt | ### Tools listed 17 tools - upload\_video - list\_videos - get\_video - update\_video - delete\_video - create\_group - list\_groups - delete\_group - index\_video - search\_videos - ask\_video - segment\_video - get\_transcript - get\_captions - get\_scenes - get\_feature\_catalog - summarize\_video ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:09Z https://mcp.reka.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1184 ms - 20:04:14Z https://mcp.reka.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 915 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.reka.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Reka. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.reka/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/reka-ai/index.md) ## Sources - [Ora score page for reka.ai](https://ora.ai/score/reka.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where Reka was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.reka%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=reka), read 4 November 2026 - [Reka website](https://reka.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Release MCP server | Agent MCP Directory" description: "Does Release have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/release-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Release MCP server | Agent MCP Directory > Does Release have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/release-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Release: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Release (release.com), so the connector had nothing to connect to. Ora's cached score for release.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Release (registry title: release.com) | | --- | --- | | Domain | release.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 7 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for release.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Release. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for release.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Release. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/release-com/index.md) ## Sources - [Ora score page for release.com](https://ora.ai/score/release.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 September 2026, read from GET /api/leaderboard) - [Where Release was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Release website](https://release.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Relvato MCP server | Agent MCP Directory" description: "Relvato has an open MCP server with 58 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/relvato-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Relvato MCP server | Agent MCP Directory > Relvato has an open MCP server with 58 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/relvato-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Relvato: MCP server, CLI and agent surfaces Yes: Relvato runs a public MCP server at app.relvato.com that listed 58 tools to a client with no credentials on 4 November 2026. Examples: list\_sites, add\_site, verify\_site. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Relvato | | --- | --- | | Domain | relvato.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for relvato.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.relvato.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | relvato 3.5.1 | | Capabilities | tools | | Tools | 58 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 642 ms over 1 attempt | ### Tools listed 58 tools; the first 40 names are recorded - list\_sites - add\_site - verify\_site - start\_monitoring\_for\_goals - list\_checks - add\_checks - dismiss\_recommendation - calibrate\_site - verify\_vitals\_beacon - site\_overview - get\_site\_health - get\_performance - get\_check - list\_runs - get\_run - get\_fix\_prompt - get\_updates - get\_safe\_update - get\_quarantine - get\_activity\_log - get\_notifications - get\_site\_settings - get\_alert\_settings - get\_status\_pages - list\_heartbeats - update\_check - pause\_monitor\_group - resume\_monitor\_group - update\_visual\_monitor - update\_check\_settings - add\_custom\_check - edit\_custom\_check - reauthor\_custom\_check - approve\_custom\_check - update\_site\_settings - update\_alert\_settings - add\_heartbeat - update\_heartbeat - trigger\_scan - cancel\_queued\_runs ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:09Z https://app.relvato.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1066 ms - 20:04:14Z https://app.relvato.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 642 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://app.relvato.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Relvato. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.relvato/relvato | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/relvato-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=relvato), read 4 November 2026 - [Relvato website](https://relvato.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Relvy MCP server | Agent MCP Directory" description: "Does Relvy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/relvy-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Relvy MCP server | Agent MCP Directory > Does Relvy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/relvy-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Relvy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Relvy (relvy.ai), so the connector had nothing to connect to. Ora's cached score for relvy.ai is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Relvy (registry title: relvy.ai) | | --- | --- | | Domain | relvy.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for relvy.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Relvy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for relvy.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Relvy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/relvy-ai/index.md) ## Sources - [Ora score page for relvy.ai](https://ora.ai/score/relvy.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Relvy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Relvy website](https://relvy.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Remote MCP server | Agent MCP Directory" description: "Remote MCP has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/remote-mcp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Remote MCP server | Agent MCP Directory > Remote MCP has an open MCP server with 1 tool and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/remote-mcp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Remote MCP: MCP server, CLI and agent surfaces Yes: Remote MCP runs a public MCP server at mcp.remote-mcp.com that listed 1 tool to a client with no credentials on 4 November 2026. Examples: ListRemoteMCPServers. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Remote MCP | | --- | --- | | Domain | remote-mcp.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for remote-mcp.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.remote-mcp.com | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Remote MCP Server Directory 1.0.1 | | Capabilities | tools | | Tools | 1 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 145 ms over 1 attempt | ### Tools listed 1 tool - ListRemoteMCPServers ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:09Z https://mcp.remote-mcp.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 629 ms - 20:04:14Z https://mcp.remote-mcp.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 145 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.remote-mcp.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Remote MCP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.remote-mcp/registry-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/remote-mcp-com/index.md) ## Sources - [Where Remote MCP was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=remote-mcp), read 4 November 2026 - [Remote MCP website](https://remote-mcp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Render MCP server | Agent MCP Directory" description: "Render: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/render-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Render MCP server | Agent MCP Directory > Render: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/render-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Render: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Render at mcp.render.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Render | | --- | --- | | Domain | render.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 82, grade B; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for render.com, a vendor-published score) | | Company found through | the vendor's own documentation | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.render.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:06 UTC | | Handshake time | 823 ms over 1 attempt | | Documentation | render.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 1 connection on 4 November 2026, read-only methods only - 20:06:15Z https://mcp.render.com/mcp sent initialize result auth-required (HTTP 401) 823 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer realm="https://mcp.render.com/mcp", resource_metadata="https://mcp.render.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.render.com | | Authorization server metadata | api.render.com | ### The sign-in route, step by step 1. Request `https://mcp.render.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://api.render.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Render. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: render.com (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: render.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/render-com/index.md) ## Sources - [Render MCP documentation](https://render.com/docs/mcp-server), read 4 November 2026 - [Ora score page for render.com](https://ora.ai/score/render.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Render website](https://render.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Replicas MCP server | Agent MCP Directory" description: "Does Replicas have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/replicas-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Replicas MCP server | Agent MCP Directory > Does Replicas have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/replicas-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Replicas: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Replicas (replicas.dev), so the connector had nothing to connect to. Ora's cached score for replicas.dev is 78, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Replicas (registry title: replicas.dev) | | --- | --- | | Domain | replicas.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 78, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for replicas.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Replicas. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for replicas.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Replicas. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/replicas-dev/index.md) ## Sources - [Ora score page for replicas.dev](https://ora.ai/score/replicas.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Replicas was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Replicas website](https://replicas.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Replit MCP server | Agent MCP Directory" description: "Replit has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/replit-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Replit MCP server | Agent MCP Directory > Replit has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/replit-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Replit: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Replit; the connector tried mcp.replit.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: HTTP 200 Does Replo have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/replo-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Replo: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Replo (replo.app), so the connector had nothing to connect to. Ora's cached score for replo.app is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Replo (registry title: replo.app) | | --- | --- | | Domain | replo.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for replo.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Replo. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for replo.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Replo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/replo-app/index.md) ## Sources - [Ora score page for replo.app](https://ora.ai/score/replo.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/leaderboard) - [Where Replo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Replo website](https://replo.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ReplyOnTheFly MCP server | Agent MCP Directory" description: "ReplyOnTheFly has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/replyonthefly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ReplyOnTheFly MCP server | Agent MCP Directory > ReplyOnTheFly has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/replyonthefly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ReplyOnTheFly: MCP server, CLI and agent surfaces Yes: ReplyOnTheFly runs a public MCP server at www.replyonthefly.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: write\_review\_reply, write\_review\_request\_message. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | ReplyOnTheFly | | --- | --- | | Domain | replyonthefly.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for replyonthefly.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.replyonthefly.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | replyonthefly 1.0.0 | | Capabilities | tools, resources | | Tools | 2 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,317 ms over 1 attempt | ### Tools listed 2 tools - write\_review\_reply - write\_review\_request\_message ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:11Z https://www.replyonthefly.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1341 ms - 20:04:16Z https://www.replyonthefly.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1317 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.replyonthefly.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ReplyOnTheFly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.replyonthefly/replyonthefly | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/replyonthefly-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=replyonthefly), read 4 November 2026 - [ReplyOnTheFly website](https://replyonthefly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ReputeMap MCP server | Agent MCP Directory" description: "ReputeMap has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/reputemap-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ReputeMap MCP server | Agent MCP Directory > ReputeMap has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/reputemap-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ReputeMap: MCP server, CLI and agent surfaces Yes: ReputeMap runs a public MCP server at api.reputemap.com that listed 7 tools to a client with no credentials on 4 November 2026. Examples: list\_locations, list\_reviews, get\_review\_stats. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | ReputeMap | | --- | --- | | Domain | reputemap.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for reputemap.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.reputemap.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | reputemap 1.1 | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,429 ms over 1 attempt | ### Tools listed 7 tools - list\_locations - list\_reviews - get\_review\_stats - send\_review\_request - draft\_reply - publish\_reply - get\_usage ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:11Z https://api.reputemap.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1568 ms - 20:04:16Z https://api.reputemap.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1429 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.reputemap.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ReputeMap. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.reputemap/reputemap | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/reputemap-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=reputemap), read 4 November 2026 - [ReputeMap website](https://reputemap.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rescuetime MCP server | Agent MCP Directory" description: "Does Rescuetime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rescuetime-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rescuetime MCP server | Agent MCP Directory > Does Rescuetime have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/rescuetime-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rescuetime: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rescuetime (rescuetime.com), so the connector had nothing to connect to. Ora's cached score for rescuetime.com is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rescuetime (registry title: rescuetime.com) | | --- | --- | | Domain | rescuetime.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rescuetime.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rescuetime. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rescuetime.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rescuetime. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: rescuetime.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rescuetime-com/index.md) ## Sources - [Ora score page for rescuetime.com](https://ora.ai/score/rescuetime.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Rescuetime was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rescuetime website](https://rescuetime.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Resemble AI MCP server | Agent MCP Directory" description: "Resemble AI has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/resemble-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Resemble AI MCP server | Agent MCP Directory > Resemble AI has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/resemble-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Resemble AI: MCP server, CLI and agent surfaces Yes: Resemble AI runs a public MCP server at mcp.resemble.ai that listed 6 tools to a client with no credentials on 4 November 2026. Examples: resemble\_docs\_lookup, resemble\_search, resemble\_get\_page. It speaks sse, protocol 2025-11-25. Ora's cached score for resemble.ai is 74, grade B, read on 5 November 2026. ## Fact sheet | Company | Resemble AI | | --- | --- | | Domain | resemble.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 74, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for resemble.ai, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.resemble.ai/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | sse | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | resemble-ai-docs 1.30.0 | | Capabilities | experimental, resources, tools | | Tools | 6 | | Resources | 19 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,039 ms over 2 attempts | ### Tools listed 6 tools - resemble\_docs\_lookup - resemble\_search - resemble\_get\_page - resemble\_list\_topics - resemble\_api\_endpoint - resemble\_api\_search ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:12Z https://mcp.resemble.ai/sse sent initialize, initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1875 ms - 20:04:17Z https://mcp.resemble.ai/sse sent initialize, initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 2039 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.resemble.ai/sse` over sse. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Resemble AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/resemble-ai/index.md) ## Sources - [Ora score page for resemble.ai](https://ora.ai/score/resemble.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where Resemble AI was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Resemble AI website](https://resemble.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Respan MCP server | Agent MCP Directory" description: "Does Respan have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/respan-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Respan MCP server | Agent MCP Directory > Does Respan have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/respan-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Respan: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Respan (respan.ai), so the connector had nothing to connect to. Ora's cached score for respan.ai is 72, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Respan (registry title: respan.ai) | | --- | --- | | Domain | respan.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for respan.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Respan. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for respan.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Respan. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/respan-ai/index.md) ## Sources - [Ora score page for respan.ai](https://ora.ai/score/respan.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where Respan was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "RestaurantDoctorAI MCP server | Agent MCP Directory" description: "RestaurantDoctorAI has an open MCP server with 22 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/restaurantdoctorai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # RestaurantDoctorAI MCP server | Agent MCP Directory > RestaurantDoctorAI has an open MCP server with 22 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/restaurantdoctorai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # RestaurantDoctorAI: MCP server, CLI and agent surfaces Yes: RestaurantDoctorAI runs a public MCP server at restaurantdoctorai.com that listed 22 tools to a client with no credentials on 4 November 2026. Examples: restaurantdoctor\_get\_questions, restaurantdoctor\_run\_free\_check, restaurantdoctor\_cost\_recipe. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | RestaurantDoctorAI | | --- | --- | | Domain | restaurantdoctorai.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for restaurantdoctorai.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://restaurantdoctorai.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | restaurantdoctorai-profit-check 1.14.0 | | Capabilities | tools | | Tools | 22 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,097 ms over 1 attempt | ### Tools listed 22 tools - restaurantdoctor\_get\_questions - restaurantdoctor\_run\_free\_check - restaurantdoctor\_cost\_recipe - restaurantdoctor\_check\_website - restaurantdoctor\_deadlines - restaurantdoctor\_search\_knowledge - restaurantdoctor\_list\_knowledge - restaurantdoctor\_read\_knowledge - restaurantdoctor\_prime\_cost - restaurantdoctor\_labor\_cost - restaurantdoctor\_break\_even - restaurantdoctor\_restaurant\_budget - restaurantdoctor\_plate\_cost - restaurantdoctor\_delivery\_price - restaurantdoctor\_menu\_calories - restaurantdoctor\_fica\_tip\_credit - restaurantdoctor\_card\_fees - restaurantdoctor\_booking\_fees - restaurantdoctor\_cash\_out - restaurantdoctor\_tip\_out - restaurantdoctor\_par\_levels - restaurantdoctor\_prime\_cost\_consult ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:12Z https://restaurantdoctorai.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2364 ms - 20:04:16Z https://restaurantdoctorai.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1097 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://restaurantdoctorai.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for RestaurantDoctorAI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: restaurantdoctorai.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.restaurantdoctorai/profit-check | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/restaurantdoctorai-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=restaurantdoctorai), read 4 November 2026 - [RestaurantDoctorAI website](https://restaurantdoctorai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ResumeQuick MCP server | Agent MCP Directory" description: "ResumeQuick: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/resumequick-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ResumeQuick MCP server | Agent MCP Directory > ResumeQuick: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/resumequick-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # ResumeQuick: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ResumeQuick at mcp.resumequick.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ResumeQuick | | --- | --- | | Domain | resumequick.app | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for resumequick.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.resumequick.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 346 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:11Z https://mcp.resumequick.app/mcp sent initialize result auth-required (HTTP 401) 728 ms - 20:04:15Z https://mcp.resumequick.app/mcp sent initialize result auth-required (HTTP 401) 346 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.resumequick.app/.well-known/oauth-protected-resource/mcp", scope="resumequick" | | Protected resource metadata | mcp.resumequick.app | | Authorization server metadata | mcp.resumequick.app | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.resumequick.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.resumequick.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ResumeQuick. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.resumequick/resumequick | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/resumequick-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=resumequick), read 4 November 2026 - [ResumeQuick website](https://resumequick.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Retool MCP server | Agent MCP Directory" description: "Does Retool have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/retool-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Retool MCP server | Agent MCP Directory > Does Retool have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/retool-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Retool: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Retool (retool.com), so the connector had nothing to connect to. Ora's cached score for retool.com is 78, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Retool | | --- | --- | | Domain | retool.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 78, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for retool.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Retool. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for retool.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Retool. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/retool-com/index.md) ## Sources - [Ora score page for retool.com](https://ora.ai/score/retool.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Retool was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Retool website](https://retool.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rev MCP server | Agent MCP Directory" description: "Does Rev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/rev-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rev MCP server | Agent MCP Directory > Does Rev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/rev-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rev: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rev (rev.com), so the connector had nothing to connect to. Ora's cached score for rev.com is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rev (registry title: rev.com) | | --- | --- | | Domain | rev.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rev.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rev. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rev.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rev-com/index.md) ## Sources - [Ora score page for rev.com](https://ora.ai/score/rev.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/leaderboard) - [Where Rev was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rev website](https://rev.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Revyl MCP server | Agent MCP Directory" description: "Does Revyl have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/revyl-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Revyl MCP server | Agent MCP Directory > Does Revyl have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/revyl-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Revyl: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Revyl (revyl.ai), so the connector had nothing to connect to. Ora's cached score for revyl.ai is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Revyl (registry title: revyl.ai) | | --- | --- | | Domain | revyl.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for revyl.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Revyl. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for revyl.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Revyl. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/revyl-ai/index.md) ## Sources - [Ora score page for revyl.ai](https://ora.ai/score/revyl.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Where Revyl was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Revyl website](https://revyl.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rivet MCP server | Agent MCP Directory" description: "Rivet: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rivet-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rivet MCP server | Agent MCP Directory > Rivet: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/rivet-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rivet: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rivet at mcp.rivet.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Rivet | | --- | --- | | Domain | rivet.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 71, grade B; Ora scanned the domain on 7 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rivet.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.rivet.dev/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,207 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:13Z https://mcp.rivet.dev/mcp sent initialize result auth-required (HTTP 401) 1697 ms - 20:04:17Z https://mcp.rivet.dev/mcp sent initialize result auth-required (HTTP 401) 1207 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.rivet.dev/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.rivet.dev | | Authorization server metadata | cloud-api.rivet.dev | | Registration endpoint | https://cloud-api.rivet.dev/api/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.rivet.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.rivet.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://cloud-api.rivet.dev/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rivet. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.rivet/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rivet-dev/index.md) ## Sources - [Ora score page for rivet.dev](https://ora.ai/score/rivet.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 October 2026, read from GET /api/leaderboard) - [Where Rivet was found](https://registry.modelcontextprotocol.io/v0/servers?search=dev.rivet%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=rivet), read 4 November 2026 - [Rivet website](https://rivet.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Robocorp MCP server | Agent MCP Directory" description: "Does Robocorp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/robocorp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Robocorp MCP server | Agent MCP Directory > Does Robocorp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/robocorp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Robocorp: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Robocorp (robocorp.com), so the connector had nothing to connect to. Ora's cached score for robocorp.com is 41, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Robocorp (registry title: robocorp.com) | | --- | --- | | Domain | robocorp.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 41, grade D; Ora scanned the domain on 7 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for robocorp.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Robocorp. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for robocorp.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Robocorp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/robocorp-com/index.md) ## Sources - [Ora score page for robocorp.com](https://ora.ai/score/robocorp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 October 2026, read from GET /api/leaderboard) - [Where Robocorp was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Robocorp website](https://robocorp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Roboflow MCP server | Agent MCP Directory" description: "Roboflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/roboflow-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Roboflow MCP server | Agent MCP Directory > Roboflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/roboflow-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Roboflow: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Roboflow at mcp.roboflow.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Roboflow (registry title: Roboflow (Official)) | | --- | --- | | Domain | roboflow.com | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 72, grade B; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for roboflow.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.roboflow.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,477 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:13Z https://mcp.roboflow.com/mcp sent initialize result auth-required (HTTP 401) 1555 ms - 20:04:17Z https://mcp.roboflow.com/mcp sent initialize result auth-required (HTTP 401) 1477 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.roboflow.com/.well-known/oauth-protected-resource/mcp", scope="workspace:read project:create project:read project:update workflow:create workflow:read workflow:update folder:create folder:read folder:update folder:delete image:create image:read image:tag image:annotate model:infer model:deploy model:manage model:compile model-eval:read workflow-evals:read workflow-evals:write workflow-evals:run workflow-evals:export device:read device:update vision-events:read vision-events:write vision-events:manage workspace-stats:read workspace-announcement:read workspace-announcement:write batch:create batch:read batch:admin-read batch:update batch:delete version:create version:read version:update training-job:create annotation-job:create annotation-job:read annotation-job:update annotation-job:submit-review annotation-job:review annotation-job:return-edits | | Protected resource metadata | mcp.roboflow.com | | Authorization server metadata | app.roboflow.com | | Registration endpoint | https://app.roboflow.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.roboflow.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.roboflow.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.roboflow.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Roboflow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.roboflow/roboflow-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/roboflow-com/index.md) ## Sources - [Ora score page for roboflow.com](https://ora.ai/score/roboflow.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where Roboflow was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.roboflow%2Froboflow-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=roboflow), read 4 November 2026 - [Roboflow website](https://roboflow.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "RoboSystems MCP server | Agent MCP Directory" description: "RoboSystems: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/robosystems-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # RoboSystems MCP server | Agent MCP Directory > RoboSystems: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/robosystems-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # RoboSystems: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for RoboSystems at api.robosystems.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | RoboSystems | | --- | --- | | Domain | robosystems.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for robosystems.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.robosystems.ai/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,406 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:13Z https://api.robosystems.ai/v1/mcp sent initialize result auth-required (HTTP 401) 1510 ms - 20:04:18Z https://api.robosystems.ai/v1/mcp sent initialize result auth-required (HTTP 401) 1406 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.robosystems.ai/.well-known/oauth-protected-resource/v1/mcp", scope="mcp" | | Protected resource metadata | api.robosystems.ai | | Authorization server metadata | api.robosystems.ai | | Registration endpoint | https://api.robosystems.ai/v1/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.robosystems.ai/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.robosystems.ai/.well-known/oauth-protected-resource/v1/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.robosystems.ai/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for RoboSystems. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.robosystems/robosystems | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/robosystems-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=robosystems), read 4 November 2026 - [RoboSystems website](https://robosystems.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "RocketReach MCP server | Agent MCP Directory" description: "RocketReach: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/rocketreach-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # RocketReach MCP server | Agent MCP Directory > RocketReach: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/rocketreach-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # RocketReach: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for RocketReach at mcp.rocketreach.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | RocketReach | | --- | --- | | Domain | rocketreach.co | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 53, grade C; Ora scanned the domain on 28 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rocketreach.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.rocketreach.co/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,627 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:14Z https://mcp.rocketreach.co/mcp sent initialize result auth-required (HTTP 401) 2137 ms - 20:04:18Z https://mcp.rocketreach.co/mcp sent initialize result auth-required (HTTP 401) 1627 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.rocketreach.co/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.rocketreach.co | | Authorization server metadata | rocketreach.co | | Registration endpoint | https://rocketreach.co/mcp-oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.rocketreach.co/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.rocketreach.co/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://rocketreach.co/mcp-oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for RocketReach. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: rocketreach.co/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.rocketreach/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rocketreach-co/index.md) ## Sources - [Ora score page for rocketreach.co](https://ora.ai/score/rocketreach.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 August 2026, read from GET /api/leaderboard) - [Where RocketReach was found](https://registry.modelcontextprotocol.io/v0/servers?search=co.rocketreach%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=rocketreach), read 4 November 2026 - [RocketReach website](https://rocketreach.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rokha MCP server | Agent MCP Directory" description: "Rokha has an open MCP server with 30 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rokha-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rokha MCP server | Agent MCP Directory > Rokha has an open MCP server with 30 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/rokha-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rokha: MCP server, CLI and agent surfaces Yes: Rokha runs a public MCP server at rokha.ai that listed 30 tools to a client with no credentials on 4 November 2026. Examples: send\_agent\_message, registry\_search, registry\_get\_skill. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Rokha | | --- | --- | | Domain | rokha.ai | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for rokha.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://rokha.ai/mcp/jsonrpc | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | rokha 1.0.0 | | Capabilities | prompts, resources, tools | | Tools | 30 | | Resources | 0 | | Prompts | 2 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,514 ms over 1 attempt | ### Tools listed 30 tools - send\_agent\_message - registry\_search - registry\_get\_skill - rig\_search - rig\_get - trace\_search - rig\_run - skill\_author - auth\_resolve - rig\_author - trace\_get - registry\_publish - auth\_wallet\_challenge - auth\_wallet\_verify - studio\_doors - market\_search - mark\_check - hunt\_report - page\_me - page\_claim - registry\_list\_server - registry\_adopt - free\_tier\_status - agent\_create - product\_get - product\_checkout - purchases\_mine - subscribe - subscription\_status - tools\_catalog ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:15Z https://rokha.ai/mcp/jsonrpc sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2644 ms - 20:04:19Z https://rokha.ai/mcp/jsonrpc sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2514 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://rokha.ai/mcp/jsonrpc` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rokha. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.rokha/rokha | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rokha-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=rokha), read 4 November 2026 - [Rokha website](https://rokha.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rollbar MCP server | Agent MCP Directory" description: "Does Rollbar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rollbar-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rollbar MCP server | Agent MCP Directory > Does Rollbar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/rollbar-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rollbar: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rollbar (rollbar.com), so the connector had nothing to connect to. Ora's cached score for rollbar.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rollbar (registry title: rollbar.com) | | --- | --- | | Domain | rollbar.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rollbar.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rollbar. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rollbar.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rollbar. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rollbar-com/index.md) ## Sources - [Ora score page for rollbar.com](https://ora.ai/score/rollbar.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/leaderboard) - [Where Rollbar was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rollbar website](https://rollbar.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rootly MCP server | Agent MCP Directory" description: "Rootly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rootly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rootly MCP server | Agent MCP Directory > Rootly: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/rootly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rootly: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rootly at mcp.rootly.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Rootly | | --- | --- | | Domain | rootly.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 83, grade B; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rootly.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.rootly.com/sse | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 925 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:13Z https://mcp.rootly.com/sse sent initialize result auth-required (HTTP 401) 728 ms - 20:04:18Z https://mcp.rootly.com/sse sent initialize result auth-required (HTTP 401) 925 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.rootly.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.rootly.com | | Authorization server metadata | rootly.com | | Registration endpoint | https://rootly.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.rootly.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.rootly.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://rootly.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rootly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: rootly.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.rootly/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rootly-com/index.md) ## Sources - [Ora score page for rootly.com](https://ora.ai/score/rootly.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where Rootly was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.rootly%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=rootly), read 4 November 2026 - [Rootly website](https://rootly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rownd MCP server | Agent MCP Directory" description: "Does Rownd have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rownd-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rownd MCP server | Agent MCP Directory > Does Rownd have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/rownd-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rownd: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rownd (rownd.ai), so the connector had nothing to connect to. Ora's cached score for rownd.ai is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rownd (registry title: rownd.ai) | | --- | --- | | Domain | rownd.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 5 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rownd.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rownd. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rownd.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rownd. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rownd-ai/index.md) ## Sources - [Ora score page for rownd.ai](https://ora.ai/score/rownd.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 September 2026, read from GET /api/leaderboard) - [Where Rownd was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rownd website](https://rownd.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rta MCP server | Agent MCP Directory" description: "Rta has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rta-lat site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rta MCP server | Agent MCP Directory > Rta has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/rta-lat Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rta: MCP server, CLI and agent surfaces Yes: Rta runs a public MCP server at attest.rta.lat that listed 2 tools to a client with no credentials on 4 November 2026. Examples: verify\_artifact, verify\_artifact\_batch. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Rta (registry title: attest: verification for AI agent artifacts) | | --- | --- | | Domain | rta.lat | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for rta.lat when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://attest.rta.lat/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | attest 0.1.0 | | Capabilities | tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,604 ms over 1 attempt | ### Tools listed 2 tools - verify\_artifact - verify\_artifact\_batch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:16Z https://attest.rta.lat/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2887 ms - 20:04:20Z https://attest.rta.lat/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2604 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://attest.rta.lat/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rta. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rta-lat/index.md) ## Sources - [Where Rta was found](https://github.com/mcp/mrpkk/attest), read 4 November 2026 - [Rta website](https://rta.lat), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rulebase MCP server | Agent MCP Directory" description: "Rulebase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/rulebase-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rulebase MCP server | Agent MCP Directory > Rulebase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/rulebase-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rulebase: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rulebase at mcp.rulebase.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Rulebase | | --- | --- | | Domain | rulebase.co | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rulebase.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.rulebase.co/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,835 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:16Z https://mcp.rulebase.co/mcp sent initialize result auth-required (HTTP 401) 1971 ms - 20:04:19Z https://mcp.rulebase.co/mcp sent initialize result auth-required (HTTP 401) 1835 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="unauthorized", error_description="Authorization needed", scope="openid email offline_access", resource_metadata="https://mcp.rulebase.co/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.rulebase.co | | Authorization server metadata | auth.rulebase.co | | Registration endpoint | https://auth.rulebase.co/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.rulebase.co/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.rulebase.co/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.rulebase.co/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rulebase. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.rulebase/rulebase | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rulebase-co/index.md) ## Sources - [Ora score page for rulebase.co](https://ora.ai/score/rulebase.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 September 2026, read from GET /api/leaderboard) - [Where Rulebase was found](https://registry.modelcontextprotocol.io/v0/servers?search=co.rulebase%2Frulebase), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=rulebase), read 4 November 2026 - [Rulebase website](https://rulebase.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rulebricks MCP server | Agent MCP Directory" description: "Does Rulebricks have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rulebricks-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rulebricks MCP server | Agent MCP Directory > Does Rulebricks have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/rulebricks-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rulebricks: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Rulebricks (rulebricks.com), so the connector had nothing to connect to. Ora's cached score for rulebricks.com is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Rulebricks (registry title: rulebricks.com) | | --- | --- | | Domain | rulebricks.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rulebricks.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Rulebricks. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for rulebricks.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Rulebricks. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rulebricks-com/index.md) ## Sources - [Ora score page for rulebricks.com](https://ora.ai/score/rulebricks.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/leaderboard) - [Where Rulebricks was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Rulebricks website](https://rulebricks.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Run MCP server | Agent MCP Directory" description: "Does Run have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/run-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Run MCP server | Agent MCP Directory > Does Run have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/run-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Run: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Run (run.ai), so the connector had nothing to connect to. Ora's cached score for run.ai is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Run (registry title: run.ai) | | --- | --- | | Domain | run.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 6 May 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for run.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Run. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for run.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Run. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/run-ai/index.md) ## Sources - [Ora score page for run.ai](https://ora.ai/score/run.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 May 2026, read from GET /api/leaderboard) - [Where Run was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "RunAnywhere MCP server | Agent MCP Directory" description: "Does RunAnywhere have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/runanywhere-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # RunAnywhere MCP server | Agent MCP Directory > Does RunAnywhere have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/runanywhere-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # RunAnywhere: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for RunAnywhere (runanywhere.ai), so the connector had nothing to connect to. Ora's cached score for runanywhere.ai is 72, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | RunAnywhere (registry title: runanywhere.ai) | | --- | --- | | Domain | runanywhere.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runanywhere.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for RunAnywhere. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for runanywhere.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for RunAnywhere. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runanywhere-ai/index.md) ## Sources - [Ora score page for runanywhere.ai](https://ora.ai/score/runanywhere.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where RunAnywhere was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [RunAnywhere website](https://runanywhere.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Runautomat MCP server | Agent MCP Directory" description: "Runautomat has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/runautomat-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Runautomat MCP server | Agent MCP Directory > Runautomat has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/runautomat-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Runautomat: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Runautomat; the connector tried mcp.runautomat.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | Runautomat (registry title: runautomat.com) | | --- | --- | | Domain | runautomat.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 65, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runautomat.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.runautomat.com/mcp | | --- | --- | | How it was found | mcp.runautomat.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 868 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:15Z https://mcp.runautomat.com/mcp sent initialize result no-answer (HTTP 404) 822 ms - 20:04:19Z https://mcp.runautomat.com/mcp sent initialize result no-answer (HTTP 404) 868 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.runautomat.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Runautomat. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runautomat-com/index.md) ## Sources - [Ora score page for runautomat.com](https://ora.ai/score/runautomat.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Runautomat was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Runautomat website](https://runautomat.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Runcaptain MCP server | Agent MCP Directory" description: "Runcaptain: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/runcaptain-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Runcaptain MCP server | Agent MCP Directory > Runcaptain: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/runcaptain-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Runcaptain: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Runcaptain; the connector's guess at mcp.runcaptain.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Runcaptain (registry title: runcaptain.com) | | --- | --- | | Domain | runcaptain.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 57, grade C; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runcaptain.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.runcaptain.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,920 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:16Z https://mcp.runcaptain.com/mcp sent initialize result auth-required (HTTP 401) 1876 ms - 20:04:20Z https://mcp.runcaptain.com/mcp sent initialize result auth-required (HTTP 401) 1920 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="captain:read", resource_metadata="https://mcp.runcaptain.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.runcaptain.com | | Authorization server metadata | api.captain.dev | | Registration endpoint | https://api.captain.dev/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.runcaptain.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.runcaptain.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.captain.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Runcaptain. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runcaptain-com/index.md) ## Sources - [Ora score page for runcaptain.com](https://ora.ai/score/runcaptain.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/leaderboard) - [Where Runcaptain was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Runcaptain website](https://runcaptain.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Runcascade MCP server | Agent MCP Directory" description: "Does Runcascade have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/runcascade-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Runcascade MCP server | Agent MCP Directory > Does Runcascade have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/runcascade-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Runcascade: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Runcascade (runcascade.com), so the connector had nothing to connect to. Ora's cached score for runcascade.com is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Runcascade (registry title: runcascade.com) | | --- | --- | | Domain | runcascade.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runcascade.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Runcascade. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for runcascade.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Runcascade. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runcascade-com/index.md) ## Sources - [Ora score page for runcascade.com](https://ora.ai/score/runcascade.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Runcascade was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Runcomfy MCP server | Agent MCP Directory" description: "Runcomfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/runcomfy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Runcomfy MCP server | Agent MCP Directory > Runcomfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/runcomfy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Runcomfy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Runcomfy at mcp.runcomfy.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Runcomfy | | --- | --- | | Domain | runcomfy.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for runcomfy.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.runcomfy.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 106 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:15Z https://mcp.runcomfy.com/mcp sent initialize result auth-required (HTTP 401) 422 ms - 20:04:19Z https://mcp.runcomfy.com/mcp sent initialize result auth-required (HTTP 401) 106 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.runcomfy.com/.well-known/oauth-protected-resource/mcp", scope="mcp:tools" | | Protected resource metadata | mcp.runcomfy.com | | Authorization server metadata | mcp.runcomfy.com | | Registration endpoint | https://mcp.runcomfy.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.runcomfy.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.runcomfy.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.runcomfy.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Runcomfy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runcomfy-com/index.md) ## Sources - [Where Runcomfy was found](https://github.com/mcp/runcomfy-com/runcomfy-mcp), read 4 November 2026 - [Runcomfy website](https://runcomfy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "RunLocal MCP server | Agent MCP Directory" description: "Does RunLocal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/runlocal-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # RunLocal MCP server | Agent MCP Directory > Does RunLocal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/runlocal-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # RunLocal: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for RunLocal (runlocal.ai), so the connector had nothing to connect to. Ora's cached score for runlocal.ai is 44, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | RunLocal (registry title: runlocal.ai) | | --- | --- | | Domain | runlocal.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 44, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runlocal.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for RunLocal. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for runlocal.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for RunLocal. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runlocal-ai/index.md) ## Sources - [Ora score page for runlocal.ai](https://ora.ai/score/runlocal.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/leaderboard) - [Where RunLocal was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [RunLocal website](https://runlocal.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Runpulse MCP server | Agent MCP Directory" description: "Runpulse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/runpulse-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Runpulse MCP server | Agent MCP Directory > Runpulse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/runpulse-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Runpulse: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Runpulse; the connector's guess at mcp.runpulse.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Runpulse (registry title: runpulse.com) | | --- | --- | | Domain | runpulse.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runpulse.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.runpulse.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,384 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:17Z https://mcp.runpulse.com/mcp sent initialize result auth-required (HTTP 401) 1529 ms - 20:04:20Z https://mcp.runpulse.com/mcp sent initialize result auth-required (HTTP 401) 1384 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.runpulse.com/.well-known/oauth-protected-resource", scope="extract" | | Protected resource metadata | mcp.runpulse.com | | Authorization server metadata | fastapi-dev.api.runpulse.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.runpulse.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.runpulse.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Runpulse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runpulse-com/index.md) ## Sources - [Ora score page for runpulse.com](https://ora.ai/score/runpulse.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Runpulse was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Runpulse website](https://runpulse.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Runtm MCP server | Agent MCP Directory" description: "Does Runtm have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/runtm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Runtm MCP server | Agent MCP Directory > Does Runtm have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/runtm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Runtm: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Runtm (runtm.com), so the connector had nothing to connect to. Ora's cached score for runtm.com is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Runtm (registry title: runtm.com) | | --- | --- | | Domain | runtm.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 28 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runtm.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Runtm. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for runtm.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Runtm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runtm-com/index.md) ## Sources - [Ora score page for runtm.com](https://ora.ai/score/runtm.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 August 2026, read from GET /api/leaderboard) - [Where Runtm was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Runtm website](https://runtm.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Runtrellis MCP server | Agent MCP Directory" description: "Does Runtrellis have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/runtrellis-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Runtrellis MCP server | Agent MCP Directory > Does Runtrellis have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/runtrellis-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Runtrellis: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Runtrellis (runtrellis.com), so the connector had nothing to connect to. Ora's cached score for runtrellis.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Runtrellis (registry title: runtrellis.com) | | --- | --- | | Domain | runtrellis.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for runtrellis.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Runtrellis. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for runtrellis.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Runtrellis. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/runtrellis-com/index.md) ## Sources - [Ora score page for runtrellis.com](https://ora.ai/score/runtrellis.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Runtrellis was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Runtrellis website](https://runtrellis.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Rus.sh MCP server | Agent MCP Directory" description: "Rus.sh: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/rus-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Rus.sh MCP server | Agent MCP Directory > Rus.sh: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/rus-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Rus.sh: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rus.sh at rus.sh answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Rus.sh | | --- | --- | | Domain | rus.sh | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for rus.sh when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://rus.sh/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 159 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:17Z https://rus.sh/mcp sent initialize result auth-required (HTTP 401) 1221 ms - 20:04:20Z https://rus.sh/mcp sent initialize result auth-required (HTTP 401) 159 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://rus.sh/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | rus.sh | | Authorization server metadata | rus.sh | | Registration endpoint | https://rus.sh/oauth/register | ### The sign-in route, step by step 1. Request `https://rus.sh/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://rus.sh/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://rus.sh/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Rus.sh. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/rus-sh/index.md) ## Sources - [Rus.sh website](https://rus.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ryvn MCP server | Agent MCP Directory" description: "Does Ryvn have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/ryvn-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ryvn MCP server | Agent MCP Directory > Does Ryvn have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/ryvn-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ryvn: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ryvn (ryvn.ai), so the connector had nothing to connect to. Ora's cached score for ryvn.ai is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ryvn (registry title: ryvn.ai) | | --- | --- | | Domain | ryvn.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ryvn.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ryvn. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ryvn.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ryvn. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ryvn-ai/index.md) ## Sources - [Ora score page for ryvn.ai](https://ora.ai/score/ryvn.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where Ryvn was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ryvn website](https://ryvn.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "S2 MCP server | Agent MCP Directory" description: "Does S2 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/s2-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # S2 MCP server | Agent MCP Directory > Does S2 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/s2-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # S2: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for S2 (s2.dev), so the connector had nothing to connect to. Ora's cached score for s2.dev is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | S2 (registry title: s2.dev) | | --- | --- | | Domain | s2.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for s2.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for S2. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for s2.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for S2. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/s2-dev/index.md) ## Sources - [Ora score page for s2.dev](https://ora.ai/score/s2.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where S2 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [S2 website](https://s2.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sadiqoon MCP server | Agent MCP Directory" description: "Sadiqoon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/sadiqoon-uk site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sadiqoon MCP server | Agent MCP Directory > Sadiqoon: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/sadiqoon-uk Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sadiqoon: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sadiqoon at mcp.khamenei-online.org answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sadiqoon (registry title: SAKH: Ayatollah Khamenei Research Corpus) | | --- | --- | | Domain | sadiqoon.uk | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for sadiqoon.uk when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.khamenei-online.org/mcp/sakh | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 691 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:17Z https://mcp.khamenei-online.org/mcp/sakh sent initialize result auth-required (HTTP 401) 1008 ms - 20:04:20Z https://mcp.khamenei-online.org/mcp/sakh sent initialize result auth-required (HTTP 401) 691 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.khamenei-online.org/.well-known/oauth-protected-resource/mcp/sakh" | | Protected resource metadata | mcp.khamenei-online.org | | Authorization server metadata | auth.sadiqoon.com | | Registration endpoint | https://auth.sadiqoon.com/realms/sadiqoon/clients-registrations/openid-connect | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.khamenei-online.org/mcp/sakh` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.khamenei-online.org/.well-known/oauth-protected-resource/mcp/sakh` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.sadiqoon.com/realms/sadiqoon/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sadiqoon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sadiqoon-uk/index.md) ## Sources - [Sadiqoon website](https://sadiqoon.uk), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Saifs MCP server | Agent MCP Directory" description: "Saifs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/saifs-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Saifs MCP server | Agent MCP Directory > Saifs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/saifs-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Saifs: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Saifs at mcp.saifs.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Saifs (registry title: Assessment Intelligence) | | --- | --- | | Domain | saifs.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for saifs.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.saifs.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,112 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:18Z https://mcp.saifs.ai/mcp sent initialize result auth-required (HTTP 401) 1397 ms - 20:04:21Z https://mcp.saifs.ai/mcp sent initialize result auth-required (HTTP 401) 1112 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.saifs.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.saifs.ai | | Authorization server metadata | multiplewords.in | | Registration endpoint | https://multiplewords.in/o/register/ | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.saifs.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.saifs.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://multiplewords.in/o/register/` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Saifs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.saifs/assessment-intelligence, ai.saifs/code-execution, ai.saifs/collections-optimizer and 2 more | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/saifs-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=saifs), read 4 November 2026 - [Saifs website](https://saifs.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Salesforce MCP server | Agent MCP Directory" description: "Does Salesforce have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/salesforce-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Salesforce MCP server | Agent MCP Directory > Does Salesforce have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/salesforce-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Salesforce: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Salesforce (salesforce.com), so the connector had nothing to connect to. A CLI is on record: @salesforce/cli on npm. Ora's cached score for salesforce.com is 51, grade C, read on 5 November 2026. ## Fact sheet | Company | Salesforce | | --- | --- | | Domain | salesforce.com | | Category | CRM (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 293 on the list of 4 November 2026 | | Ora score | 51, grade C; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for salesforce.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Salesforce. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for salesforce.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | @salesforce/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 2.157.8 | | Last publish | 3 November 2026 | | Command names | sf, sfdx | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/salesforce-com/index.md) ## Sources - [Ora score page for salesforce.com](https://ora.ai/score/salesforce.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Salesforce website](https://salesforce.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Salvy MCP server | Agent MCP Directory" description: "Salvy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/salvy-com-br site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Salvy MCP server | Agent MCP Directory > Salvy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/salvy-com-br Site: Agent MCP Directory Last reviewed: 2026-11-05 # Salvy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Salvy at mcp.salvy.com.br answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Salvy | | --- | --- | | Domain | salvy.com.br | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 76, grade B; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for salvy.com.br, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.salvy.com.br/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,080 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:18Z https://mcp.salvy.com.br/mcp sent initialize result auth-required (HTTP 401) 1560 ms - 20:04:21Z https://mcp.salvy.com.br/mcp sent initialize result auth-required (HTTP 401) 1080 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.salvy.com.br/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.salvy.com.br | | Authorization server metadata | clerk.salvy.com.br | | Registration endpoint | https://clerk.salvy.com.br/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.salvy.com.br/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.salvy.com.br/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.salvy.com.br/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Salvy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: br.com.salvy/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/salvy-com-br/index.md) ## Sources - [Ora score page for salvy.com.br](https://ora.ai/score/salvy.com.br?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=salvy), read 4 November 2026 - [Salvy website](https://salvy.com.br), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SanctionsKit MCP server | Agent MCP Directory" description: "SanctionsKit has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sanctionskit-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SanctionsKit MCP server | Agent MCP Directory > SanctionsKit has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sanctionskit-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SanctionsKit: MCP server, CLI and agent surfaces Yes: SanctionsKit runs a public MCP server at www.sanctionskit.com that listed 9 tools to a client with no credentials on 4 November 2026. Examples: search\_docs, get\_doc, get\_api\_schema. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | SanctionsKit (registry title: SanctionsKit developer MCP) | | --- | --- | | Domain | sanctionskit.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for sanctionskit.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.sanctionskit.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | sanctionskit 1.0.0 | | Capabilities | tools, resources, prompts | | Tools | 9 | | Resources | 116 | | Prompts | 1 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,237 ms over 1 attempt | ### Tools listed 9 tools - search\_docs - get\_doc - get\_api\_schema - validate\_screening\_request - list\_sources - run\_sandbox\_screening - get\_screening\_result - get\_usage - get\_profile ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:19Z https://www.sanctionskit.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1674 ms - 20:04:22Z https://www.sanctionskit.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1237 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.sanctionskit.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SanctionsKit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.sanctionskit.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sanctionskit-com/index.md) ## Sources - [SanctionsKit website](https://sanctionskit.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sanity MCP server | Agent MCP Directory" description: "Sanity: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sanity-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sanity MCP server | Agent MCP Directory > Sanity: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sanity-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sanity: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sanity at mcp.sanity.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sanity | | --- | --- | | Domain | sanity.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,733 on the list of 4 November 2026 | | Ora score | 72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sanity.io, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sanity.io | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 436 ms over 1 attempt | | Documentation | www.sanity.io | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:03Z https://mcp.sanity.io sent initialize result auth-required (HTTP 401) 371 ms - 20:01:39Z https://mcp.sanity.io sent initialize result auth-required (HTTP 401) 436 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.sanity.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.sanity.io | | Authorization server metadata | mcp.sanity.io | | Registration endpoint | https://mcp.sanity.io/register | ### The sign-in route, step by step 1. Request `https://mcp.sanity.io` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sanity.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sanity.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @sanity/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 8.27.0 | | Last publish | 30 October 2026 | | Command names | sanity | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sanity-io/index.md) ## Sources - [Sanity MCP documentation](https://www.sanity.io/docs/compute-and-ai/mcp-server), read 4 November 2026 - [Ora score page for sanity.io](https://ora.ai/score/sanity.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Sanity website](https://sanity.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SAP MCP server | Agent MCP Directory" description: "Does SAP have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/sap-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SAP MCP server | Agent MCP Directory > Does SAP have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/sap-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SAP: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SAP (sap.com), so the connector had nothing to connect to. Ora's cached score for sap.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SAP | | --- | --- | | Domain | sap.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,162 on the list of 4 November 2026 | | Ora score | 52, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sap.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SAP. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sap.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SAP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sap-com/index.md) ## Sources - [Ora score page for sap.com](https://ora.ai/score/sap.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/score) - [Where SAP was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SAP website](https://sap.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Say It Again MCP server | Agent MCP Directory" description: "Say It Again: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce." canonical: https://agentmcpdirectory.com/directory/sayitagain-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Say It Again MCP server | Agent MCP Directory > Say It Again: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: E-commerce. Source: https://agentmcpdirectory.com/directory/sayitagain-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Say It Again: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Say It Again at app.sayitagain.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Say It Again | | --- | --- | | Domain | sayitagain.ai | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for sayitagain.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.sayitagain.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,039 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:19Z https://app.sayitagain.ai/mcp sent initialize result auth-required (HTTP 401) 1225 ms - 20:04:22Z https://app.sayitagain.ai/mcp sent initialize result auth-required (HTTP 401) 1039 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Say It Again", resource_metadata="https://app.sayitagain.ai/.well-known/oauth-protected-resource", scope="mcp" | | Protected resource metadata | app.sayitagain.ai | | Authorization server metadata | app.sayitagain.ai | | Registration endpoint | https://app.sayitagain.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://app.sayitagain.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.sayitagain.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.sayitagain.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Say It Again. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.sayitagain/sayitagain | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sayitagain-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sayitagain), read 4 November 2026 - [Say It Again website](https://sayitagain.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sazabi MCP server | Agent MCP Directory" description: "Sazabi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sazabi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sazabi MCP server | Agent MCP Directory > Sazabi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sazabi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sazabi: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Sazabi; the connector's guess at mcp.sazabi.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sazabi (registry title: sazabi.com) | | --- | --- | | Domain | sazabi.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 60, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sazabi.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sazabi.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,087 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:20Z https://mcp.sazabi.com/mcp sent initialize result auth-required (HTTP 401) 2070 ms - 20:04:23Z https://mcp.sazabi.com/mcp sent initialize result auth-required (HTTP 401) 2087 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.sazabi.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.sazabi.com | | Authorization server metadata | api.platform.sazabi.com | | Registration endpoint | https://api.platform.sazabi.com/api/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.sazabi.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sazabi.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.platform.sazabi.com/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sazabi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sazabi-com/index.md) ## Sources - [Ora score page for sazabi.com](https://ora.ai/score/sazabi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where Sazabi was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sazabi website](https://sazabi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scaleway MCP server | Agent MCP Directory" description: "Does Scaleway have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scaleway-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scaleway MCP server | Agent MCP Directory > Does Scaleway have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/scaleway-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scaleway: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Scaleway (scaleway.com), so the connector had nothing to connect to. Ora's cached score for scaleway.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Scaleway | | --- | --- | | Domain | scaleway.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for scaleway.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Scaleway. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for scaleway.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Scaleway. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scaleway-com/index.md) ## Sources - [Ora score page for scaleway.com](https://ora.ai/score/scaleway.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where Scaleway was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Scaleway website](https://scaleway.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scalix Cloud MCP server | Agent MCP Directory" description: "Scalix Cloud has an open MCP server with 53 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scalix-world site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scalix Cloud MCP server | Agent MCP Directory > Scalix Cloud has an open MCP server with 53 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/scalix-world Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scalix Cloud: MCP server, CLI and agent surfaces Yes: Scalix Cloud runs a public MCP server at api.scalix.world that listed 53 tools to a client with no credentials on 4 November 2026. Examples: scalix\_db\_relationships, scalix\_db\_search\_columns, scalix\_db\_pii. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Scalix Cloud | | --- | --- | | Domain | scalix.world | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for scalix.world when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.scalix.world/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | scalix-cloud 1.5.0 | | Capabilities | resources, tools | | Tools | 53 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 559 ms over 1 attempt | ### Tools listed 53 tools; the first 40 names are recorded - scalix\_db\_relationships - scalix\_db\_search\_columns - scalix\_db\_pii - scalix\_db\_optimize - scalix\_db\_text\_to\_sql - scalix\_db\_query - scalix\_db\_schema - scalix\_db\_table - scalix\_db\_migrate - scalix\_storage\_list - scalix\_storage\_upload - scalix\_storage\_download - scalix\_storage\_create\_bucket - scalix\_storage\_delete\_object - scalix\_storage\_delete\_bucket - scalix\_fn\_list - scalix\_fn\_deploy - scalix\_fn\_invoke - scalix\_kv\_get - scalix\_kv\_set - scalix\_kv\_list - scalix\_ai\_infer - scalix\_ai\_models - scalix\_events\_publish - scalix\_events\_topics - scalix\_cron\_create - scalix\_sandbox\_run - scalix\_computer\_create - scalix\_computer\_set\_ssh\_keys - scalix\_computer\_list - scalix\_computer\_exec - scalix\_computer\_write\_file - scalix\_computer\_read\_file - scalix\_computer\_stop - scalix\_computer\_start - scalix\_computer\_delete - scalix\_crew\_list - scalix\_crew\_board\_read - scalix\_crew\_board\_post - scalix\_domain\_add ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:19Z https://api.scalix.world/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 857 ms - 20:04:22Z https://api.scalix.world/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 559 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.scalix.world/v1/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Scalix Cloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scalix-world/index.md) ## Sources - [Scalix Cloud website](https://scalix.world), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scalr MCP server | Agent MCP Directory" description: "Does Scalr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scalr-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scalr MCP server | Agent MCP Directory > Does Scalr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/scalr-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scalr: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Scalr (scalr.com), so the connector had nothing to connect to. Ora's cached score for scalr.com is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Scalr (registry title: scalr.com) | | --- | --- | | Domain | scalr.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for scalr.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Scalr. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for scalr.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Scalr. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scalr-com/index.md) ## Sources - [Ora score page for scalr.com](https://ora.ai/score/scalr.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Scalr was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Scalr website](https://scalr.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scalyr MCP server | Agent MCP Directory" description: "Does Scalyr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scalyr-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scalyr MCP server | Agent MCP Directory > Does Scalyr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/scalyr-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scalyr: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Scalyr (scalyr.com), so the connector had nothing to connect to. Ora's cached score for scalyr.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Scalyr (registry title: scalyr.com) | | --- | --- | | Domain | scalyr.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for scalyr.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Scalyr. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for scalyr.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Scalyr. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scalyr-com/index.md) ## Sources - [Ora score page for scalyr.com](https://ora.ai/score/scalyr.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Scalyr was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scape MCP server | Agent MCP Directory" description: "Does Scape have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scape-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scape MCP server | Agent MCP Directory > Does Scape have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/scape-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scape: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Scape (scape.app), so the connector had nothing to connect to. Ora's cached score for scape.app is 36, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Scape (registry title: scape.app) | | --- | --- | | Domain | scape.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 36, grade D; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for scape.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Scape. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for scape.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Scape. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scape-app/index.md) ## Sources - [Ora score page for scape.app](https://ora.ai/score/scape.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/leaderboard) - [Where Scape was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Scape website](https://scape.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scavio MCP server | Agent MCP Directory" description: "Scavio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scavio-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scavio MCP server | Agent MCP Directory > Scavio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/scavio-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scavio: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Scavio at mcp.scavio.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Scavio | | --- | --- | | Domain | scavio.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for scavio.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.scavio.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 463 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:20Z https://mcp.scavio.dev/mcp sent initialize result auth-required (HTTP 401) 731 ms - 20:04:22Z https://mcp.scavio.dev/mcp sent initialize result auth-required (HTTP 401) 463 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.scavio.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.scavio.dev | | Authorization server metadata | mcp.scavio.dev | | Registration endpoint | https://mcp.scavio.dev/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.scavio.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.scavio.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.scavio.dev/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Scavio. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scavio-dev/index.md) ## Sources - [Where Scavio was found](https://github.com/mcp/scavio-ai/scavio-mcp), read 4 November 2026 - [Scavio website](https://scavio.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scento MCP server | Agent MCP Directory" description: "Scento has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scento-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scento MCP server | Agent MCP Directory > Scento has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/scento-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scento: MCP server, CLI and agent surfaces Yes: Scento runs a public MCP server at www.scento.com that listed 12 tools to a client with no credentials on 4 November 2026. Examples: perfume-search, perfume-portrait, scent-neighbours. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for scento.com is 82, grade B, read on 5 November 2026. ## Fact sheet | Company | Scento (registry title: Scento Perfume API (MCP server)) | | --- | --- | | Domain | scento.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 82, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for scento.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.scento.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | scento-perfume-api 1.0.0 | | Capabilities | tools, resources, prompts, logging | | Tools | 12 | | Resources | 2 | | Prompts | 2 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,004 ms over 1 attempt | ### Tools listed 12 tools - perfume-search - perfume-portrait - scent-neighbours - perfume-contrast - note-portrait - material-match - house-portrait - family-map - occasion-edit - wardrobe-composer - perfumery-lexicon - journal-search ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:20Z https://www.scento.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1227 ms - 20:04:23Z https://www.scento.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1004 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.scento.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Scento. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.scento/perfume-api | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scento-com/index.md) ## Sources - [Ora score page for scento.com](https://ora.ai/score/scento.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=scento), read 4 November 2026 - [Scento website](https://scento.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scholar Sidekick MCP server | Agent MCP Directory" description: "Scholar Sidekick has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scholar-sidekick-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scholar Sidekick MCP server | Agent MCP Directory > Scholar Sidekick has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/scholar-sidekick-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scholar Sidekick: MCP server, CLI and agent surfaces Yes: Scholar Sidekick runs a public MCP server at scholar-sidekick.com that listed 7 tools to a client with no credentials on 4 November 2026. Examples: verifyCitation, auditBibliography, checkRetraction. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for scholar-sidekick.com is 98, grade A+, read on 5 November 2026. ## Fact sheet | Company | Scholar Sidekick | | --- | --- | | Domain | scholar-sidekick.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 98, grade A+; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for scholar-sidekick.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://scholar-sidekick.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | scholar-sidekick 0.8.13 | | Capabilities | tools, prompts, resources | | Tools | 7 | | Resources | 4 | | Prompts | 7 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,947 ms over 1 attempt | ### Tools listed 7 tools - verifyCitation - auditBibliography - checkRetraction - checkOpenAccess - resolveIdentifier - formatCitation - exportCitation ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:22Z https://scholar-sidekick.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2796 ms - 20:04:24Z https://scholar-sidekick.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1947 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://scholar-sidekick.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Scholar Sidekick. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: scholar-sidekick.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scholar-sidekick-com/index.md) ## Sources - [Ora score page for scholar-sidekick.com](https://ora.ai/score/scholar-sidekick.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/score) - [Where Scholar Sidekick was found](https://github.com/mcp/mlava/scholar-sidekick-mcp), read 4 November 2026 - [Scholar Sidekick website](https://scholar-sidekick.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scorecard MCP server | Agent MCP Directory" description: "Scorecard: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/scorecard-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scorecard MCP server | Agent MCP Directory > Scorecard: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/scorecard-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scorecard: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Scorecard at scorecard-mcp.dare-d5b.workers.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Scorecard | | --- | --- | | Domain | scorecard.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for scorecard.io when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://scorecard-mcp.dare-d5b.workers.dev/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 147 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:20Z https://scorecard-mcp.dare-d5b.workers.dev/sse sent initialize result auth-required (HTTP 401) 585 ms - 20:04:22Z https://scorecard-mcp.dare-d5b.workers.dev/sse sent initialize result auth-required (HTTP 401) 147 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token" | | Authorization server metadata | scorecard-mcp.dare-d5b.workers.dev | | Registration endpoint | https://scorecard-mcp.dare-d5b.workers.dev/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://scorecard-mcp.dare-d5b.workers.dev/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://scorecard-mcp.dare-d5b.workers.dev/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Scorecard. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scorecard-io/index.md) ## Sources - [Where Scorecard was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Scorecard website](https://scorecard.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scoutapm MCP server | Agent MCP Directory" description: "Scoutapm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/scoutapm-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scoutapm MCP server | Agent MCP Directory > Scoutapm: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/scoutapm-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scoutapm: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Scoutapm at scoutapm.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Scoutapm (registry title: Scout Monitoring) | | --- | --- | | Domain | scoutapm.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 67, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for scoutapm.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://scoutapm.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,428 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:21Z https://scoutapm.com/mcp sent initialize result auth-required (HTTP 401) 1539 ms - 20:04:24Z https://scoutapm.com/mcp sent initialize result auth-required (HTTP 401) 1428 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Scout Monitoring", authorization_uri="https://scoutapm.com/oauth/authorize", resource="https://scoutapm.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | scoutapm.com | | Authorization server metadata | scoutapm.com | | Registration endpoint | https://scoutapm.com/oauth/register | ### The sign-in route, step by step 1. Request `https://scoutapm.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://scoutapm.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://scoutapm.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Scoutapm. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: scoutapm.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.scoutapm/scout-monitoring | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scoutapm-com/index.md) ## Sources - [Ora score page for scoutapm.com](https://ora.ai/score/scoutapm.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where Scoutapm was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.scoutapm%2Fscout-monitoring), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=scoutapm), read 4 November 2026 - [Scoutapm website](https://scoutapm.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ScrapingBee MCP server | Agent MCP Directory" description: "ScrapingBee has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scrapingbee-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ScrapingBee MCP server | Agent MCP Directory > ScrapingBee has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/scrapingbee-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ScrapingBee: MCP server, CLI and agent surfaces Yes: ScrapingBee runs a public MCP server at mcp.scrapingbee.com that listed 18 tools to a client with no credentials on 4 November 2026. Examples: get\_amazon\_search\_results, get\_amazon\_product\_details, get\_amazon\_pricing. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for scrapingbee.com is 61, grade C, read on 5 November 2026. ## Fact sheet | Company | ScrapingBee | | --- | --- | | Domain | scrapingbee.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 61, grade C; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for scrapingbee.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.scrapingbee.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | ScrapingBee 2.2.1 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 18 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,066 ms over 1 attempt | ### Tools listed 18 tools - get\_amazon\_search\_results - get\_amazon\_product\_details - get\_amazon\_pricing - ask\_chatgpt - fast\_search - ask\_gemini - get\_google\_search\_results - get\_page\_text - get\_page\_html - extract\_page\_data - get\_screenshot - get\_file - get\_scrapingbee\_usage - get\_walmart\_search\_results - get\_walmart\_product\_details - get\_youtube\_search\_results - get\_youtube\_video\_metadata - get\_youtube\_video\_subtitles ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:21Z https://mcp.scrapingbee.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1301 ms - 20:04:23Z https://mcp.scrapingbee.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1066 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.scrapingbee.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ScrapingBee. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.scrapingbee/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scrapingbee-com/index.md) ## Sources - [Ora score page for scrapingbee.com](https://ora.ai/score/scrapingbee.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=scrapingbee), read 4 November 2026 - [ScrapingBee website](https://scrapingbee.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Screenforge MCP server | Agent MCP Directory" description: "Screenforge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/screenforge-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Screenforge MCP server | Agent MCP Directory > Screenforge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/screenforge-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Screenforge: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Screenforge at api.director.screenforge.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Screenforge (registry title: Director) | | --- | --- | | Domain | screenforge.co | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for screenforge.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.director.screenforge.co/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 747 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:21Z https://api.director.screenforge.co/api/mcp sent initialize result auth-required (HTTP 401) 936 ms - 20:04:23Z https://api.director.screenforge.co/api/mcp sent initialize result auth-required (HTTP 401) 747 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.director.screenforge.co/.well-known/oauth-protected-resource" | | Protected resource metadata | api.director.screenforge.co | | Authorization server metadata | api.director.screenforge.co | | Registration endpoint | https://api.director.screenforge.co/api/oauth/register | ### The sign-in route, step by step 1. Request `https://api.director.screenforge.co/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.director.screenforge.co/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.director.screenforge.co/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Screenforge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.screenforge/director | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/screenforge-co/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=screenforge), read 4 November 2026 - [Screenforge website](https://screenforge.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ScreensDesign MCP server | Agent MCP Directory" description: "ScreensDesign: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/screensdesign-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ScreensDesign MCP server | Agent MCP Directory > ScreensDesign: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/screensdesign-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ScreensDesign: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ScreensDesign at api.screensdesign.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ScreensDesign | | --- | --- | | Domain | screensdesign.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 35, grade D; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for screensdesign.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.screensdesign.com/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 464 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:21Z https://api.screensdesign.com/v1/mcp sent initialize result auth-required (HTTP 401) 668 ms - 20:04:23Z https://api.screensdesign.com/v1/mcp sent initialize result auth-required (HTTP 401) 464 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="ScreensDesign MCP", resource_metadata="https://api.screensdesign.com/v1/.well-known/oauth-protected-resource" | | Protected resource metadata | api.screensdesign.com | | Authorization server metadata | api.screensdesign.com | | Registration endpoint | https://api.screensdesign.com/v1/oauth/register | ### The sign-in route, step by step 1. Request `https://api.screensdesign.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.screensdesign.com/v1/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.screensdesign.com/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ScreensDesign. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.screensdesign/screensdesign | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/screensdesign-com/index.md) ## Sources - [Ora score page for screensdesign.com](https://ora.ai/score/screensdesign.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=screensdesign), read 4 November 2026 - [ScreensDesign website](https://screensdesign.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Screenshot Scout MCP server | Agent MCP Directory" description: "Screenshot Scout: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/screenshotscout-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Screenshot Scout MCP server | Agent MCP Directory > Screenshot Scout: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/screenshotscout-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Screenshot Scout: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Screenshot Scout at mcp.screenshotscout.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Screenshot Scout | | --- | --- | | Domain | screenshotscout.com | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for screenshotscout.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.screenshotscout.com/mcp/api-key | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 159 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:21Z https://mcp.screenshotscout.com/mcp/api-key sent initialize result auth-required-no-oauth (HTTP 401) 586 ms - 20:04:23Z https://mcp.screenshotscout.com/mcp/api-key sent initialize result auth-required-no-oauth (HTTP 401) 159 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | Bearer realm="Screenshot Scout" | ### The sign-in route, step by step 1. Request `https://mcp.screenshotscout.com/mcp/api-key` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Screenshot Scout. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.screenshotscout/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/screenshotscout-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=screenshotscout), read 4 November 2026 - [Screenshot Scout website](https://screenshotscout.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ScreenVerb MCP server | Agent MCP Directory" description: "ScreenVerb: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/screenverb-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ScreenVerb MCP server | Agent MCP Directory > ScreenVerb: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/screenverb-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ScreenVerb: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ScreenVerb at mcp.screenverb.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ScreenVerb | | --- | --- | | Domain | screenverb.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for screenverb.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.screenverb.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 599 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:22Z https://mcp.screenverb.com/mcp sent initialize result auth-required (HTTP 401) 721 ms - 20:04:24Z https://mcp.screenverb.com/mcp sent initialize result auth-required (HTTP 401) 599 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.screenverb.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.screenverb.com | | Authorization server metadata | mcp.screenverb.com | | Registration endpoint | https://mcp.screenverb.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.screenverb.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.screenverb.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.screenverb.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ScreenVerb. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.screenverb/screenverb | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/screenverb-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=screenverb), read 4 November 2026 - [ScreenVerb website](https://screenverb.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Scripe MCP server | Agent MCP Directory" description: "Scripe: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/scripe-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Scripe MCP server | Agent MCP Directory > Scripe: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/scripe-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scripe: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Scripe at mcp.scripe.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Scripe | | --- | --- | | Domain | scripe.io | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 69, grade C; Ora scanned the domain on 28 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for scripe.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.scripe.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 715 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:22Z https://mcp.scripe.io/mcp sent initialize result auth-required (HTTP 401) 1082 ms - 20:04:24Z https://mcp.scripe.io/mcp sent initialize result auth-required (HTTP 401) 715 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No Authorization header. This endpoint accepts OAuth bearer tokens only (API keys work on the REST API, not on MCP). Authorize through the authorization server advertised at the resource_metadata URL in this challenge.", resource_metadata="https://mcp.scripe.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.scripe.io | | Authorization server metadata | scripe.io | | Registration endpoint | https://scripe.io/api/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.scripe.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.scripe.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://scripe.io/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Scripe. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/scripe-io/index.md) ## Sources - [Ora score page for scripe.io](https://ora.ai/score/scripe.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 August 2026, read from GET /api/score) - [Scripe website](https://scripe.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Seam MCP server | Agent MCP Directory" description: "Seam has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/seam-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Seam MCP server | Agent MCP Directory > Seam has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/seam-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Seam: MCP server, CLI and agent surfaces Yes: Seam runs a public MCP server at mcp.seam.co, found by guessing the subdomain, and it listed 7 tools to a client with no credentials on 4 November 2026. Examples: search\_docs, get\_docs, search\_api. It speaks streamable-http, protocol 2025-11-25. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | Seam (registry title: seam.co) | | --- | --- | | Domain | seam.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 53, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for seam.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.seam.co/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | seam-docs-mcp 0.1.0 | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,221 ms over 1 attempt | ### Tools listed 7 tools - search\_docs - get\_docs - search\_api - get\_apis - search\_prompts - get\_prompt - get\_prompt\_context ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:23Z https://mcp.seam.co/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1270 ms - 20:04:25Z https://mcp.seam.co/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1221 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.seam.co/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Seam. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/seam-co/index.md) ## Sources - [Ora score page for seam.co](https://ora.ai/score/seam.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/score) - [Where Seam was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Seam website](https://seam.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SearchAPI MCP server | Agent MCP Directory" description: "SearchAPI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/searchapi-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SearchAPI MCP server | Agent MCP Directory > SearchAPI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/searchapi-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # SearchAPI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SearchAPI at www.searchapi.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SearchAPI | | --- | --- | | Domain | searchapi.io | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 39, grade D; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for searchapi.io, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.searchapi.io/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 553 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:22Z https://www.searchapi.io/mcp sent initialize result auth-required (HTTP 401) 788 ms - 20:04:24Z https://www.searchapi.io/mcp sent initialize result auth-required (HTTP 401) 553 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.searchapi.io/.well-known/oauth-protected-resource/mcp", scope="mcp" | | Protected resource metadata | www.searchapi.io | | Authorization server metadata | www.searchapi.io | | Registration endpoint | https://www.searchapi.io/oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://www.searchapi.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.searchapi.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://www.searchapi.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SearchAPI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/searchapi-io/index.md) ## Sources - [Ora score page for searchapi.io](https://ora.ai/score/searchapi.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/score) - [Where SearchAPI was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [SearchAPI website](https://searchapi.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SearchConsole.ai MCP server | Agent MCP Directory" description: "SearchConsole.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/searchconsole-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SearchConsole.ai MCP server | Agent MCP Directory > SearchConsole.ai: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/searchconsole-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # SearchConsole.ai: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SearchConsole.ai at searchconsole.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SearchConsole.ai | | --- | --- | | Domain | searchconsole.ai | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for searchconsole.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://searchconsole.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 925 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:23Z https://searchconsole.ai/mcp sent initialize result auth-required (HTTP 401) 995 ms - 20:04:25Z https://searchconsole.ai/mcp sent initialize result auth-required (HTTP 401) 925 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Google Search Console MCP", resource_metadata="https://searchconsole.ai/.well-known/oauth-protected-resource", scope="mcp:tools" | | Protected resource metadata | searchconsole.ai | | Authorization server metadata | searchconsole.ai | | Registration endpoint | https://searchconsole.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://searchconsole.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://searchconsole.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://searchconsole.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SearchConsole.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.searchconsole/searchconsole-ai | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/searchconsole-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=searchconsole), read 4 November 2026 - [SearchConsole.ai website](https://searchconsole.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Searcherries MCP server | Agent MCP Directory" description: "Searcherries: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/searcherries-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Searcherries MCP server | Agent MCP Directory > Searcherries: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/searcherries-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Searcherries: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Searcherries at app.searcherries.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Searcherries (registry title: Searcherries: AI Visibility & SEO) | | --- | --- | | Domain | searcherries.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for searcherries.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.searcherries.com/mcp/searcherries | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 518 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:23Z https://app.searcherries.com/mcp/searcherries sent initialize result auth-required (HTTP 401) 626 ms - 20:04:25Z https://app.searcherries.com/mcp/searcherries sent initialize result auth-required (HTTP 401) 518 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://app.searcherries.com/.well-known/oauth-protected-resource/mcp/searcherries" | | Protected resource metadata | app.searcherries.com | | Authorization server metadata | app.searcherries.com | | Registration endpoint | https://app.searcherries.com/oauth/register | ### The sign-in route, step by step 1. Request `https://app.searcherries.com/mcp/searcherries` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://app.searcherries.com/.well-known/oauth-protected-resource/mcp/searcherries` to find the authorization server. 3. Register a client at the registration endpoint `https://app.searcherries.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Searcherries. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.searcherries/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/searcherries-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=searcherries), read 4 November 2026 - [Searcherries website](https://searcherries.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Search Fragments MCP server | Agent MCP Directory" description: "Search Fragments has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/searchfragments-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Search Fragments MCP server | Agent MCP Directory > Search Fragments has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/searchfragments-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Search Fragments: MCP server, CLI and agent surfaces Yes: Search Fragments runs a public MCP server at searchfragments.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: resolve\_fragment, submit\_resolution\_feedback, verify\_claim. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Search Fragments | | --- | --- | | Domain | searchfragments.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for searchfragments.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://searchfragments.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | search-fragments-mcp 0.2.6 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 866 ms over 1 attempt | ### Tools listed 3 tools - resolve\_fragment - submit\_resolution\_feedback - verify\_claim ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:23Z https://searchfragments.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1052 ms - 20:04:25Z https://searchfragments.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 866 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://searchfragments.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Search Fragments. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.searchfragments/search-fragments | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/searchfragments-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=searchfragments), read 4 November 2026 - [Search Fragments website](https://searchfragments.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Seller Profit Doctor MCP server | Agent MCP Directory" description: "Seller Profit Doctor has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sellerprofitdoctor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Seller Profit Doctor MCP server | Agent MCP Directory > Seller Profit Doctor has an open MCP server with 16 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sellerprofitdoctor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Seller Profit Doctor: MCP server, CLI and agent surfaces Yes: Seller Profit Doctor runs a public MCP server at sellerprofitdoctor.com that listed 16 tools to a client with no credentials on 4 November 2026. Examples: sellerprofit\_checkup, sellerprofit\_etsy\_fees, sellerprofit\_etsy\_profit. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Seller Profit Doctor | | --- | --- | | Domain | sellerprofitdoctor.com | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for sellerprofitdoctor.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://sellerprofitdoctor.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | sellerprofitdoctor-free-tools 1.5.0 | | Capabilities | tools | | Tools | 16 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,230 ms over 1 attempt | ### Tools listed 16 tools - sellerprofit\_checkup - sellerprofit\_etsy\_fees - sellerprofit\_etsy\_profit - sellerprofit\_offsite\_ads - sellerprofit\_shipping\_gap - sellerprofit\_ads\_breakeven - sellerprofit\_price\_for\_margin - sellerprofit\_sale\_breakeven - sellerprofit\_compare\_fees - sellerprofit\_ads\_roas\_breakeven - sellerprofit\_box\_billing - sellerprofit\_shopify\_plan\_fit - sellerprofit\_shopify\_order\_fees - sellerprofit\_amazon\_fees - sellerprofit\_amazon\_ads\_breakeven - sellerprofit\_rates ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:24Z https://sellerprofitdoctor.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1423 ms - 20:04:26Z https://sellerprofitdoctor.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1230 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://sellerprofitdoctor.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Seller Profit Doctor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.sellerprofitdoctor/free-tools | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sellerprofitdoctor-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sellerprofitdoctor), read 4 November 2026 - [Seller Profit Doctor website](https://sellerprofitdoctor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sellfy MCP server | Agent MCP Directory" description: "Sellfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sellfy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sellfy MCP server | Agent MCP Directory > Sellfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sellfy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sellfy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sellfy at api.sellfy.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sellfy (registry title: Sellfy MCP Server) | | --- | --- | | Domain | sellfy.com | | Category | Commerce Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sellfy.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.sellfy.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,435 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:25Z https://api.sellfy.com/mcp sent initialize result auth-required (HTTP 401) 2251 ms - 20:04:26Z https://api.sellfy.com/mcp sent initialize result auth-required (HTTP 401) 1435 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.sellfy.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.sellfy.com | | Authorization server metadata | app.sellfy.com | | Registration endpoint | https://app.sellfy.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.sellfy.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.sellfy.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.sellfy.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sellfy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.sellfy/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sellfy-com/index.md) ## Sources - [Ora score page for sellfy.com](https://ora.ai/score/sellfy.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/leaderboard) - [Where Sellfy was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.sellfy%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sellfy), read 4 November 2026 - [Sellfy website](https://sellfy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Semaphore MCP server | Agent MCP Directory" description: "Does Semaphore have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/semaphoreci-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Semaphore MCP server | Agent MCP Directory > Does Semaphore have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/semaphoreci-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Semaphore: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Semaphore (semaphoreci.com), so the connector had nothing to connect to. Ora's cached score for semaphoreci.com is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Semaphore (registry title: semaphoreci.com) | | --- | --- | | Domain | semaphoreci.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for semaphoreci.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Semaphore. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for semaphoreci.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Semaphore. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: semaphoreci.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/semaphoreci-com/index.md) ## Sources - [Ora score page for semaphoreci.com](https://ora.ai/score/semaphoreci.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where Semaphore was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Semaphore website](https://semaphoreci.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Semgrep MCP server | Agent MCP Directory" description: "Semgrep: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/semgrep-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Semgrep MCP server | Agent MCP Directory > Semgrep: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/semgrep-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Semgrep: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Semgrep at mcp.semgrep.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Semgrep | | --- | --- | | Domain | semgrep.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 60, grade C; Ora scanned the domain on 5 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for semgrep.dev, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.semgrep.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,575 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:59:24Z https://mcp.semgrep.ai/sse sent initialize result no-answer (HTTP 404) 1236 ms - 20:04:26Z https://mcp.semgrep.ai/sse sent initialize result no-answer (HTTP 404) 1246 ms - 20:04:28Z https://mcp.semgrep.ai/mcp sent initialize result auth-required (HTTP 401) 1575 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.semgrep.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.semgrep.ai | | Authorization server metadata | login.semgrep.dev | | Registration endpoint | https://login.semgrep.dev/oauth2/register | | Client ID metadata documents | supported | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.semgrep.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.semgrep.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://login.semgrep.dev/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Semgrep. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: semgrep.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/semgrep-dev/index.md) ## Sources - [Ora score page for semgrep.dev](https://ora.ai/score/semgrep.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 October 2026, read from GET /api/leaderboard) - [Where Semgrep was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Semgrep website](https://semgrep.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sendmux MCP server | Agent MCP Directory" description: "Sendmux: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/sendmux-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sendmux MCP server | Agent MCP Directory > Sendmux: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/sendmux-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sendmux: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sendmux at mcp.sendmux.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sendmux (registry title: Email Inbox API + Sending by Sendmux) | | --- | --- | | Domain | sendmux.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 93, grade A; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sendmux.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sendmux.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 618 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:24Z https://mcp.sendmux.ai/mcp sent initialize result auth-required (HTTP 401) 713 ms - 20:04:26Z https://mcp.sendmux.ai/mcp sent initialize result auth-required (HTTP 401) 618 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.sendmux.ai/.well-known/oauth-protected-resource/mcp", scope="analytics.read billing.read domain.create domain.read domain.verify email.send logs.read mailbox.admin.create mailbox.admin.manage mailbox.admin.read mailbox.read mailbox.settings.update webhook.create webhook.manage webhook.read" | | Protected resource metadata | mcp.sendmux.ai | | Authorization server metadata | app.sendmux.ai | | Registration endpoint | https://app.sendmux.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.sendmux.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sendmux.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.sendmux.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sendmux. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sendmux-ai/index.md) ## Sources - [Ora score page for sendmux.ai](https://ora.ai/score/sendmux.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/score) - [Sendmux website](https://sendmux.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SendPulse MCP server | Agent MCP Directory" description: "SendPulse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/sendpulse-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SendPulse MCP server | Agent MCP Directory > SendPulse: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/sendpulse-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SendPulse: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SendPulse at mcp.sendpulse.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SendPulse | | --- | --- | | Domain | sendpulse.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 47, grade D; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sendpulse.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sendpulse.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 517 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:24Z https://mcp.sendpulse.com/mcp sent initialize result auth-required (HTTP 401) 663 ms - 20:04:26Z https://mcp.sendpulse.com/mcp sent initialize result auth-required (HTTP 401) 517 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.sendpulse.com/.well-known/oauth-protected-resource/mcp", scope="rest" | | Protected resource metadata | mcp.sendpulse.com | | Authorization server metadata | mcp.sendpulse.com | | Registration endpoint | https://mcp.sendpulse.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.sendpulse.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sendpulse.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sendpulse.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SendPulse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.sendpulse.mcp/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sendpulse-com/index.md) ## Sources - [Ora score page for sendpulse.com](https://ora.ai/score/sendpulse.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/leaderboard) - [Where SendPulse was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.sendpulse.mcp%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sendpulse), read 4 November 2026 - [SendPulse website](https://sendpulse.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SentinelX MCP server | Agent MCP Directory" description: "SentinelX: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/sentinelx-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SentinelX MCP server | Agent MCP Directory > SentinelX: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/sentinelx-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # SentinelX: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SentinelX at mcp.sentinelx.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SentinelX (registry title: SentinelX MCP) | | --- | --- | | Domain | sentinelx.app | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for sentinelx.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sentinelx.app/mcp/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,112 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:25Z https://mcp.sentinelx.app/mcp/mcp sent initialize result auth-required (HTTP 401) 1441 ms - 20:04:26Z https://mcp.sentinelx.app/mcp/mcp sent initialize result auth-required (HTTP 401) 1112 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="sentinelx-cloud-hub", resource_metadata="https://mcp.sentinelx.app/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.sentinelx.app | | Authorization server metadata | keycloak.pensa.ar | | Registration endpoint | https://keycloak.pensa.ar/realms/mcp/clients-registrations/openid-connect | ### The sign-in route, step by step 1. Request `https://mcp.sentinelx.app/mcp/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sentinelx.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://keycloak.pensa.ar/realms/mcp/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SentinelX. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.sentinelx/sentinelx | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sentinelx-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sentinelx), read 4 November 2026 - [SentinelX website](https://sentinelx.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sentry (sentry.dev) MCP server | Agent MCP Directory" description: "Sentry (sentry.dev): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/sentry-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sentry (sentry.dev) MCP server | Agent MCP Directory > Sentry (sentry.dev): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/sentry-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sentry: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sentry at mcp.sentry.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sentry (registry title: Getsentry Sentry) | | --- | --- | | Domain | sentry.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 65, grade C; Ora scanned the domain on 1 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sentry.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sentry.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 109 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:24Z https://mcp.sentry.dev/mcp sent initialize result auth-required (HTTP 401) 95 ms - 20:04:26Z https://mcp.sentry.dev/mcp sent initialize result auth-required (HTTP 401) 109 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.sentry.dev | | Authorization server metadata | mcp.sentry.dev | | Registration endpoint | https://mcp.sentry.dev/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.sentry.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sentry.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sentry. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sentry-dev/index.md) ## Sources - [Ora score page for sentry.dev](https://ora.ai/score/sentry.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 September 2026, read from GET /api/score) - [Sentry website](https://sentry.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sentry (sentry.io) MCP server | Agent MCP Directory" description: "Sentry (sentry.io): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/sentry-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sentry (sentry.io) MCP server | Agent MCP Directory > Sentry (sentry.io): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/sentry-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sentry: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sentry at mcp.sentry.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sentry | | --- | --- | | Domain | sentry.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 102 on the list of 4 November 2026 | | Ora score | 79, grade B; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sentry.io, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sentry.dev/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 246 ms over 1 attempt | | Documentation | docs.sentry.io | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:51Z https://mcp.sentry.dev/mcp sent initialize result auth-required (HTTP 401) 117 ms - 20:01:26Z https://mcp.sentry.dev/mcp sent initialize result auth-required (HTTP 401) 246 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.sentry.dev | | Authorization server metadata | mcp.sentry.dev | | Registration endpoint | https://mcp.sentry.dev/oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.sentry.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sentry.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @sentry/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 3.8.2 | | Last publish | 22 October 2026 | | Command names | sentry-cli | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: sentry.io/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: sentry.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sentry-io/index.md) ## Sources - [Sentry MCP documentation](https://docs.sentry.io/product/sentry-mcp/), read 4 November 2026 - [Ora score page for sentry.io](https://ora.ai/score/sentry.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/score) - [Sentry website](https://sentry.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SEOmatic MCP server | Agent MCP Directory" description: "SEOmatic has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/seomatic-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SEOmatic MCP server | Agent MCP Directory > SEOmatic has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/seomatic-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # SEOmatic: MCP server, CLI and agent surfaces Yes: SEOmatic runs a public MCP server at app.seomatic.ai that listed 2 tools to a client with no credentials on 4 November 2026. Examples: check\_site, connect\_seomatic. It speaks streamable-http, protocol 2026-07-28. Ora's cached score for seomatic.ai is 35, grade D, read on 5 November 2026. ## Fact sheet | Company | SEOmatic | | --- | --- | | Domain | seomatic.ai | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 35, grade D; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for seomatic.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://app.seomatic.ai/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | seomatic 1.0.0 | | Capabilities | tools, prompts, resources | | Tools | 2 | | Resources | 5 | | Prompts | 5 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,251 ms over 1 attempt | ### Tools listed 2 tools - check\_site - connect\_seomatic ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:26Z https://app.seomatic.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1474 ms - 20:04:27Z https://app.seomatic.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1251 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://app.seomatic.ai/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SEOmatic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.seomatic/seomatic | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/seomatic-ai/index.md) ## Sources - [Ora score page for seomatic.ai](https://ora.ai/score/seomatic.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=seomatic), read 4 November 2026 - [SEOmatic website](https://seomatic.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sequencer MCP server | Agent MCP Directory" description: "Sequencer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/sequencer-media site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sequencer MCP server | Agent MCP Directory > Sequencer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/sequencer-media Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sequencer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sequencer at mcp.sequencer.media answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sequencer | | --- | --- | | Domain | sequencer.media | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for sequencer.media when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sequencer.media/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 795 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:26Z https://mcp.sequencer.media/ sent initialize result auth-required (HTTP 401) 1475 ms - 20:04:27Z https://mcp.sequencer.media/ sent initialize result auth-required (HTTP 401) 795 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="sequencer-mcp", resource_metadata="https://mcp.sequencer.media/.well-known/oauth-protected-resource", scope="openid email sequencer.production.manage" | | Protected resource metadata | mcp.sequencer.media | | Authorization server metadata | mcp.sequencer.media | | Registration endpoint | https://mcp.sequencer.media/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.sequencer.media/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sequencer.media/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sequencer.media/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sequencer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sequencer-media/index.md) ## Sources - [Sequencer website](https://sequencer.media), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SerpApi MCP server | Agent MCP Directory" description: "SerpApi has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/serpapi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SerpApi MCP server | Agent MCP Directory > SerpApi has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/serpapi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SerpApi: MCP server, CLI and agent surfaces Yes: SerpApi runs a public MCP server at mcp.serpapi.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: search\_dashboard, search\_table, extract. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for serpapi.com is 59, grade C, read on 5 November 2026. ## Fact sheet | Company | SerpApi | | --- | --- | | Domain | serpapi.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 59, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for serpapi.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.serpapi.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | SerpApi MCP Server 2.2.0 | | Capabilities | logging, prompts, resources, tools, completions | | Tools | 4 | | Resources | 3 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,413 ms over 1 attempt | ### Tools listed 4 tools - search\_dashboard - search\_table - extract - search ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:26Z https://mcp.serpapi.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1352 ms - 20:04:28Z https://mcp.serpapi.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1413 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.serpapi.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SerpApi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/serpapi-com/index.md) ## Sources - [Ora score page for serpapi.com](https://ora.ai/score/serpapi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where SerpApi was found](https://github.com/mcp/serpapi/serpapi-mcp), read 4 November 2026 - [SerpApi website](https://serpapi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Serpstat MCP server | Agent MCP Directory" description: "Serpstat: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/serpstat-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Serpstat MCP server | Agent MCP Directory > Serpstat: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/serpstat-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Serpstat: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Serpstat at mcp.serpstat.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Serpstat | | --- | --- | | Domain | serpstat.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 37, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for serpstat.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.serpstat.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 939 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:26Z https://mcp.serpstat.com/mcp sent initialize result auth-required (HTTP 401) 968 ms - 20:04:27Z https://mcp.serpstat.com/mcp sent initialize result auth-required (HTTP 401) 939 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.serpstat.com/.well-known/oauth-protected-resource/mcp",scope="mcp:connect openid offline offline_access",authorization_uri="https://mcp.serpstat.com/oauth2/auth" | | Protected resource metadata | mcp.serpstat.com | | Authorization server metadata | auth.serpstat.com | | Registration endpoint | https://auth.serpstat.com/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.serpstat.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.serpstat.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.serpstat.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Serpstat. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.serpstat/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/serpstat-com/index.md) ## Sources - [Ora score page for serpstat.com](https://ora.ai/score/serpstat.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Serpstat was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.serpstat%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=serpstat), read 4 November 2026 - [Serpstat website](https://serpstat.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Server4Agent MCP server | Agent MCP Directory" description: "Server4Agent: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/server4agent-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Server4Agent MCP server | Agent MCP Directory > Server4Agent: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/server4agent-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Server4Agent: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Server4Agent at mcp.server4agent.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Server4Agent | | --- | --- | | Domain | server4agent.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for server4agent.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.server4agent.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 874 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:27Z https://mcp.server4agent.com sent initialize result auth-required (HTTP 401) 1491 ms - 20:04:28Z https://mcp.server4agent.com sent initialize result auth-required (HTTP 401) 874 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.server4agent.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.server4agent.com | | Authorization server metadata | www.server4agent.com | | Registration endpoint | https://www.server4agent.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.server4agent.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.server4agent.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.server4agent.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Server4Agent. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.server4agent/server4agent | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/server4agent-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=server4agent), read 4 November 2026 - [Server4Agent website](https://server4agent.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Servicebricks MCP server | Agent MCP Directory" description: "Servicebricks has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/servicebricks-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Servicebricks MCP server | Agent MCP Directory > Servicebricks has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/servicebricks-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Servicebricks: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Servicebricks (servicebricks.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). ## Fact sheet | Company | Servicebricks (registry title: Holomodular Servicebricks) | | --- | --- | | Domain | servicebricks.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for servicebricks.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://servicebricks.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | HTTP status | 404 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,118 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 no content-type) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:27Z https://servicebricks.com/api/mcp sent initialize result no-answer (HTTP 404) 1312 ms - 20:04:28Z https://servicebricks.com/api/mcp sent initialize result no-answer (HTTP 404) 1118 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://servicebricks.com/api/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Servicebricks. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/servicebricks-com/index.md) ## Sources - [Where Servicebricks was found](https://github.com/mcp/holomodular/ServiceBricks), read 4 November 2026 - [Servicebricks website](https://servicebricks.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SF Tensor MCP server | Agent MCP Directory" description: "Does SF Tensor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sf-tensor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SF Tensor MCP server | Agent MCP Directory > Does SF Tensor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sf-tensor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SF Tensor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SF Tensor (sf-tensor.com), so the connector had nothing to connect to. Ora's cached score for sf-tensor.com is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SF Tensor (registry title: sf-tensor.com) | | --- | --- | | Domain | sf-tensor.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sf-tensor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SF Tensor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sf-tensor.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SF Tensor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sf-tensor-com/index.md) ## Sources - [Ora score page for sf-tensor.com](https://ora.ai/score/sf-tensor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where SF Tensor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SF Tensor website](https://sf-tensor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shaped MCP server | Agent MCP Directory" description: "Does Shaped have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/shaped-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shaped MCP server | Agent MCP Directory > Does Shaped have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/shaped-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shaped: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Shaped (shaped.ai), so the connector had nothing to connect to. Ora's cached score for shaped.ai is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Shaped (registry title: shaped.ai) | | --- | --- | | Domain | shaped.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for shaped.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Shaped. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for shaped.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Shaped. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shaped-ai/index.md) ## Sources - [Ora score page for shaped.ai](https://ora.ai/score/shaped.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where Shaped was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Shaped website](https://shaped.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ShapelessAI MCP server | Agent MCP Directory" description: "ShapelessAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media." canonical: https://agentmcpdirectory.com/directory/shapelessai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ShapelessAI MCP server | Agent MCP Directory > ShapelessAI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media. Source: https://agentmcpdirectory.com/directory/shapelessai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ShapelessAI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ShapelessAI at shapelessai.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ShapelessAI | | --- | --- | | Domain | shapelessai.com | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for shapelessai.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://shapelessai.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 725 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:27Z https://shapelessai.com/mcp sent initialize result auth-required (HTTP 401) 887 ms - 20:04:28Z https://shapelessai.com/mcp sent initialize result auth-required (HTTP 401) 725 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://shapelessai.com/.well-known/oauth-protected-resource/mcp", scope="read write publish offline_access" | | Protected resource metadata | shapelessai.com | | Authorization server metadata | shapelessai.com | | Registration endpoint | https://shapelessai.com/api/auth/mcp/register | ### The sign-in route, step by step 1. Request `https://shapelessai.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://shapelessai.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://shapelessai.com/api/auth/mcp/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ShapelessAI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: shapelessai.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.shapelessai/shapeless | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shapelessai-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=shapelessai), read 4 November 2026 - [ShapelessAI website](https://shapelessai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sherweb MCP server | Agent MCP Directory" description: "Sherweb: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sherweb-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sherweb MCP server | Agent MCP Directory > Sherweb: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sherweb-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sherweb: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sherweb at mcp.sherweb.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sherweb (registry title: Sherweb Platform MCP Server) | | --- | --- | | Domain | sherweb.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 53, grade C; Ora scanned the domain on 1 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sherweb.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sherweb.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,980 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:29Z https://mcp.sherweb.com sent initialize result auth-required (HTTP 401) 2421 ms - 20:04:30Z https://mcp.sherweb.com sent initialize result auth-required (HTTP 401) 1980 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="http://mcp.sherweb.com/.well-known/oauth-protected-resource/" | | Protected resource metadata | mcp.sherweb.com | | Authorization server metadata | cumulus.sherweb.com | ### The sign-in route, step by step 1. Request `https://mcp.sherweb.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://cumulus.sherweb.com/oidc/.well-known/openid-configuration`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sherweb. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.sherweb/platform | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sherweb-com/index.md) ## Sources - [Ora score page for sherweb.com](https://ora.ai/score/sherweb.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sherweb), read 4 November 2026 - [Sherweb website](https://sherweb.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shipbook MCP server | Agent MCP Directory" description: "Shipbook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/shipbook-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shipbook MCP server | Agent MCP Directory > Shipbook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/shipbook-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shipbook: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Shipbook at api.shipbook.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Shipbook | | --- | --- | | Domain | shipbook.io | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for shipbook.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.shipbook.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 323 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:27Z https://api.shipbook.io/mcp sent initialize result auth-required (HTTP 401) 550 ms - 20:04:28Z https://api.shipbook.io/mcp sent initialize result auth-required (HTTP 401) 323 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | api.shipbook.io | | Authorization server metadata | api.shipbook.io | | Registration endpoint | https://api.shipbook.io/oauth/register | ### The sign-in route, step by step 1. Request `https://api.shipbook.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.shipbook.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.shipbook.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Shipbook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shipbook-io/index.md) ## Sources - [Shipbook website](https://shipbook.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shippo MCP server | Agent MCP Directory" description: "Shippo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/shippo-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shippo MCP server | Agent MCP Directory > Shippo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/shippo-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shippo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Shippo at mcp.shippo.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Shippo | | --- | --- | | Domain | shippo.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for shippo.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.shippo.com | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,536 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:29Z https://mcp.shippo.com sent initialize result auth-required (HTTP 401) 2252 ms - 20:04:29Z https://mcp.shippo.com sent initialize result auth-required (HTTP 401) 1536 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | mcp.shippo.com | | Authorization server metadata | goshippo.com | | Registration endpoint | https://goshippo.com/oauth/clients | ### The sign-in route, step by step 1. Request `https://mcp.shippo.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.shippo.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://goshippo.com/oauth/clients` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Shippo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: shippo.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.shippo/shippo-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shippo-com/index.md) ## Sources - [Ora score page for shippo.com](https://ora.ai/score/shippo.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where Shippo was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.shippo%2Fshippo-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=shippo), read 4 November 2026 - [Shippo website](https://shippo.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ShipStatic MCP server | Agent MCP Directory" description: "ShipStatic has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/shipstatic-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ShipStatic MCP server | Agent MCP Directory > ShipStatic has an open MCP server with 15 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/shipstatic-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ShipStatic: MCP server, CLI and agent surfaces Yes: ShipStatic runs a public MCP server at mcp.shipstatic.com that listed 15 tools to a client with no credentials on 4 November 2026. Examples: deployments\_upload, deployments\_list, deployments\_get. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | ShipStatic | | --- | --- | | Domain | shipstatic.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for shipstatic.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.shipstatic.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | shipstatic 2.8.2 | | Capabilities | resources, tools | | Tools | 15 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 201 ms over 1 attempt | ### Tools listed 15 tools - deployments\_upload - deployments\_list - deployments\_get - deployments\_set - deployments\_delete - domains\_set - domains\_list - domains\_get - domains\_records - domains\_dns - domains\_share - domains\_validate - domains\_verify - domains\_delete - whoami ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:27Z https://mcp.shipstatic.com sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 343 ms - 20:04:28Z https://mcp.shipstatic.com sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 201 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.shipstatic.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ShipStatic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.shipstatic/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shipstatic-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=shipstatic), read 4 November 2026 - [ShipStatic website](https://shipstatic.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shogun MCP server | Agent MCP Directory" description: "Does Shogun have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/shogun-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shogun MCP server | Agent MCP Directory > Does Shogun have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/shogun-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shogun: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Shogun (shogun.com), so the connector had nothing to connect to. Ora's cached score for shogun.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Shogun (registry title: shogun.com) | | --- | --- | | Domain | shogun.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 22 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for shogun.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Shogun. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for shogun.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Shogun. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shogun-com/index.md) ## Sources - [Ora score page for shogun.com](https://ora.ai/score/shogun.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 August 2026, read from GET /api/leaderboard) - [Where Shogun was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Shogun website](https://shogun.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shopify MCP server | Agent MCP Directory" description: "Does Shopify have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/shopify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shopify MCP server | Agent MCP Directory > Does Shopify have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/shopify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shopify: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Shopify (shopify.com), so the connector had nothing to connect to. A CLI is on record: @shopify/cli on npm. Ora's cached score for shopify.com is 72, grade B, read on 5 November 2026. ## Fact sheet | Company | Shopify | | --- | --- | | Domain | shopify.com | | Category | Commerce Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 171 on the list of 4 November 2026 | | Ora score | 72, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for shopify.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Shopify. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for shopify.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | @shopify/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 5.0.1 | | Last publish | 4 November 2026 | | Command names | shopify | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shopify-com/index.md) ## Sources - [Ora score page for shopify.com](https://ora.ai/score/shopify.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Where Shopify was found](https://shopify.dev/docs/apps/build/storefront-mcp), read 4 November 2026 - [Shopify website](https://shopify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Short.io MCP server | Agent MCP Directory" description: "Short.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/short-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Short.io MCP server | Agent MCP Directory > Short.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/short-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Short.io: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Short.io at ai-assistant.short.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Short.io | | --- | --- | | Domain | short.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for short.io when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai-assistant.short.io/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,417 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:29Z https://ai-assistant.short.io/mcp sent initialize result auth-required (HTTP 401) 1314 ms - 20:04:30Z https://ai-assistant.short.io/mcp sent initialize result auth-required (HTTP 401) 1417 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Authorization server metadata | ai-assistant.short.io | | Registration endpoint | https://app.short.io/public/register | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://ai-assistant.short.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://app.short.io/public/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Short.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/short-io/index.md) ## Sources - [Where Short.io was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Short.io website](https://short.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shortcut MCP server | Agent MCP Directory" description: "Shortcut: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/shortcut-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shortcut MCP server | Agent MCP Directory > Shortcut: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/shortcut-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shortcut: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Shortcut; the connector's guess at mcp.shortcut.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Shortcut (registry title: shortcut.com) | | --- | --- | | Domain | shortcut.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 85, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for shortcut.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.shortcut.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,384 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:29Z https://mcp.shortcut.com/mcp sent initialize result auth-required (HTTP 401) 1539 ms - 20:04:30Z https://mcp.shortcut.com/mcp sent initialize result auth-required (HTTP 401) 1384 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.shortcut.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.shortcut.com | | Authorization server metadata | api.app.shortcut.com | | Registration endpoint | https://api.app.shortcut.com/oauth-client-registration-flow/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.shortcut.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.shortcut.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.app.shortcut.com/oauth-client-registration-flow/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Shortcut. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.shortcut.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shortcut-com/index.md) ## Sources - [Ora score page for shortcut.com](https://ora.ai/score/shortcut.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Shortcut was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Shortcut website](https://shortcut.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shortimize MCP server | Agent MCP Directory" description: "Shortimize has an open MCP server with 32 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/shortimize-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shortimize MCP server | Agent MCP Directory > Shortimize has an open MCP server with 32 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/shortimize-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shortimize: MCP server, CLI and agent surfaces Yes: Shortimize runs a public MCP server at api.shortimize.com that listed 32 tools to a client with no credentials on 4 November 2026. Examples: get\_all\_accounts, track\_account, stop\_tracking\_account. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Shortimize | | --- | --- | | Domain | shortimize.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for shortimize.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.shortimize.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Shortimize MCP Server 0.1.0 | | Capabilities | tools | | Tools | 32 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 179 ms over 1 attempt | ### Tools listed 32 tools - get\_all\_accounts - track\_account - stop\_tracking\_account - bulk\_track\_accounts - bulk\_stop\_tracking\_accounts - get\_all\_videos - track\_video - stop\_tracking\_video - bulk\_track\_videos - bulk\_stop\_tracking\_videos - authenticate - get\_organisation\_history - get\_video - get\_video\_history - get\_account\_history - get\_account - get\_videos\_linked\_to\_account - total\_videos - total\_accounts - refresh\_account\_data - refresh\_video\_data - get\_all\_collections - create\_collection - get\_collection - update\_collection - delete\_collection - get\_collection\_videos - add\_videos\_to\_collection - remove\_videos\_from\_collection - get\_collection\_accounts - add\_accounts\_to\_collection - remove\_accounts\_from\_collection ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:28Z https://api.shortimize.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 517 ms - 20:04:29Z https://api.shortimize.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 179 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.shortimize.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Shortimize. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.shortimize/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shortimize-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=shortimize), read 4 November 2026 - [Shortimize website](https://shortimize.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ShortSync MCP server | Agent MCP Directory" description: "ShortSync: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/shortsync-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ShortSync MCP server | Agent MCP Directory > ShortSync: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/shortsync-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # ShortSync: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ShortSync at www.shortsync.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ShortSync | | --- | --- | | Domain | shortsync.app | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for shortsync.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.shortsync.app/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 543 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:29Z https://www.shortsync.app/api/mcp sent initialize result auth-required (HTTP 401) 601 ms - 20:04:29Z https://www.shortsync.app/api/mcp sent initialize result auth-required (HTTP 401) 543 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.shortsync.app/.well-known/oauth-protected-resource" | | Protected resource metadata | www.shortsync.app | | Authorization server metadata | www.shortsync.app | | Registration endpoint | https://www.shortsync.app/api/oauth/register | ### The sign-in route, step by step 1. Request `https://www.shortsync.app/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.shortsync.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.shortsync.app/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ShortSync. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.shortsync/shortsync | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shortsync-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=shortsync), read 4 November 2026 - [ShortSync website](https://shortsync.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Shuttle MCP server | Agent MCP Directory" description: "Does Shuttle have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/shuttle-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Shuttle MCP server | Agent MCP Directory > Does Shuttle have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/shuttle-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Shuttle: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Shuttle (shuttle.dev), so the connector had nothing to connect to. Ora's cached score for shuttle.dev is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Shuttle (registry title: shuttle.dev) | | --- | --- | | Domain | shuttle.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for shuttle.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Shuttle. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for shuttle.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Shuttle. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/shuttle-dev/index.md) ## Sources - [Ora score page for shuttle.dev](https://ora.ai/score/shuttle.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/leaderboard) - [Where Shuttle was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Shuttle website](https://shuttle.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SID AI MCP server | Agent MCP Directory" description: "Does SID AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sid-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SID AI MCP server | Agent MCP Directory > Does SID AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sid-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # SID AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SID AI (sid.ai), so the connector had nothing to connect to. Ora's cached score for sid.ai is 35, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SID AI | | --- | --- | | Domain | sid.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 35, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sid.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SID AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sid.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SID AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sid-ai/index.md) ## Sources - [Ora score page for sid.ai](https://ora.ai/score/sid.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where SID AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SID AI website](https://sid.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Siemens MCP server | Agent MCP Directory" description: "Siemens has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/siemens-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Siemens MCP server | Agent MCP Directory > Siemens has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/siemens-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Siemens: MCP server, CLI and agent surfaces Yes: Siemens runs a public MCP server at mcp.siemens.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: siemens\_assets, siemens\_developer\_search, siemens\_search. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for siemens.com is 56, grade C, read on 5 November 2026. ## Fact sheet | Company | Siemens | | --- | --- | | Domain | siemens.com | | Category | Hardware & Robotics (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 1,197 on the list of 4 November 2026 | | Ora score | 56, grade C; Ora scanned the domain on 8 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for siemens.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.siemens.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | siemens-mcp-server 2026-11-04-cb570be | | Capabilities | tools, resources, prompts, logging | | Tools | 6 | | Resources | 7 | | Prompts | 6 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,455 ms over 1 attempt | ### Tools listed 6 tools - siemens\_assets - siemens\_developer\_search - siemens\_search - siemens\_aiSearch - siemens\_productSearch - siemens\_get\_web\_content ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.siemens.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 995 ms - 20:01:33Z https://mcp.siemens.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1455 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.siemens.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Siemens. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.siemens.mcp/siemens | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/siemens-com/index.md) ## Sources - [Ora score page for siemens.com](https://ora.ai/score/siemens.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 September 2026, read from GET /api/score) - [Where Siemens was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.siemens.mcp%2Fsiemens), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=siemens), read 4 November 2026 - [Siemens website](https://siemens.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SigmaMind AI MCP server | Agent MCP Directory" description: "Does SigmaMind AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sigmamind-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SigmaMind AI MCP server | Agent MCP Directory > Does SigmaMind AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sigmamind-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # SigmaMind AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SigmaMind AI (sigmamind.ai), so the connector had nothing to connect to. Ora's cached score for sigmamind.ai is 74, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SigmaMind AI | | --- | --- | | Domain | sigmamind.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 74, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sigmamind.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SigmaMind AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sigmamind.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SigmaMind AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sigmamind-ai/index.md) ## Sources - [Ora score page for sigmamind.ai](https://ora.ai/score/sigmamind.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where SigmaMind AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SigmaMind AI website](https://sigmamind.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Signadot MCP server | Agent MCP Directory" description: "Signadot has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/signadot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Signadot MCP server | Agent MCP Directory > Signadot has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/signadot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Signadot: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Signadot; the connector tried mcp.signadot.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | Signadot (registry title: signadot.com) | | --- | --- | | Domain | signadot.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 68, grade C; Ora scanned the domain on 28 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for signadot.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.signadot.com/mcp | | --- | --- | | How it was found | mcp.signadot.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,802 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:31Z https://mcp.signadot.com/mcp sent initialize result no-answer (HTTP 404) 1713 ms - 20:04:32Z https://mcp.signadot.com/mcp sent initialize result no-answer (HTTP 404) 1802 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.signadot.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Signadot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/signadot-com/index.md) ## Sources - [Ora score page for signadot.com](https://ora.ai/score/signadot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 August 2026, read from GET /api/leaderboard) - [Where Signadot was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Signadot website](https://signadot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SigNoz MCP server | Agent MCP Directory" description: "Does SigNoz have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/signoz-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SigNoz MCP server | Agent MCP Directory > Does SigNoz have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/signoz-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # SigNoz: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SigNoz (signoz.io), so the connector had nothing to connect to. Ora's cached score for signoz.io is 71, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SigNoz (registry title: signoz.io) | | --- | --- | | Domain | signoz.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 71, grade B; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for signoz.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SigNoz. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for signoz.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SigNoz. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: signoz.io/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/signoz-io/index.md) ## Sources - [Ora score page for signoz.io](https://ora.ai/score/signoz.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Where SigNoz was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SigNoz website](https://signoz.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SimpleBackups MCP server | Agent MCP Directory" description: "SimpleBackups: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/simplebackups-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SimpleBackups MCP server | Agent MCP Directory > SimpleBackups: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/simplebackups-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SimpleBackups: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SimpleBackups at mcp.simplebackups.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SimpleBackups | | --- | --- | | Domain | simplebackups.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for simplebackups.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.simplebackups.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,031 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:31Z https://mcp.simplebackups.ai/mcp sent initialize result auth-required (HTTP 401) 1310 ms - 20:04:31Z https://mcp.simplebackups.ai/mcp sent initialize result auth-required (HTTP 401) 1031 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.simplebackups.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.simplebackups.ai | | Authorization server metadata | my.simplebackups.com | | Registration endpoint | https://mcp.simplebackups.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.simplebackups.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.simplebackups.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.simplebackups.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SimpleBackups. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.simplebackups/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/simplebackups-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=simplebackups), read 4 November 2026 - [SimpleBackups website](https://simplebackups.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Simplenote MCP server | Agent MCP Directory" description: "Does Simplenote have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/simplenote-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Simplenote MCP server | Agent MCP Directory > Does Simplenote have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/simplenote-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Simplenote: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Simplenote (simplenote.com), so the connector had nothing to connect to. Ora's cached score for simplenote.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Simplenote (registry title: simplenote.com) | | --- | --- | | Domain | simplenote.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 26 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for simplenote.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Simplenote. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for simplenote.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Simplenote. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/simplenote-com/index.md) ## Sources - [Ora score page for simplenote.com](https://ora.ai/score/simplenote.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 August 2026, read from GET /api/leaderboard) - [Where Simplenote was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Simplenote website](https://simplenote.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SimplePDF MCP server | Agent MCP Directory" description: "SimplePDF: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/simplepdf-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SimplePDF MCP server | Agent MCP Directory > SimplePDF: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/simplepdf-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SimplePDF: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SimplePDF at simplepdf.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SimplePDF | | --- | --- | | Domain | simplepdf.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 87, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for simplepdf.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://simplepdf.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 577 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:31Z https://simplepdf.com/mcp sent initialize result auth-required (HTTP 401) 746 ms - 20:04:31Z https://simplepdf.com/mcp sent initialize result auth-required (HTTP 401) 577 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://simplepdf.com/.well-known/oauth-protected-resource", scope="profile email" | | Protected resource metadata | simplepdf.com | | Authorization server metadata | simplepdf.com | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://simplepdf.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://simplepdf.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SimplePDF. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: simplepdf.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: simplepdf.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.simplepdf/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/simplepdf-com/index.md) ## Sources - [Ora score page for simplepdf.com](https://ora.ai/score/simplepdf.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where SimplePDF was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.simplepdf%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=simplepdf), read 4 November 2026 - [SimplePDF website](https://simplepdf.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Simplescraper MCP server | Agent MCP Directory" description: "Simplescraper: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/simplescraper-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Simplescraper MCP server | Agent MCP Directory > Simplescraper: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/simplescraper-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Simplescraper: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Simplescraper at mcp.simplescraper.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Simplescraper | | --- | --- | | Domain | simplescraper.io | | Category | Agent Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for simplescraper.io when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.simplescraper.io/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 190 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:30Z https://mcp.simplescraper.io/mcp sent initialize result auth-required (HTTP 401) 329 ms - 20:04:31Z https://mcp.simplescraper.io/mcp sent initialize result auth-required (HTTP 401) 190 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.simplescraper.io/.well-known/oauth-protected-resource/mcp", scope="scrape" | | Protected resource metadata | mcp.simplescraper.io | | Authorization server metadata | mcp.simplescraper.io | | Registration endpoint | https://mcp.simplescraper.io/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.simplescraper.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.simplescraper.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.simplescraper.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Simplescraper. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/simplescraper-io/index.md) ## Sources - [Where Simplescraper was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Simplescraper website](https://simplescraper.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Simvoly MCP server | Agent MCP Directory" description: "Does Simvoly have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/simvoly-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Simvoly MCP server | Agent MCP Directory > Does Simvoly have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/simvoly-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Simvoly: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Simvoly (simvoly.com), so the connector had nothing to connect to. Ora's cached score for simvoly.com is 54, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Simvoly (registry title: simvoly.com) | | --- | --- | | Domain | simvoly.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 54, grade C; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for simvoly.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Simvoly. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for simvoly.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Simvoly. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/simvoly-com/index.md) ## Sources - [Ora score page for simvoly.com](https://ora.ai/score/simvoly.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/leaderboard) - [Where Simvoly was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Simvoly website](https://simvoly.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Since.dev MCP server | Agent MCP Directory" description: "Since.dev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/since-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Since.dev MCP server | Agent MCP Directory > Since.dev: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/since-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Since.dev: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Since.dev at api.since.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Since.dev | | --- | --- | | Domain | since.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for since.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.since.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,283 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:31Z https://api.since.dev/mcp sent initialize result auth-required (HTTP 401) 1040 ms - 20:04:33Z https://api.since.dev/mcp sent initialize result auth-required (HTTP 401) 1283 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.since.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.since.dev | | Authorization server metadata | api.since.dev | | Registration endpoint | https://api.since.dev/api/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://api.since.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.since.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.since.dev/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Since.dev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/since-dev/index.md) ## Sources - [Where Since.dev was found](https://github.com/mcp/Since-dev/mcp), read 4 November 2026 - [Since.dev website](https://since.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sisense MCP server | Agent MCP Directory" description: "Sisense: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/sisense-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sisense MCP server | Agent MCP Directory > Sisense: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/sisense-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sisense: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sisense at mcp.sisense.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sisense | | --- | --- | | Domain | sisense.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 71, grade B; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sisense.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sisense.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 633 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:31Z https://mcp.sisense.com/mcp sent initialize result auth-required (HTTP 401) 676 ms - 20:04:32Z https://mcp.sisense.com/mcp sent initialize result auth-required (HTTP 401) 633 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://mcp.sisense.com", scope="openid mcp:access offline_access", resource_metadata="https://mcp.sisense.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.sisense.com | | Authorization server metadata | mcp.sisense.com | | Registration endpoint | https://mcp.sisense.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.sisense.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sisense.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sisense.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sisense. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.sisense/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sisense-com/index.md) ## Sources - [Ora score page for sisense.com](https://ora.ai/score/sisense.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/leaderboard) - [Where Sisense was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.sisense%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sisense), read 4 November 2026 - [Sisense website](https://sisense.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Site24x7 MCP server | Agent MCP Directory" description: "Does Site24x7 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/site24x7-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Site24x7 MCP server | Agent MCP Directory > Does Site24x7 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/site24x7-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Site24x7: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Site24x7 (site24x7.com), so the connector had nothing to connect to. Ora's cached score for site24x7.com is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Site24x7 (registry title: site24x7.com) | | --- | --- | | Domain | site24x7.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for site24x7.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Site24x7. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for site24x7.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Site24x7. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/site24x7-com/index.md) ## Sources - [Ora score page for site24x7.com](https://ora.ai/score/site24x7.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where Site24x7 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Site24x7 website](https://site24x7.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sitecore MCP server | Agent MCP Directory" description: "Does Sitecore have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sitecore-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sitecore MCP server | Agent MCP Directory > Does Sitecore have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sitecore-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sitecore: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sitecore (sitecore.com), so the connector had nothing to connect to. Ora's cached score for sitecore.com is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sitecore (registry title: sitecore.com) | | --- | --- | | Domain | sitecore.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sitecore.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sitecore. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sitecore.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sitecore. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sitecore-com/index.md) ## Sources - [Ora score page for sitecore.com](https://ora.ai/score/sitecore.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Sitecore was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sitecore website](https://sitecore.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sitelemetry MCP server | Agent MCP Directory" description: "Sitelemetry: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/sitelemetry-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sitelemetry MCP server | Agent MCP Directory > Sitelemetry: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/sitelemetry-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sitelemetry: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sitelemetry at sitelemetry.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sitelemetry | | --- | --- | | Domain | sitelemetry.com | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for sitelemetry.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://sitelemetry.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 472 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:32Z https://sitelemetry.com/mcp sent initialize result auth-required (HTTP 401) 634 ms - 20:04:32Z https://sitelemetry.com/mcp sent initialize result auth-required (HTTP 401) 472 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://sitelemetry.com/.well-known/oauth-protected-resource/mcp", scope="audit" | | Protected resource metadata | sitelemetry.com | | Authorization server metadata | sitelemetry.com | | Registration endpoint | https://sitelemetry.com/oauth/register | ### The sign-in route, step by step 1. Request `https://sitelemetry.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://sitelemetry.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://sitelemetry.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sitelemetry. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.sitelemetry/sitelemetry | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sitelemetry-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sitelemetry), read 4 November 2026 - [Sitelemetry website](https://sitelemetry.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sitepulsar MCP server | Agent MCP Directory" description: "Sitepulsar has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sitepulsar-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sitepulsar MCP server | Agent MCP Directory > Sitepulsar has an open MCP server with 13 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sitepulsar-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sitepulsar: MCP server, CLI and agent surfaces Yes: Sitepulsar runs a public MCP server at mcp.sitepulsar.ai that listed 13 tools to a client with no credentials on 4 November 2026. Examples: check\_agent\_readiness, run\_audit, get\_audit. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Sitepulsar | | --- | --- | | Domain | sitepulsar.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for sitepulsar.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sitepulsar.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | sitepulsar-mcp 0.0.1 | | Capabilities | tools | | Tools | 13 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 890 ms over 1 attempt | ### Tools listed 13 tools - check\_agent\_readiness - run\_audit - get\_audit - get\_audit\_detail - compare\_aeo - get\_fixes - get\_audit\_full - search\_companies - probe\_agent\_discovery - probe\_ucp\_readiness - probe\_mcp\_functional - scan\_product\_page - scan\_visibility ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:32Z https://mcp.sitepulsar.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 964 ms - 20:04:33Z https://mcp.sitepulsar.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 890 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.sitepulsar.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sitepulsar. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.sitepulsar.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.sitepulsar/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sitepulsar-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sitepulsar), read 4 November 2026 - [Sitepulsar website](https://sitepulsar.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sixtyfour MCP server | Agent MCP Directory" description: "Sixtyfour: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/sixtyfour-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sixtyfour MCP server | Agent MCP Directory > Sixtyfour: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/sixtyfour-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sixtyfour: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Sixtyfour; the connector's guess at mcp.sixtyfour.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sixtyfour (registry title: sixtyfour.ai) | | --- | --- | | Domain | sixtyfour.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 79, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sixtyfour.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sixtyfour.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,143 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:33Z https://mcp.sixtyfour.ai/mcp sent initialize result auth-required (HTTP 401) 1422 ms - 20:04:34Z https://mcp.sixtyfour.ai/mcp sent initialize result auth-required (HTTP 401) 1143 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.sixtyfour.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.sixtyfour.ai | | Authorization server metadata | mcp.sixtyfour.ai | | Registration endpoint | https://mcp.sixtyfour.ai/register | ### The sign-in route, step by step 1. Request `https://mcp.sixtyfour.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sixtyfour.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sixtyfour.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sixtyfour. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sixtyfour-ai/index.md) ## Sources - [Ora score page for sixtyfour.ai](https://ora.ai/score/sixtyfour.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Sixtyfour was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sixtyfour website](https://sixtyfour.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SkillDB MCP server | Agent MCP Directory" description: "SkillDB: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/skilldb-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SkillDB MCP server | Agent MCP Directory > SkillDB: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/skilldb-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # SkillDB: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SkillDB at skilldb.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SkillDB | | --- | --- | | Domain | skilldb.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for skilldb.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://skilldb.dev/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 714 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:33Z https://skilldb.dev/api/mcp sent initialize result auth-required (HTTP 401) 1027 ms - 20:04:33Z https://skilldb.dev/api/mcp sent initialize result auth-required (HTTP 401) 714 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://skilldb.dev/.well-known/oauth-protected-resource" | | Protected resource metadata | skilldb.dev | | Authorization server metadata | skilldb.dev | | Registration endpoint | https://skilldb.dev/api/oauth/register | ### The sign-in route, step by step 1. Request `https://skilldb.dev/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://skilldb.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://skilldb.dev/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SkillDB. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/skilldb-dev/index.md) ## Sources - [SkillDB website](https://skilldb.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SKU.io MCP server | Agent MCP Directory" description: "SKU.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sku-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SKU.io MCP server | Agent MCP Directory > SKU.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sku-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # SKU.io: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SKU.io at mcp.sku.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SKU.io | | --- | --- | | Domain | sku.io | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for sku.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sku.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,189 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:33Z https://mcp.sku.io/mcp sent initialize result auth-required (HTTP 401) 1296 ms - 20:04:34Z https://mcp.sku.io/mcp sent initialize result auth-required (HTTP 401) 1189 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.sku.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.sku.io | | Authorization server metadata | mcp.sku.io | | Registration endpoint | https://mcp.sku.io/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.sku.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sku.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sku.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SKU.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sku-io/index.md) ## Sources - [SKU.io website](https://sku.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SkyAccess MCP server | Agent MCP Directory" description: "SkyAccess has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/skyaccess-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SkyAccess MCP server | Agent MCP Directory > SkyAccess has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/skyaccess-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SkyAccess: MCP server, CLI and agent surfaces Yes: SkyAccess runs a public MCP server at mcp.skyaccess.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: search\_empty\_legs, get\_flight, booking\_handoff. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | SkyAccess | | --- | --- | | Domain | skyaccess.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for skyaccess.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.skyaccess.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | SkyAccess 1.0.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,112 ms over 1 attempt | ### Tools listed 6 tools - search\_empty\_legs - get\_flight - booking\_handoff - get\_charter\_estimate - list\_routes - request\_booking ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:33Z https://mcp.skyaccess.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1349 ms - 20:04:34Z https://mcp.skyaccess.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1112 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.skyaccess.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SkyAccess. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.skyaccess/skyaccess | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/skyaccess-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=skyaccess), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Skydropx MCP server | Agent MCP Directory" description: "Skydropx: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Logistics & Supply Chain." canonical: https://agentmcpdirectory.com/directory/skydropx-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Skydropx MCP server | Agent MCP Directory > Skydropx: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Logistics & Supply Chain. Source: https://agentmcpdirectory.com/directory/skydropx-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Skydropx: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Skydropx at mcp.skydropx.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Skydropx | | --- | --- | | Domain | skydropx.com | | Category | Logistics & Supply Chain (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 41, grade D; Ora scanned the domain on 6 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for skydropx.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.skydropx.com/ | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 956 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:33Z https://mcp.skydropx.com/ sent initialize result auth-required (HTTP 401) 1189 ms - 20:04:34Z https://mcp.skydropx.com/ sent initialize result auth-required (HTTP 401) 956 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.skydropx.com/.well-known/oauth-protected-resource", scope="read write" | | Protected resource metadata | mcp.skydropx.com | | Authorization server metadata | mcp.skydropx.com | | Registration endpoint | https://mcp.skydropx.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.skydropx.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.skydropx.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.skydropx.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Skydropx. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.skydropx/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/skydropx-com/index.md) ## Sources - [Ora score page for skydropx.com](https://ora.ai/score/skydropx.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 August 2026, read from GET /api/leaderboard) - [Where Skydropx was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.skydropx%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=skydropx), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Skyhook MCP server | Agent MCP Directory" description: "Does Skyhook have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/skyhook-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Skyhook MCP server | Agent MCP Directory > Does Skyhook have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/skyhook-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Skyhook: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Skyhook (skyhook.io), so the connector had nothing to connect to. Ora's cached score for skyhook.io is 72, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Skyhook (registry title: skyhook.io) | | --- | --- | | Domain | skyhook.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for skyhook.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Skyhook. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for skyhook.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Skyhook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/skyhook-io/index.md) ## Sources - [Ora score page for skyhook.io](https://ora.ai/score/skyhook.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Skyhook was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Skyhook website](https://skyhook.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Skyvern MCP server | Agent MCP Directory" description: "Skyvern: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/skyvern-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Skyvern MCP server | Agent MCP Directory > Skyvern: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/skyvern-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Skyvern: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Skyvern at api.skyvern.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Skyvern | | --- | --- | | Domain | skyvern.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 87, grade A; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for skyvern.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.skyvern.com/mcp/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,132 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:35Z https://api.skyvern.com/mcp/ sent initialize result auth-required (HTTP 401) 1438 ms - 20:04:35Z https://api.skyvern.com/mcp/ sent initialize result auth-required (HTTP 401) 1132 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://api.skyvern.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.skyvern.com | | Authorization server metadata | api.skyvern.com | | Registration endpoint | https://api.skyvern.com/oauth/register | ### The sign-in route, step by step 1. Request `https://api.skyvern.com/mcp/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.skyvern.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.skyvern.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Skyvern. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: skyvern.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: skyvern.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/skyvern-com/index.md) ## Sources - [Ora score page for skyvern.com](https://ora.ai/score/skyvern.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Skyvern was found](https://github.com/mcp/Skyvern-AI/skyvern), read 4 November 2026 - [Skyvern website](https://skyvern.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Slack MCP server | Agent MCP Directory" description: "Slack: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/slack-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Slack MCP server | Agent MCP Directory > Slack: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/slack-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Slack: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Slack at mcp.slack.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Slack | | --- | --- | | Domain | slack.com | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Tranco rank | 301 on the list of 4 November 2026 | | Ora score | 59, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for slack.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.slack.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 807 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:53Z https://mcp.slack.com/mcp sent initialize result auth-required (HTTP 401) 743 ms - 20:01:29Z https://mcp.slack.com/mcp sent initialize result auth-required (HTTP 401) 807 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.slack.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.slack.com | | Authorization server metadata | mcp.slack.com | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.slack.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://mcp.slack.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Slack. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/slack-com/index.md) ## Sources - [Ora score page for slack.com](https://ora.ai/score/slack.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/score) - [Where Slack was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Slack website](https://slack.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SlideForge MCP server | Agent MCP Directory" description: "SlideForge has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/slideforge-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SlideForge MCP server | Agent MCP Directory > SlideForge has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/slideforge-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # SlideForge: MCP server, CLI and agent surfaces Yes: SlideForge runs a public MCP server at api.slideforge.dev that listed 9 tools to a client with no credentials on 4 November 2026. Examples: browse\_catalog, plan\_slide, create\_slide. It speaks streamable-http, protocol 2025-03-26. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | SlideForge | | --- | --- | | Domain | slideforge.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for slideforge.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.slideforge.dev/mcp/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | slideforge 5.0.0 | | Capabilities | tools, prompts, resources | | Tools | 9 | | Resources | 2 | | Prompts | 2 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 775 ms over 1 attempt | ### Tools listed 9 tools - browse\_catalog - plan\_slide - create\_slide - create\_deck - edit\_slide - edit\_deck - translate\_deck - upload\_asset - manage\_account ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:34Z https://api.slideforge.dev/mcp/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 890 ms - 20:04:35Z https://api.slideforge.dev/mcp/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 775 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.slideforge.dev/mcp/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SlideForge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.slideforge/slideforge | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/slideforge-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=slideforge), read 4 November 2026 - [SlideForge website](https://slideforge.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SmartBear MCP server | Agent MCP Directory" description: "SmartBear: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/smartbear-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SmartBear MCP server | Agent MCP Directory > SmartBear: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/smartbear-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SmartBear: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SmartBear at zephyr.mcp.smartbear.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SmartBear (registry title: SmartBear MCP) | | --- | --- | | Domain | smartbear.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for smartbear.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://zephyr.mcp.smartbear.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,665 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:35Z https://zephyr.mcp.smartbear.com/mcp sent initialize result auth-required (HTTP 401) 1631 ms - 20:04:36Z https://zephyr.mcp.smartbear.com/mcp sent initialize result auth-required (HTTP 401) 1665 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | OAuth resource_metadata="https://zephyr.mcp.smartbear.com/.well-known/oauth-protected-resource" | | Protected resource metadata | zephyr.mcp.smartbear.com | | Authorization server metadata | app.tm4j.smartbear.com | | Registration endpoint | https://app.tm4j.smartbear.com/backend/oauthproxy/register | ### The sign-in route, step by step 1. Request `https://zephyr.mcp.smartbear.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://zephyr.mcp.smartbear.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.tm4j.smartbear.com/backend/oauthproxy/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SmartBear. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.smartbear/smartbear-mcp, com.smartbear/swagger-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/smartbear-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=smartbear), read 4 November 2026 - [SmartBear website](https://smartbear.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SmartGate MCP server | Agent MCP Directory" description: "SmartGate: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/smartgate-network site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SmartGate MCP server | Agent MCP Directory > SmartGate: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/smartgate-network Site: Agent MCP Directory Last reviewed: 2026-11-05 # SmartGate: MCP server, CLI and agent surfaces Not counted. The endpoint listed for SmartGate at smartgate.network asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | SmartGate | | --- | --- | | Domain | smartgate.network | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for smartgate.network when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://smartgate.network/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 998 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:35Z https://smartgate.network/api/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1868 ms - 20:04:35Z https://smartgate.network/api/mcp sent initialize result auth-required-no-oauth (HTTP 401) 998 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://smartgate.network/api/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SmartGate. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/smartgate-network/index.md) ## Sources - [SmartGate website](https://smartgate.network), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Smobi MCP server | Agent MCP Directory" description: "Does Smobi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/smobi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Smobi MCP server | Agent MCP Directory > Does Smobi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/smobi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Smobi: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Smobi (smobi.com), so the connector had nothing to connect to. Ora's cached score for smobi.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Smobi (registry title: smobi.com) | | --- | --- | | Domain | smobi.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 27 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for smobi.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Smobi. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for smobi.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Smobi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/smobi-com/index.md) ## Sources - [Ora score page for smobi.com](https://ora.ai/score/smobi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 September 2026, read from GET /api/leaderboard) - [Where Smobi was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Smobi website](https://smobi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "smol machines MCP server | Agent MCP Directory" description: "Does smol machines have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/smolmachines-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # smol machines MCP server | Agent MCP Directory > Does smol machines have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/smolmachines-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # smol machines: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for smol machines (smolmachines.com), so the connector had nothing to connect to. Ora's cached score for smolmachines.com is 80, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | smol machines (registry title: smolmachines.com) | | --- | --- | | Domain | smolmachines.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 80, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for smolmachines.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for smol machines. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for smolmachines.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for smol machines. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: smolmachines.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/smolmachines-com/index.md) ## Sources - [Ora score page for smolmachines.com](https://ora.ai/score/smolmachines.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where smol machines was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [smol machines website](https://smolmachines.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Snorkel AI MCP server | Agent MCP Directory" description: "Does Snorkel AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/snorkel-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Snorkel AI MCP server | Agent MCP Directory > Does Snorkel AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/snorkel-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Snorkel AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Snorkel AI (snorkel.ai), so the connector had nothing to connect to. Ora's cached score for snorkel.ai is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Snorkel AI | | --- | --- | | Domain | snorkel.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 31 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for snorkel.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Snorkel AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for snorkel.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Snorkel AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/snorkel-ai/index.md) ## Sources - [Ora score page for snorkel.ai](https://ora.ai/score/snorkel.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 August 2026, read from GET /api/leaderboard) - [Where Snorkel AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Snorkel AI website](https://snorkel.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Snowflake MCP server | Agent MCP Directory" description: "Does Snowflake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/snowflake-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Snowflake MCP server | Agent MCP Directory > Does Snowflake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/snowflake-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Snowflake: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Snowflake (snowflake.com), so the connector had nothing to connect to. A CLI is on record: snowflake-cli on pypi. Ora's cached score for snowflake.com is 66, grade C, read on 5 November 2026. ## Fact sheet | Company | Snowflake | | --- | --- | | Domain | snowflake.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,293 on the list of 4 November 2026 | | Ora score | 66, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for snowflake.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Snowflake. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for snowflake.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI | Package | snowflake-cli on pypi (page) | | --- | --- | | Exists | yes | | Latest version | 3.32.1 | | Last publish | 2 November 2026 | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: snowflake.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/snowflake-com/index.md) ## Sources - [snowflake-cli on pypi](https://pypi.org/project/snowflake-cli/), read 4 November 2026 - [Ora score page for snowflake.com](https://ora.ai/score/snowflake.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where Snowflake was found](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp), read 4 November 2026 - [Snowflake website](https://snowflake.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Snyk MCP server | Agent MCP Directory" description: "Does Snyk have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/snyk-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Snyk MCP server | Agent MCP Directory > Does Snyk have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/snyk-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Snyk: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Snyk (snyk.io), so the connector had nothing to connect to. Ora's cached score for snyk.io is 79, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Snyk | | --- | --- | | Domain | snyk.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 79, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for snyk.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Snyk. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for snyk.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Snyk. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/snyk-io/index.md) ## Sources - [Ora score page for snyk.io](https://ora.ai/score/snyk.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Snyk was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Snyk website](https://snyk.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Social Growth Engineers MCP server | Agent MCP Directory" description: "Social Growth Engineers: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/socialgrowthengineers-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Social Growth Engineers MCP server | Agent MCP Directory > Social Growth Engineers: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/socialgrowthengineers-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Social Growth Engineers: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Social Growth Engineers at www.socialgrowthengineers.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Social Growth Engineers | | --- | --- | | Domain | socialgrowthengineers.com | | Category | E-commerce (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for socialgrowthengineers.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.socialgrowthengineers.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,015 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:36Z https://www.socialgrowthengineers.com/mcp sent initialize result auth-required (HTTP 401) 1612 ms - 20:04:36Z https://www.socialgrowthengineers.com/mcp sent initialize result auth-required (HTTP 401) 1015 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.socialgrowthengineers.com/.well-known/oauth-protected-resource/mcp", scope="email" | | Protected resource metadata | www.socialgrowthengineers.com | | Authorization server metadata | vmuswetydyupmkcvmyxi.supabase.co | | Registration endpoint | https://vmuswetydyupmkcvmyxi.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://www.socialgrowthengineers.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.socialgrowthengineers.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://vmuswetydyupmkcvmyxi.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Social Growth Engineers. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.socialgrowthengineers/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/socialgrowthengineers-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=socialgrowthengineers), read 4 November 2026 - [Social Growth Engineers website](https://socialgrowthengineers.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sociality.io MCP server | Agent MCP Directory" description: "Sociality.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/sociality-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sociality.io MCP server | Agent MCP Directory > Sociality.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/sociality-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sociality.io: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sociality.io at api.sociality.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sociality.io (registry title: Sociality.io MCP) | | --- | --- | | Domain | sociality.io | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 73, grade B; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sociality.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.sociality.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 642 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:35Z https://api.sociality.io/mcp sent initialize result auth-required (HTTP 401) 783 ms - 20:04:36Z https://api.sociality.io/mcp sent initialize result auth-required (HTTP 401) 642 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://api.sociality.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.sociality.io | | Authorization server metadata | api.sociality.io | | Registration endpoint | https://api.sociality.io/oauth/register | ### The sign-in route, step by step 1. Request `https://api.sociality.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.sociality.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.sociality.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sociality.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sociality-io/index.md) ## Sources - [Ora score page for sociality.io](https://ora.ai/score/sociality.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Sociality.io website](https://sociality.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Socialync MCP server | Agent MCP Directory" description: "Socialync: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/socialync-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Socialync MCP server | Agent MCP Directory > Socialync: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/socialync-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Socialync: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Socialync at mcp.socialync.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Socialync | | --- | --- | | Domain | socialync.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for socialync.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.socialync.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,079 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:36Z https://mcp.socialync.io/mcp sent initialize result auth-required (HTTP 401) 1637 ms - 20:04:36Z https://mcp.socialync.io/mcp sent initialize result auth-required (HTTP 401) 1079 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.socialync.io/.well-known/oauth-protected-resource/mcp", error="invalid_request", error_description="Missing Authorization: Bearer header" | | Protected resource metadata | mcp.socialync.io | | Authorization server metadata | www.socialync.io | | Registration endpoint | https://www.socialync.io/api/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.socialync.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.socialync.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://www.socialync.io/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Socialync. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/socialync-io/index.md) ## Sources - [Socialync website](https://socialync.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Softr MCP server | Agent MCP Directory" description: "Does Softr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/softr-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Softr MCP server | Agent MCP Directory > Does Softr have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/softr-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Softr: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Softr (softr.io), so the connector had nothing to connect to. Ora's cached score for softr.io is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Softr (registry title: softr.io) | | --- | --- | | Domain | softr.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for softr.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Softr. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for softr.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Softr. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: softr.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/softr-io/index.md) ## Sources - [Ora score page for softr.io](https://ora.ai/score/softr.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/leaderboard) - [Where Softr was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Softr website](https://softr.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sofya MCP server | Agent MCP Directory" description: "Sofya: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sofya-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sofya MCP server | Agent MCP Directory > Sofya: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sofya-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sofya: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sofya at mcp.sofya.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sofya | | --- | --- | | Domain | sofya.co | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for sofya.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sofya.co/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,209 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:36Z https://mcp.sofya.co/mcp sent initialize result auth-required (HTTP 401) 1210 ms - 20:04:36Z https://mcp.sofya.co/mcp sent initialize result auth-required (HTTP 401) 1209 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Sofya", resource_metadata="https://mcp.sofya.co/.well-known/oauth-protected-resource", scope="mcp" | | Protected resource metadata | mcp.sofya.co | | Authorization server metadata | mcp.sofya.co | | Registration endpoint | https://mcp.sofya.co/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.sofya.co/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sofya.co/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sofya.co/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sofya. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: sofya.co (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.sofya/sofya | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sofya-co/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sofya), read 4 November 2026 - [Sofya website](https://sofya.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sonar MCP server | Agent MCP Directory" description: "Does Sonar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sonarsource-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sonar MCP server | Agent MCP Directory > Does Sonar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sonarsource-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sonar: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sonar (sonarsource.com), so the connector had nothing to connect to. Ora's cached score for sonarsource.com is 71, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sonar | | --- | --- | | Domain | sonarsource.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 71, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sonarsource.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sonar. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sonarsource.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sonar. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sonarsource-com/index.md) ## Sources - [Ora score page for sonarsource.com](https://ora.ai/score/sonarsource.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Sonar was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sonar website](https://sonarsource.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sonatype MCP server | Agent MCP Directory" description: "Sonatype: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/sonatype-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sonatype MCP server | Agent MCP Directory > Sonatype: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/sonatype-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sonatype: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Sonatype at mcp.guide.sonatype.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Sonatype (registry title: Sonatype Dependency Management) | | --- | --- | | Domain | sonatype.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 65, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sonatype.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.guide.sonatype.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,940 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:37Z https://mcp.guide.sonatype.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1623 ms - 20:04:37Z https://mcp.guide.sonatype.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1940 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="No Sonatype access token was supplied, so this MCP server is not authenticated. Add an 'Authorization: Bearer ' header to your MCP client configuration, using a token from your Sonatype account settings." | ### The sign-in route, step by step 1. Request `https://mcp.guide.sonatype.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sonatype. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.sonatype/dependency-management-mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sonatype-com/index.md) ## Sources - [Ora score page for sonatype.com](https://ora.ai/score/sonatype.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sonatype), read 4 November 2026 - [Sonatype website](https://sonatype.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Soracom MCP server | Agent MCP Directory" description: "Soracom has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/soracom-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Soracom MCP server | Agent MCP Directory > Soracom has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/soracom-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Soracom: MCP server, CLI and agent surfaces Yes: Soracom runs a public MCP server at knowledge-mcp.soracom.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: get\_document, search\_api\_docs, search\_soracom\_docs. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Soracom (registry title: Soracom Knowledge) | | --- | --- | | Domain | soracom.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for soracom.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://knowledge-mcp.soracom.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | soracom-knowledge 1.1.5 | | Capabilities | logging, tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,097 ms over 1 attempt | ### Tools listed 3 tools - get\_document - search\_api\_docs - search\_soracom\_docs ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:38Z https://knowledge-mcp.soracom.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2248 ms - 20:04:38Z https://knowledge-mcp.soracom.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2097 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://knowledge-mcp.soracom.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Soracom. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.soracom/knowledge | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/soracom-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=soracom), read 4 November 2026 - [Soracom website](https://soracom.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sourcebot MCP server | Agent MCP Directory" description: "Does Sourcebot have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sourcebot-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sourcebot MCP server | Agent MCP Directory > Does Sourcebot have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sourcebot-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sourcebot: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sourcebot (sourcebot.dev), so the connector had nothing to connect to. Ora's cached score for sourcebot.dev is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sourcebot (registry title: sourcebot.dev) | | --- | --- | | Domain | sourcebot.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 17 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sourcebot.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sourcebot. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sourcebot.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sourcebot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sourcebot-dev/index.md) ## Sources - [Ora score page for sourcebot.dev](https://ora.ai/score/sourcebot.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 September 2026, read from GET /api/leaderboard) - [Where Sourcebot was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sourcebot website](https://sourcebot.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SourceForge MCP server | Agent MCP Directory" description: "Does SourceForge have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sourceforge-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SourceForge MCP server | Agent MCP Directory > Does SourceForge have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sourceforge-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # SourceForge: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SourceForge (sourceforge.net), so the connector had nothing to connect to. Ora's cached score for sourceforge.net is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SourceForge (registry title: sourceforge.net) | | --- | --- | | Domain | sourceforge.net | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 250 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sourceforge.net, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SourceForge. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sourceforge.net, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SourceForge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: sourceforge.net/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sourceforge-net/index.md) ## Sources - [Ora score page for sourceforge.net](https://ora.ai/score/sourceforge.net?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/score) - [Where SourceForge was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SourceForge website](https://sourceforge.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sourcegraph MCP server | Agent MCP Directory" description: "Does Sourcegraph have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sourcegraph-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sourcegraph MCP server | Agent MCP Directory > Does Sourcegraph have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sourcegraph-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sourcegraph: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sourcegraph (sourcegraph.com), so the connector had nothing to connect to. Ora's cached score for sourcegraph.com is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sourcegraph | | --- | --- | | Domain | sourcegraph.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 24 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sourcegraph.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sourcegraph. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sourcegraph.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sourcegraph. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: sourcegraph.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sourcegraph-com/index.md) ## Sources - [Ora score page for sourcegraph.com](https://ora.ai/score/sourcegraph.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 September 2026, read from GET /api/leaderboard) - [Where Sourcegraph was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sourcegraph website](https://sourcegraph.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "sourcehut MCP server | Agent MCP Directory" description: "Does sourcehut have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sourcehut-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # sourcehut MCP server | Agent MCP Directory > Does sourcehut have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sourcehut-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # sourcehut: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for sourcehut (sourcehut.org), so the connector had nothing to connect to. Ora's cached score for sourcehut.org is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | sourcehut (registry title: sourcehut.org) | | --- | --- | | Domain | sourcehut.org | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sourcehut.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for sourcehut. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sourcehut.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for sourcehut. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sourcehut-org/index.md) ## Sources - [Ora score page for sourcehut.org](https://ora.ai/score/sourcehut.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where sourcehut was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [sourcehut website](https://sourcehut.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Spacefast MCP server | Agent MCP Directory" description: "Spacefast: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/spacefast-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Spacefast MCP server | Agent MCP Directory > Spacefast: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/spacefast-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spacefast: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Spacefast at mcp.spacefast.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Spacefast | | --- | --- | | Domain | spacefast.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 90, grade A; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for spacefast.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.spacefast.com?mode=full | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 916 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:38Z https://mcp.spacefast.com?mode=full sent initialize result auth-required (HTTP 401) 1345 ms - 20:04:37Z https://mcp.spacefast.com?mode=full sent initialize result auth-required (HTTP 401) 916 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.spacefast.com/.well-known/oauth-protected-resource", scope="teams:read teams:create teams:members.write sell:write spaces:read spaces:write spaces:rename spaces:access.write versions:download publish:write domains:read domains:write oauth-apps:write offline_access" | | Protected resource metadata | mcp.spacefast.com | | Authorization server metadata | api.spacefast.com | | Registration endpoint | https://api.spacefast.com/v1/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.spacefast.com?mode=full` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.spacefast.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.spacefast.com/v1/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Spacefast. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: api.spacefast.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spacefast-com/index.md) ## Sources - [Ora score page for spacefast.com](https://ora.ai/score/spacefast.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Where Spacefast was found](https://github.com/mcp/spacefast/mcp), read 4 November 2026 - [Spacefast website](https://spacefast.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Spacelift MCP server | Agent MCP Directory" description: "Does Spacelift have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/spacelift-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Spacelift MCP server | Agent MCP Directory > Does Spacelift have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/spacelift-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spacelift: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Spacelift (spacelift.io), so the connector had nothing to connect to. Ora's cached score for spacelift.io is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Spacelift (registry title: spacelift.io) | | --- | --- | | Domain | spacelift.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 1 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for spacelift.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Spacelift. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for spacelift.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Spacelift. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spacelift-io/index.md) ## Sources - [Ora score page for spacelift.io](https://ora.ai/score/spacelift.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 October 2026, read from GET /api/leaderboard) - [Where Spacelift was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Spacelift website](https://spacelift.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Speakeroo MCP server | Agent MCP Directory" description: "Speakeroo has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/speakeroo-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Speakeroo MCP server | Agent MCP Directory > Speakeroo has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/speakeroo-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Speakeroo: MCP server, CLI and agent surfaces Yes: Speakeroo runs a public MCP server at mcp.speakeroo.app that listed 7 tools to a client with no credentials on 4 November 2026. Examples: analyze\_transcript, refine\_transcript, analyze\_speech. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for speakeroo.app is 73, grade B, read on 5 November 2026. ## Fact sheet | Company | Speakeroo (registry title: Speakeroo speaking coach) | | --- | --- | | Domain | speakeroo.app | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 73, grade B; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for speakeroo.app, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.speakeroo.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | speakeroo 1.0.1 | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,213 ms over 1 attempt | ### Tools listed 7 tools - analyze\_transcript - refine\_transcript - analyze\_speech - get\_speech\_topics - how\_to\_pronounce - get\_speaking\_rubric - list\_filler\_words ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:39Z https://mcp.speakeroo.app/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2623 ms - 20:04:38Z https://mcp.speakeroo.app/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1213 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.speakeroo.app/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Speakeroo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.speakeroo/speaking-coach | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/speakeroo-app/index.md) ## Sources - [Ora score page for speakeroo.app](https://ora.ai/score/speakeroo.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=speakeroo), read 4 November 2026 - [Speakeroo website](https://speakeroo.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Specific MCP server | Agent MCP Directory" description: "Does Specific have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/specific-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Specific MCP server | Agent MCP Directory > Does Specific have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/specific-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Specific: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Specific (specific.dev), so the connector had nothing to connect to. Ora's cached score for specific.dev is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Specific (registry title: specific.dev) | | --- | --- | | Domain | specific.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for specific.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Specific. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for specific.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Specific. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/specific-dev/index.md) ## Sources - [Ora score page for specific.dev](https://ora.ai/score/specific.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Specific was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Specific website](https://specific.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Speedscale MCP server | Agent MCP Directory" description: "Does Speedscale have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/speedscale-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Speedscale MCP server | Agent MCP Directory > Does Speedscale have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/speedscale-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Speedscale: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Speedscale (speedscale.com), so the connector had nothing to connect to. Ora's cached score for speedscale.com is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Speedscale (registry title: speedscale.com) | | --- | --- | | Domain | speedscale.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for speedscale.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Speedscale. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for speedscale.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Speedscale. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/speedscale-com/index.md) ## Sources - [Ora score page for speedscale.com](https://ora.ai/score/speedscale.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 September 2026, read from GET /api/leaderboard) - [Where Speedscale was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Speedscale website](https://speedscale.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Spicrawl MCP server | Agent MCP Directory" description: "Spicrawl has an open MCP server with 24 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/spicrawl-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Spicrawl MCP server | Agent MCP Directory > Spicrawl has an open MCP server with 24 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/spicrawl-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spicrawl: MCP server, CLI and agent surfaces Yes: Spicrawl runs a public MCP server at mcp.spicrawl.com that listed 24 tools to a client with no credentials on 4 November 2026. Examples: spicrawl\_scrape, spicrawl\_batch\_submit, spicrawl\_batch\_list. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Spicrawl | | --- | --- | | Domain | spicrawl.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for spicrawl.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.spicrawl.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | spicrawl-mcp-server 0.1.7 | | Capabilities | tools | | Tools | 24 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,949 ms over 1 attempt | ### Tools listed 24 tools - spicrawl\_scrape - spicrawl\_batch\_submit - spicrawl\_batch\_list - spicrawl\_batch\_status - spicrawl\_batch\_results - spicrawl\_batch\_task\_content - spicrawl\_batch\_cancel - spicrawl\_batch\_retry - spicrawl\_batch\_add\_items - spicrawl\_batch\_close - spicrawl\_session\_create - spicrawl\_session\_list - spicrawl\_session\_get - spicrawl\_session\_context - spicrawl\_session\_release - spicrawl\_session\_delete - spicrawl\_usage - spicrawl\_usage\_summary - spicrawl\_usage\_reconciliation - spicrawl\_requests\_list - spicrawl\_request\_get - spicrawl\_docs\_search - spicrawl\_docs\_read - spicrawl\_docs\_index ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:39Z https://mcp.spicrawl.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2142 ms - 20:04:39Z https://mcp.spicrawl.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1949 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.spicrawl.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Spicrawl. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spicrawl-com/index.md) ## Sources - [Where Spicrawl was found](https://github.com/mcp/OfficialSpicrawl/mcp), read 4 November 2026 - [Spicrawl website](https://spicrawl.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Spike (spike.app) MCP server | Agent MCP Directory" description: "Does Spike (spike.app) have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/spike-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Spike (spike.app) MCP server | Agent MCP Directory > Does Spike (spike.app) have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/spike-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spike: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Spike (spike.app), so the connector had nothing to connect to. Ora's cached score for spike.app is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Spike (registry title: spike.app) | | --- | --- | | Domain | spike.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for spike.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Spike. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for spike.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Spike. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spike-app/index.md) ## Sources - [Ora score page for spike.app](https://ora.ai/score/spike.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Spike was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Spike website](https://spike.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Spike (spike.sh) MCP server | Agent MCP Directory" description: "Spike (spike.sh): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/spike-sh site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Spike (spike.sh) MCP server | Agent MCP Directory > Spike (spike.sh): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/spike-sh Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spike: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Spike; the connector's guess at mcp.spike.sh answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Spike (registry title: spike.sh) | | --- | --- | | Domain | spike.sh | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 15 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for spike.sh, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.spike.sh/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,358 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:39Z https://mcp.spike.sh/mcp sent initialize result auth-required (HTTP 401) 1553 ms - 20:04:39Z https://mcp.spike.sh/mcp sent initialize result auth-required (HTTP 401) 1358 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.spike.sh/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.spike.sh | | Authorization server metadata | api.spike.sh | | Registration endpoint | https://api.spike.sh/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.spike.sh/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.spike.sh/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.spike.sh/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Spike. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spike-sh/index.md) ## Sources - [Ora score page for spike.sh](https://ora.ai/score/spike.sh?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 September 2026, read from GET /api/leaderboard) - [Where Spike was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Spike website](https://spike.sh), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Spinnaker MCP server | Agent MCP Directory" description: "Does Spinnaker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/spinnaker-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Spinnaker MCP server | Agent MCP Directory > Does Spinnaker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/spinnaker-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spinnaker: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Spinnaker (spinnaker.io), so the connector had nothing to connect to. Ora's cached score for spinnaker.io is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Spinnaker (registry title: spinnaker.io) | | --- | --- | | Domain | spinnaker.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for spinnaker.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Spinnaker. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for spinnaker.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Spinnaker. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spinnaker-io/index.md) ## Sources - [Ora score page for spinnaker.io](https://ora.ai/score/spinnaker.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Spinnaker was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Spinnaker website](https://spinnaker.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Split.io MCP server | Agent MCP Directory" description: "Does Split.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/split-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Split.io MCP server | Agent MCP Directory > Does Split.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/split-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Split.io: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Split.io (split.io), so the connector had nothing to connect to. Ora's cached score for split.io is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Split.io | | --- | --- | | Domain | split.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 1,096 on the list of 4 November 2026 | | Ora score | 60, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for split.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Split.io. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for split.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Split.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/split-io/index.md) ## Sources - [Ora score page for split.io](https://ora.ai/score/split.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/score) - [Where Split.io was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Split.io website](https://split.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SpriteCook MCP server | Agent MCP Directory" description: "SpriteCook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media." canonical: https://agentmcpdirectory.com/directory/spritecook-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SpriteCook MCP server | Agent MCP Directory > SpriteCook: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media. Source: https://agentmcpdirectory.com/directory/spritecook-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # SpriteCook: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SpriteCook at api.spritecook.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SpriteCook | | --- | --- | | Domain | spritecook.ai | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 69, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for spritecook.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.spritecook.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 972 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:39Z https://api.spritecook.ai/mcp sent initialize result auth-required (HTTP 401) 1048 ms - 20:04:39Z https://api.spritecook.ai/mcp sent initialize result auth-required (HTTP 401) 972 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens." | | Protected resource metadata | api.spritecook.ai | | Authorization server metadata | api.spritecook.ai | | Registration endpoint | https://api.spritecook.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://api.spritecook.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.spritecook.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.spritecook.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SpriteCook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.spritecook.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.spritecook/generate | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spritecook-ai/index.md) ## Sources - [Ora score page for spritecook.ai](https://ora.ai/score/spritecook.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=spritecook), read 4 November 2026 - [SpriteCook website](https://spritecook.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Spurtest MCP server | Agent MCP Directory" description: "Does Spurtest have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/spurtest-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Spurtest MCP server | Agent MCP Directory > Does Spurtest have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/spurtest-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spurtest: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Spurtest (spurtest.com), so the connector had nothing to connect to. Ora's cached score for spurtest.com is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Spurtest (registry title: spurtest.com) | | --- | --- | | Domain | spurtest.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 30 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for spurtest.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Spurtest. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for spurtest.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Spurtest. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/spurtest-com/index.md) ## Sources - [Ora score page for spurtest.com](https://ora.ai/score/spurtest.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 August 2026, read from GET /api/leaderboard) - [Where Spurtest was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Spurtest website](https://spurtest.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Square (square.com) MCP server | Agent MCP Directory" description: "Square (square.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/square-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Square (square.com) MCP server | Agent MCP Directory > Square (square.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/square-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Square: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Square at mcp.squareup.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Square | | --- | --- | | Domain | square.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 26, grade F; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for square.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.squareup.com/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 129 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:39Z https://mcp.squareup.com/sse sent initialize result auth-required (HTTP 401) 150 ms - 20:04:38Z https://mcp.squareup.com/sse sent initialize result auth-required (HTTP 401) 129 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.squareup.com/.well-known/oauth-protected-resource/sse", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.squareup.com | | Authorization server metadata | mcp.squareup.com | | Registration endpoint | https://mcp.squareup.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.squareup.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.squareup.com/.well-known/oauth-protected-resource/sse` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.squareup.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Square. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/square-com/index.md) ## Sources - [Ora score page for square.com](https://ora.ai/score/square.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Where Square was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Square website](https://square.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Square (squareup.com) MCP server | Agent MCP Directory" description: "Square (squareup.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/squareup-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Square (squareup.com) MCP server | Agent MCP Directory > Square (squareup.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/squareup-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Square: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Square at mcp.squareup.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Square | | --- | --- | | Domain | squareup.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,023 on the list of 4 November 2026 | | Ora score | 57, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for squareup.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.squareup.com/sse | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 103 ms over 1 attempt | | Documentation | developer.squareup.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://mcp.squareup.com/sse sent initialize result auth-required (HTTP 401) 147 ms - 20:01:33Z https://mcp.squareup.com/sse sent initialize result auth-required (HTTP 401) 103 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.squareup.com/.well-known/oauth-protected-resource/sse", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.squareup.com | | Authorization server metadata | mcp.squareup.com | | Registration endpoint | https://mcp.squareup.com/register | ### The sign-in route, step by step 1. Request `https://mcp.squareup.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.squareup.com/.well-known/oauth-protected-resource/sse` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.squareup.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Square. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/squareup-com/index.md) ## Sources - [Square MCP documentation](https://developer.squareup.com/docs/mcp), read 4 November 2026 - [Ora score page for squareup.com](https://ora.ai/score/squareup.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/score) - [Square website](https://squareup.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sre MCP server | Agent MCP Directory" description: "Does Sre have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/sre-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sre MCP server | Agent MCP Directory > Does Sre have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/sre-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sre: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sre (sre.ai), so the connector had nothing to connect to. Ora's cached score for sre.ai is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sre (registry title: sre.ai) | | --- | --- | | Domain | sre.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sre.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sre. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sre.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sre. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sre-ai/index.md) ## Sources - [Ora score page for sre.ai](https://ora.ai/score/sre.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Sre was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sre website](https://sre.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SRIFT MCP server | Agent MCP Directory" description: "SRIFT has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/srift-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SRIFT MCP server | Agent MCP Directory > SRIFT has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/srift-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # SRIFT: MCP server, CLI and agent surfaces Yes: SRIFT runs a public MCP server at srift.app that listed 9 tools to a client with no credentials on 4 November 2026. Examples: srift\_start\_session, srift\_join\_session, srift\_session\_status. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | SRIFT | | --- | --- | | Domain | srift.app | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for srift.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://srift.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | srift-mcp-server 4.4.0 | | Capabilities | tools, resources, prompts, logging, extensions | | Tools | 9 | | Resources | 3 | | Prompts | 1 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 2,400 ms over 1 attempt | ### Tools listed 9 tools - srift\_start\_session - srift\_join\_session - srift\_session\_status - srift\_close\_session - srift\_approve\_join - srift\_reject\_join - srift\_kick\_user - srift\_list\_transfers - srift\_net\_diagnose ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:42Z https://srift.app/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3487 ms - 20:04:41Z https://srift.app/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2400 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://srift.app/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SRIFT. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: srift.app (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.srift/srift | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/srift-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=srift), read 4 November 2026 - [SRIFT website](https://srift.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SST MCP server | Agent MCP Directory" description: "Does SST have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/sst-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SST MCP server | Agent MCP Directory > Does SST have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/sst-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # SST: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SST (sst.dev), so the connector had nothing to connect to. Ora's cached score for sst.dev is 63, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SST | | --- | --- | | Domain | sst.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sst.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SST. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sst.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SST. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sst-dev/index.md) ## Sources - [Ora score page for sst.dev](https://ora.ai/score/sst.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where SST was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SST website](https://sst.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "StableBrowse MCP server | Agent MCP Directory" description: "Does StableBrowse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/stablebrowse-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # StableBrowse MCP server | Agent MCP Directory > Does StableBrowse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/stablebrowse-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # StableBrowse: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for StableBrowse (stablebrowse.com), so the connector had nothing to connect to. Ora's cached score for stablebrowse.com is 54, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | StableBrowse (registry title: stablebrowse.com) | | --- | --- | | Domain | stablebrowse.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 54, grade C; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for stablebrowse.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for StableBrowse. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for stablebrowse.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for StableBrowse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stablebrowse-com/index.md) ## Sources - [Ora score page for stablebrowse.com](https://ora.ai/score/stablebrowse.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/leaderboard) - [Where StableBrowse was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [StableBrowse website](https://stablebrowse.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Stably MCP server | Agent MCP Directory" description: "Does Stably have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/stably-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Stably MCP server | Agent MCP Directory > Does Stably have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/stably-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Stably: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Stably (stably.ai), so the connector had nothing to connect to. Ora's cached score for stably.ai is 79, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Stably (registry title: stably.ai) | | --- | --- | | Domain | stably.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 79, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for stably.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Stably. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for stably.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Stably. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stably-ai/index.md) ## Sources - [Ora score page for stably.ai](https://ora.ai/score/stably.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Stably was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Stably website](https://stably.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "StackBlitz MCP server | Agent MCP Directory" description: "Does StackBlitz have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/stackblitz-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # StackBlitz MCP server | Agent MCP Directory > Does StackBlitz have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/stackblitz-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # StackBlitz: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for StackBlitz (stackblitz.com), so the connector had nothing to connect to. Ora's cached score for stackblitz.com is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | StackBlitz | | --- | --- | | Domain | stackblitz.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for stackblitz.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for StackBlitz. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for stackblitz.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for StackBlitz. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stackblitz-com/index.md) ## Sources - [Ora score page for stackblitz.com](https://ora.ai/score/stackblitz.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/leaderboard) - [Where StackBlitz was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [StackBlitz website](https://stackblitz.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "StackOverflow MCP server | Agent MCP Directory" description: "StackOverflow: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/stackoverflow-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # StackOverflow MCP server | Agent MCP Directory > StackOverflow: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/stackoverflow-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # StackOverflow: MCP server, CLI and agent surfaces Not counted. The endpoint listed for StackOverflow at mcp.stackoverflow.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | StackOverflow | | --- | --- | | Domain | stackoverflow.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Credential wall | | Tranco rank | 548 on the list of 4 November 2026 | | Ora score | 23, grade F; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for stackoverflow.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.stackoverflow.com | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 635 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:54Z https://mcp.stackoverflow.com sent initialize result auth-required-no-oauth (HTTP 401) 620 ms - 20:01:30Z https://mcp.stackoverflow.com sent initialize result auth-required-no-oauth (HTTP 401) 635 ms ## Authentication | Auth type | API key | | --- | --- | | What the challenge said | Bearer | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.stackoverflow.com` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for StackOverflow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.stackoverflow.mcp/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stackoverflow-com/index.md) ## Sources - [Ora score page for stackoverflow.com](https://ora.ai/score/stackoverflow.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [Where StackOverflow was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=stackoverflow), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Stackup MCP server | Agent MCP Directory" description: "Does Stackup have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/stackup-fi site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Stackup MCP server | Agent MCP Directory > Does Stackup have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/stackup-fi Site: Agent MCP Directory Last reviewed: 2026-11-05 # Stackup: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Stackup (stackup.fi), so the connector had nothing to connect to. Ora's cached score for stackup.fi is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Stackup (registry title: stackup.fi) | | --- | --- | | Domain | stackup.fi | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for stackup.fi, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Stackup. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for stackup.fi, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Stackup. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stackup-fi/index.md) ## Sources - [Ora score page for stackup.fi](https://ora.ai/score/stackup.fi?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Stackup was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Stackup website](https://stackup.fi), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "stagewise MCP server | Agent MCP Directory" description: "Does stagewise have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/stagewise-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # stagewise MCP server | Agent MCP Directory > Does stagewise have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/stagewise-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # stagewise: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for stagewise (stagewise.io), so the connector had nothing to connect to. Ora's cached score for stagewise.io is 71, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | stagewise (registry title: stagewise.io) | | --- | --- | | Domain | stagewise.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 71, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for stagewise.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for stagewise. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for stagewise.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for stagewise. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stagewise-io/index.md) ## Sources - [Ora score page for stagewise.io](https://ora.ai/score/stagewise.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/leaderboard) - [Where stagewise was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [stagewise website](https://stagewise.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Standard Notes MCP server | Agent MCP Directory" description: "Does Standard Notes have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/standardnotes-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Standard Notes MCP server | Agent MCP Directory > Does Standard Notes have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/standardnotes-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Standard Notes: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Standard Notes (standardnotes.com), so the connector had nothing to connect to. Ora's cached score for standardnotes.com is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Standard Notes (registry title: standardnotes.com) | | --- | --- | | Domain | standardnotes.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for standardnotes.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Standard Notes. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for standardnotes.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Standard Notes. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/standardnotes-com/index.md) ## Sources - [Ora score page for standardnotes.com](https://ora.ai/score/standardnotes.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Standard Notes was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Standard Notes website](https://standardnotes.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "StarSling MCP server | Agent MCP Directory" description: "Does StarSling have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/starsling-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # StarSling MCP server | Agent MCP Directory > Does StarSling have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/starsling-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # StarSling: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for StarSling (starsling.dev), so the connector had nothing to connect to. Ora's cached score for starsling.dev is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | StarSling (registry title: starsling.dev) | | --- | --- | | Domain | starsling.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for starsling.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for StarSling. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for starsling.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for StarSling. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/starsling-dev/index.md) ## Sources - [Ora score page for starsling.dev](https://ora.ai/score/starsling.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/leaderboard) - [Where StarSling was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [StarSling website](https://starsling.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Startup Ignition MCP server | Agent MCP Directory" description: "Startup Ignition: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/startupignition-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Startup Ignition MCP server | Agent MCP Directory > Startup Ignition: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/startupignition-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Startup Ignition: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Startup Ignition at mcp.startupignition.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Startup Ignition (registry title: Startup Ignition ToolSuite) | | --- | --- | | Domain | startupignition.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for startupignition.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.startupignition.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 160 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:41Z https://mcp.startupignition.com/mcp sent initialize result auth-required (HTTP 401) 479 ms - 20:04:40Z https://mcp.startupignition.com/mcp sent initialize result auth-required (HTTP 401) 160 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.startupignition.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.startupignition.com | | Authorization server metadata | mcp.startupignition.com | | Registration endpoint | https://mcp.startupignition.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.startupignition.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.startupignition.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.startupignition.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Startup Ignition. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.startupignition/toolsuite | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/startupignition-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=startupignition), read 4 November 2026 - [Startup Ignition website](https://startupignition.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Statamic MCP server | Agent MCP Directory" description: "Does Statamic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/statamic-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Statamic MCP server | Agent MCP Directory > Does Statamic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/statamic-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Statamic: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Statamic (statamic.com), so the connector had nothing to connect to. Ora's cached score for statamic.com is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Statamic (registry title: statamic.com) | | --- | --- | | Domain | statamic.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for statamic.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Statamic. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for statamic.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Statamic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/statamic-com/index.md) ## Sources - [Ora score page for statamic.com](https://ora.ai/score/statamic.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/leaderboard) - [Where Statamic was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Statamic website](https://statamic.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Statsig MCP server | Agent MCP Directory" description: "Statsig: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/statsig-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Statsig MCP server | Agent MCP Directory > Statsig: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/statsig-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Statsig: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Statsig at api.statsig.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Statsig (registry title: statsig.com) | | --- | --- | | Domain | statsig.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,700 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for statsig.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.statsig.com/v1/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 336 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:05Z https://api.statsig.com/v1/mcp sent initialize result auth-required (HTTP 401) 315 ms - 20:01:42Z https://api.statsig.com/v1/mcp sent initialize result auth-required (HTTP 401) 336 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="statsig", resource="https://api.statsig.com/v1/mcp", resource_metadata="https://api.statsig.com/.well-known/oauth-protected-resource/v1/mcp" | | Protected resource metadata | api.statsig.com | | Authorization server metadata | api.statsig.com | | Registration endpoint | https://api.statsig.com/v1/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.statsig.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.statsig.com/.well-known/oauth-protected-resource/v1/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.statsig.com/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Statsig. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.statsig/statsig-mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/statsig-com/index.md) ## Sources - [Ora score page for statsig.com](https://ora.ai/score/statsig.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/score) - [Where Statsig was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.statsig%2Fstatsig-mcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=statsig), read 4 November 2026 - [Statsig website](https://statsig.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP status credential wall: 19 companies | Agent MCP Directory" description: "19 companies with MCP status credential wall. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/credential-wall site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP status credential wall: 19 companies | Agent MCP Directory > 19 companies with MCP status credential wall. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/credential-wall Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: credential wall 19 companies have the status credential wall. The endpoint asked for credentials and published no OAuth metadata, so it cannot be told apart from any other protected API. Not counted as an MCP server. Rows run from Appcircle to testRigor. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Appcircle appcircle.io | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Bitculator bitculator.com | Credential wall API key | – | | – | not read | 2026-11-04 | | Cavyro cavyro.com | Credential wall API key | – | 73 B | yes | not read | 2026-11-04 | | Contentstack contentstack.com | Credential wall API key | – | 67 C | – | no | 2026-11-04 | | Devtron devtron.ai | Credential wall API key | – | 48 C | – | no | 2026-11-04 | | Hookstep hookstep.in | Credential wall API key | – | | – | not read | 2026-11-04 | | Klavis klavis.ai | Credential wall API key | – | 71 B | – | no | 2026-11-04 | | Mezmo mezmo.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | Netdata netdata.cloud | Credential wall API key | – | | – | not read | 2026-11-04 | | Northflank northflank.com | Credential wall API key | – | 53 C | – | no | 2026-11-04 | | Oids tryoids.com | Credential wall API key | – | | – | not read | 2026-11-04 | | OneSchema oneschema.co | Credential wall API key | – | 56 C | – | no | 2026-11-04 | | PageProofer pageproofer.com | Credential wall API key | – | | – | not read | 2026-11-04 | | PrintFriendly printfriendly.com | Credential wall API key | – | | yes | not read | 2026-11-04 | | Screenshot Scout screenshotscout.com | Credential wall API key | – | | – | not read | 2026-11-04 | | SmartGate smartgate.network | Credential wall API key | – | | – | not read | 2026-11-04 | | Sonatype sonatype.com | Credential wall API key | – | 65 C | – | no | 2026-11-04 | | StackOverflow stackoverflow.com | Credential wall API key | – | 23 F | – | no | 2026-11-04 | | testRigor testrigor.com | Credential wall API key | – | 56 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/credential-wall/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP status no answer: 47 companies | Agent MCP Directory" description: "47 companies with MCP status no answer. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/no-answer site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP status no answer: 47 companies | Agent MCP Directory > 47 companies with MCP status no answer. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/no-answer Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: no answer 47 companies have the status no answer. A source lists an endpoint, but it did not answer an MCP handshake on the day. Not counted. Rows run from Abstra to ZeroEntropy. 0 of them have a CLI on record. Checked on 4 November 2026. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Abstra abstra.io | No answer | – | 55 C | – | no | 2026-11-04 | | Better Stack betterstack.com | No answer | – | 59 C | – | no | 2026-11-04 | | BittleBits bittlebits.ai | No answer | – | | – | not read | 2026-11-04 | | Bolna AI bolna.ai | No answer | – | 63 C | – | no | 2026-11-04 | | Chonkie chonkie.ai | No answer | – | 43 D | – | no | 2026-11-04 | | Clicon clicon.app | No answer | – | | – | not read | 2026-11-04 | | Continue continue.dev | No answer | – | 54 C | – | no | 2026-11-04 | | CORE getcore.me | No answer | – | 55 C | – | no | 2026-11-04 | | CustomGPT.ai customgpt.ai | No answer | – | | – | not read | 2026-11-04 | | Dappier dappier.com | No answer | – | | – | not read | 2026-11-04 | | Dedalus Labs dedaluslabs.ai | No answer | – | 85 B | – | no | 2026-11-04 | | Docker docker.com | No answer | – | 69 C | – | no | 2026-11-04 | | Elementary Data elementary-data.com | No answer | – | 56 C | – | no | 2026-11-04 | | Ellipsis ellipsis.dev | No answer | – | 69 C | – | no | 2026-11-04 | | Firmament getfirmament.com | No answer | – | | – | not read | 2026-11-04 | | Glideapps glideapps.com | No answer | – | 64 C | – | no | 2026-11-04 | | Grafbase grafbase.com | No answer | – | 45 D | – | no | 2026-11-04 | | hardoz hardoz.eu.cc | No answer | – | | – | not read | 2026-11-04 | | Infracost infracost.io | No answer | – | 50 C | – | no | 2026-11-04 | | Inkeep inkeep.com | No answer | – | 71 B | – | no | 2026-11-04 | | Kollektiv thekollektiv.ai | No answer | – | | – | not read | 2026-11-04 | | LaunchDarkly launchdarkly.com | No answer | – | 69 C | – | no | 2026-11-04 | | Llmtxt llmtxt.dev | No answer | – | | – | not read | 2026-11-04 | | Malware Patrol malwarepatrol.net | No answer | – | | – | not read | 2026-11-04 | | ManageEngine manageengine.com | No answer | – | 62 C | – | no | 2026-11-04 | | Mercado Libre mercadolibre.com | No answer | – | 40 D | – | no | 2026-11-04 | | Morph morphllm.com | No answer | – | 82 B | – | no | 2026-11-04 | | Morphik morphik.ai | No answer | – | 70 B | – | no | 2026-11-04 | | Nameshift nameshift.com | No answer | – | | – | no | 2026-11-04 | | Needle needle-ai.com | No answer | – | | – | not read | 2026-11-04 | | Nuxt nuxt.com | No answer | – | 79 B | yes | no | 2026-11-04 | | OpenMesh openmesh.dev | No answer | – | | – | not read | 2026-11-04 | | Plane plane.so | No answer | – | 78 B | yes | no | 2026-11-04 | | Redis redis.io | No answer | – | 62 C | – | no | 2026-11-04 | | Replit replit.com | No answer | – | 73 B | – | no | 2026-11-04 | | Runautomat runautomat.com | No answer | – | 65 C | – | no | 2026-11-04 | | Servicebricks servicebricks.com | No answer | – | | – | not read | 2026-11-04 | | Signadot signadot.com | No answer | – | 68 C | – | no | 2026-11-04 | | Svix svix.com | No answer | – | 69 C | – | no | 2026-11-04 | | Theneo theneo.io | No answer | – | 67 C | – | no | 2026-11-04 | | TickTick ticktick.com | No answer | – | 61 C | – | no | 2026-11-04 | | Waldium waldium.com | No answer | – | 37 D | – | no | 2026-11-04 | | WayStation waystation.ai | No answer | – | | – | not read | 2026-11-04 | | Workamajig workamajig.com | No answer | – | 62 C | – | no | 2026-11-04 | | Workato workato.com | No answer | – | 64 C | – | no | 2026-11-04 | | Wrike wrike.com | No answer | – | 66 C | – | no | 2026-11-04 | | ZeroEntropy zeroentropy.dev | No answer | – | 73 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/no-answer/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP status no tools listed: 2 companies | Agent MCP Directory" description: "2 companies with MCP status no tools listed. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/no-tools site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP status no tools listed: 2 companies | Agent MCP Directory > 2 companies with MCP status no tools listed. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/no-tools Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: no tools listed 2 companies have the status no tools listed. The endpoint completed the handshake and listed no tools. Not counted. Rows run from Award Travel Finder to Storyblok. 0 of them have a CLI on record. Checked on 4 November 2026. ## Rows | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Award Travel Finder awardtravelfinder.com | No tools listed | – | | – | not read | 2026-11-04 | | Storyblok storyblok.com | No tools listed | – | 67 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/no-tools/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP status none found: 472 companies | Agent MCP Directory" description: "472 companies with MCP status none found. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/none-found site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP status none found: 472 companies | Agent MCP Directory > 472 companies with MCP status none found. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/none-found Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: none found 472 companies have the status none found. No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to. This page lists rows 1 to 100, from a0.dev to CoreWeave. 10 of them have a CLI on record. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | a0.dev a0.dev | None found | – | 51 C | – | no | 2026-11-04 | | Acquia acquia.com | None found | – | 69 C | – | no | 2026-11-04 | | Activeloop activeloop.ai | None found | – | 47 D | – | no | 2026-11-04 | | Actual AI actual.ai | None found | – | 81 B | yes | no | 2026-11-04 | | Adalo adalo.com | None found | – | 69 C | – | no | 2026-11-04 | | Aden adenhq.com | None found | – | 70 B | – | no | 2026-11-04 | | AfterQuery afterquery.com | None found | – | 55 C | – | no | 2026-11-04 | | AgentHub agenthublabs.com | None found | – | 40 D | – | no | 2026-11-04 | | Aider aider.chat | None found | – | 41 D | – | no | 2026-11-04 | | Airbrake airbrake.io | None found | – | 49 C | – | not read | 2026-11-04 | | Aiven aiven.io | None found | – | 76 B | – | no | 2026-11-04 | | Alidns alidns.com | None found | – | | – | no | 2026-11-04 | | Amika amika.dev | None found | – | 55 C | – | no | 2026-11-04 | | Anchore anchore.com | None found | – | 46 D | – | no | 2026-11-04 | | Anthropic anthropic.com | None found | @anthropic-ai/claude-code | 71 B | – | no | 2026-11-04 | | Anytype anytype.io | None found | – | 40 D | – | no | 2026-11-04 | | Apoxy apoxy.dev | None found | – | 37 D | – | no | 2026-11-04 | | Appian appian.com | None found | – | 51 C | – | no | 2026-11-04 | | AppSignal appsignal.com | None found | – | 69 C | – | no | 2026-11-04 | | AppVeyor appveyor.com | None found | – | 40 D | – | no | 2026-11-04 | | Aptible aptible.com | None found | – | 63 C | – | no | 2026-11-04 | | Ara ara.so | None found | – | 53 C | – | no | 2026-11-04 | | Archbee archbee.com | None found | – | 63 C | – | no | 2026-11-04 | | Archil archil.com | None found | – | 62 C | – | no | 2026-11-04 | | Ardent tryardent.com | None found | – | 71 B | – | no | 2026-11-04 | | Arga Labs argalabs.com | None found | – | 65 C | – | no | 2026-11-04 | | Arthur arthur.ai | None found | – | 60 C | – | no | 2026-11-04 | | Artillery artillery.io | None found | – | 55 C | – | no | 2026-11-04 | | Assembla assembla.com | None found | – | 52 C | – | no | 2026-11-04 | | assistant-ui assistant-ui.com | None found | – | 79 B | – | no | 2026-11-04 | | Automattic automattic.com | None found | – | 53 C | – | no | 2026-11-04 | | Auvik auvik.com | None found | – | 54 C | – | no | 2026-11-04 | | Aviator aviator.co | None found | – | 55 C | – | no | 2026-11-04 | | Axolo axolo.co | None found | – | 41 D | – | no | 2026-11-04 | | Azure azure.com | None found | – | 58 C | – | no | 2026-11-04 | | Backendless backendless.com | None found | – | 48 C | – | no | 2026-11-04 | | Base44 base44.com | None found | – | 86 A | – | no | 2026-11-04 | | Beam beam.cloud | None found | – | 74 B | – | no | 2026-11-04 | | Bear bear.app | None found | – | 40 D | – | no | 2026-11-04 | | Benchspan benchspan.com | None found | – | 61 C | – | no | 2026-11-04 | | Bento bentoml.com | None found | – | 41 D | – | no | 2026-11-04 | | Betteruptime betteruptime.com | None found | – | 48 C | – | no | 2026-11-04 | | BigPanda bigpanda.io | None found | – | 54 C | – | no | 2026-11-04 | | BigTime bigtime.net | None found | – | 41 D | – | no | 2026-11-04 | | Bitbucket bitbucket.org | None found | – | 34 D | – | no | 2026-11-04 | | Blacksmith blacksmith.sh | None found | – | 42 D | – | no | 2026-11-04 | | Bland bland.com | None found | – | 60 C | yes | no | 2026-11-04 | | Blaxel blaxel.ai | None found | – | 80 B | – | no | 2026-11-04 | | Blueprism blueprism.com | None found | – | 59 C | – | no | 2026-11-04 | | Bolt bolt.new | None found | – | 65 C | – | no | 2026-11-04 | | Botcity botcity.dev | None found | – | 65 C | – | not read | 2026-11-04 | | Brainboard brainboard.co | None found | – | 65 C | – | no | 2026-11-04 | | Browserbase browserbase.com | None found | – | 84 B | – | no | 2026-11-04 | | Browserbook browserbook.com | None found | – | 40 D | – | no | 2026-11-04 | | Bucket bucket.co | None found | – | 50 C | – | no | 2026-11-04 | | BugSnag bugsnag.com | None found | – | 52 C | – | no | 2026-11-04 | | BuildBuddy buildbuddy.io | None found | – | 44 D | – | no | 2026-11-04 | | Builder.io builder.io | None found | – | 45 D | – | no | 2026-11-04 | | BuildJet buildjet.com | None found | – | 45 D | – | no | 2026-11-04 | | Buildwithglide buildwithglide.com | None found | – | 45 D | – | no | 2026-11-04 | | Bun bun.sh | None found | – | 49 C | – | no | 2026-11-04 | | Carrd carrd.co | None found | – | 42 D | – | no | 2026-11-04 | | Castari castari.com | None found | – | 61 C | – | no | 2026-11-04 | | Cedana cedana.ai | None found | – | 34 D | – | no | 2026-11-04 | | Cekura cekura.ai | None found | – | 82 B | – | no | 2026-11-04 | | Chamber usechamber.io | None found | – | 68 C | – | no | 2026-11-04 | | Checkmarx checkmarx.com | None found | – | 61 C | – | no | 2026-11-04 | | Chronosphere chronosphere.io | None found | – | 67 C | – | no | 2026-11-04 | | Cisco cisco.com | None found | – | 33 D | – | no | 2026-11-04 | | Clarm clarm.com | None found | – | 69 C | yes | no | 2026-11-04 | | Cleanlab cleanlab.ai | None found | – | 34 D | – | no | 2026-11-04 | | Clidey clidey.com | None found | – | 38 D | – | no | 2026-11-04 | | Cline cline.bot | None found | – | 77 B | – | no | 2026-11-04 | | Clockify™ clockify.me | None found | – | 64 C | – | no | 2026-11-04 | | CloudBees cloudbees.com | None found | – | 68 C | – | no | 2026-11-04 | | Cloudthread cloudthread.io | None found | – | 41 D | – | not read | 2026-11-04 | | Clubhouse clubhouse.io | None found | – | 62 C | yes | no | 2026-11-04 | | cmux cmux.com | None found | – | 43 D | – | no | 2026-11-04 | | Coasts coasts.dev | None found | – | 40 D | – | no | 2026-11-04 | | CockroachDB cockroachlabs.com | None found | – | 69 C | – | no | 2026-11-04 | | Code Climate codeclimate.com | None found | – | 50 C | – | no | 2026-11-04 | | Codeanywhere codeanywhere.com | None found | – | 40 D | – | no | 2026-11-04 | | Codeberg.org codeberg.org | None found | – | 54 C | – | no | 2026-11-04 | | Codecov codecov.io | None found | – | 68 C | – | not read | 2026-11-04 | | Codefresh codefresh.io | None found | – | 50 C | – | no | 2026-11-04 | | Codeium codeium.com | None found | – | 49 C | – | no | 2026-11-04 | | Codemagic codemagic.io | None found | – | 58 C | – | no | 2026-11-04 | | Coder coder.com | None found | – | 70 B | – | no | 2026-11-04 | | CodeSandbox codesandbox.io | None found | – | 44 D | – | no | 2026-11-04 | | Codev co.dev | None found | – | 50 C | – | no | 2026-11-04 | | Composio composio.dev | None found | composio | 83 B | – | no | 2026-11-04 | | Compresr compresr.ai | None found | – | 49 C | yes | no | 2026-11-04 | | Compyle compyle.ai | None found | – | 55 C | – | no | 2026-11-04 | | Concourse CI concourse-ci.org | None found | – | 41 D | – | no | 2026-11-04 | | Conductor conductor.build | None found | – | 72 B | – | no | 2026-11-04 | | Confluent confluent.io | None found | – | 78 B | – | no | 2026-11-04 | | Convoy getconvoy.io | None found | – | 59 C | – | no | 2026-11-04 | | Coralogix coralogix.com | None found | – | 79 B | yes | no | 2026-11-04 | | CoreMedia coremedia.com | None found | – | 57 C | – | no | 2026-11-04 | | CoreWeave coreweave.com | None found | – | 68 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/none-found/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "None found, page 2 | Agent MCP Directory" description: "472 companies with MCP status none found. Not counted as having an MCP server. Page 2 of 5. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/none-found/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # None found, page 2 | Agent MCP Directory > 472 companies with MCP status none found. Not counted as having an MCP server. Page 2 of 5. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/none-found/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: none found, page 2 472 companies have the status none found. No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to. This page lists rows 101 to 200, from Cosine to Keyframe Labs. 10 of them have a CLI on record. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Cosine cosine.sh | None found | – | 37 D | – | no | 2026-11-04 | | Cosmic cosmicjs.com | None found | – | 75 B | yes | no | 2026-11-04 | | Craft CMS craftcms.com | None found | – | 44 D | – | no | 2026-11-04 | | CTGT ctgt.ai | None found | – | 46 D | – | no | 2026-11-04 | | Cursor cursor.com | None found | – | 74 B | – | no | 2026-11-04 | | Cyberdesk cyberdesk.io | None found | – | 74 B | – | no | 2026-11-04 | | Daft daft.ai | None found | – | 45 D | – | no | 2026-11-04 | | Dagger dagger.io | None found | – | 48 C | – | no | 2026-11-04 | | Dailybot dailybot.com | None found | – | 76 B | yes | no | 2026-11-04 | | dari.dev dari.dev | None found | – | 42 D | – | no | 2026-11-04 | | Datasaur datasaur.ai | None found | – | 69 C | – | no | 2026-11-04 | | Deci deci.ai | None found | – | 44 D | – | no | 2026-11-04 | | Deepnote deepnote.com | None found | – | 65 C | – | no | 2026-11-04 | | Deno deno.com | None found | deno | 65 C | – | no | 2026-11-04 | | Designbase designbase.com | None found | – | 55 C | – | no | 2026-11-04 | | DeskCrew deskcrew.io | None found | – | | yes | not read | 2026-11-04 | | Devo devo.com | None found | – | 43 D | – | no | 2026-11-04 | | DevZero devzero.io | None found | – | 58 C | – | no | 2026-11-04 | | Directus directus.io | None found | – | 47 D | – | no | 2026-11-04 | | Dittowords dittowords.com | None found | – | 67 C | – | no | 2026-11-04 | | Docket docketqa.com | None found | – | 58 C | – | no | 2026-11-04 | | Dojah dojah.io | None found | – | 77 B | – | no | 2026-11-04 | | Dorik dorik.com | None found | – | 35 D | – | no | 2026-11-04 | | Double double.bot | None found | – | 54 C | – | no | 2026-11-04 | | DrDroid drdroid.io | None found | – | 61 C | – | no | 2026-11-04 | | Duffel duffel.com | None found | – | 65 C | – | no | 2026-11-04 | | Dynatrace dynatrace.com | None found | – | 82 B | – | no | 2026-11-04 | | Elastic elastic.co | None found | – | 59 C | – | no | 2026-11-04 | | Electroneek electroneek.com | None found | – | 68 C | – | no | 2026-11-04 | | Env0 env0.com | None found | – | 73 B | – | no | 2026-11-04 | | Epsilla epsilla.com | None found | – | 57 C | – | no | 2026-11-04 | | Everhour everhour.com | None found | – | 68 C | – | no | 2026-11-04 | | Evidently AI evidentlyai.com | None found | – | 58 C | – | no | 2026-11-04 | | FastJVM fastjvm.com | None found | – | 43 D | – | no | 2026-11-04 | | Fastly fastly.com | None found | – | 70 B | – | no | 2026-11-04 | | Fastmail fastmail.com | None found | – | 37 D | – | no | 2026-11-04 | | Fastshot fastshot.ai | None found | – | 66 C | – | no | 2026-11-04 | | Fiddler AI fiddler.ai | None found | – | 68 C | – | no | 2026-11-04 | | Firebase firebase.google.com | None found | firebase-tools | 56 C | – | not read | 2026-11-04 | | FireHydrant firehydrant.com | None found | – | 49 C | – | no | 2026-11-04 | | Flightcontrol flightcontrol.dev | None found | – | 46 D | – | no | 2026-11-04 | | Flowtel flowtel.ai | None found | – | 55 C | – | no | 2026-11-04 | | FlutterFlow flutterflow.io | None found | – | 53 C | – | no | 2026-11-04 | | Flux fluxcd.io | None found | – | 38 D | – | no | 2026-11-04 | | Font Awesome fontawesome.com | None found | – | 56 C | – | no | 2026-11-04 | | Galileo AI galileo.ai | None found | – | 78 B | – | no | 2026-11-04 | | Getdecipher getdecipher.com | None found | – | 45 D | – | no | 2026-11-04 | | Getmocha getmocha.com | None found | – | 46 D | – | not read | 2026-11-04 | | Ghost ghost.org | None found | – | 70 B | – | no | 2026-11-04 | | Gitea gitea.com | None found | – | 55 C | – | no | 2026-11-04 | | GitOps gitops.tech | None found | – | 37 D | – | no | 2026-11-04 | | Gitpod gitpod.io | None found | – | 41 D | – | not read | 2026-11-04 | | Glean glean.com | None found | – | 72 B | – | no | 2026-11-04 | | Glide glide.app | None found | – | 50 C | – | no | 2026-11-04 | | Google Cloud cloud.google.com | None found | – | 51 C | – | no | 2026-11-04 | | Google Gemini gemini.google.com | None found | @google/gemini-cli | 43 D | – | not read | 2026-11-04 | | Grav getgrav.org | None found | – | 68 C | – | no | 2026-11-04 | | Graylog graylog.org | None found | – | 45 D | – | no | 2026-11-04 | | Greptile greptile.com | None found | – | 77 B | – | no | 2026-11-04 | | Gumroad gumroad.com | None found | – | 69 C | – | no | 2026-11-04 | | Habitica habitica.com | None found | – | 34 D | – | no | 2026-11-04 | | HackerRank hackerrank.com | None found | – | 69 C | – | no | 2026-11-04 | | HARVEST.com harvest.com | None found | – | 39 D | – | no | 2026-11-04 | | HashiCorp hashicorp.com | None found | – | 60 C | – | no | 2026-11-04 | | Hasura hasura.io | None found | – | 51 C | – | no | 2026-11-04 | | Hatchet hatchet.run | None found | – | 53 C | – | no | 2026-11-04 | | Haystackeditor haystackeditor.com | None found | – | 44 D | – | no | 2026-11-04 | | Healthline healthline.com | None found | – | 75 B | – | no | 2026-11-04 | | HeroUI heroui.com | None found | – | 81 B | yes | no | 2026-11-04 | | HetrixTools hetrixtools.com | None found | – | 59 C | – | no | 2026-11-04 | | Hetzner hetzner.com | None found | – | 50 C | – | no | 2026-11-04 | | Hiro hiro.so | None found | – | 49 C | – | no | 2026-11-04 | | Hive hive.com | None found | – | 66 C | – | no | 2026-11-04 | | Honeybadger honeybadger.io | None found | – | 72 B | – | not read | 2026-11-04 | | hoop.dev hoop.dev | None found | – | 41 D | – | no | 2026-11-04 | | Hygraph hygraph.com | None found | – | 69 C | – | no | 2026-11-04 | | Hyperbeam hyperbeam.com | None found | – | 57 C | – | no | 2026-11-04 | | Hyperspell hyperspell.com | None found | – | 75 B | – | no | 2026-11-04 | | Imgix imgix.com | None found | – | 67 C | – | no | 2026-11-04 | | IncidentFox incidentfox.ai | None found | – | 67 C | – | no | 2026-11-04 | | Inconvo inconvo.com | None found | – | 60 C | – | no | 2026-11-04 | | Infer infer.so | None found | – | 37 D | – | no | 2026-11-04 | | Infield infield.ai | None found | – | 48 C | – | no | 2026-11-04 | | Infra infra.new | None found | – | 60 C | – | no | 2026-11-04 | | Integuru integuru.ai | None found | – | 47 D | – | no | 2026-11-04 | | Interfaze interfaze.ai | None found | – | 66 C | yes | no | 2026-11-04 | | Intuned intunedhq.com | None found | – | 63 C | – | no | 2026-11-04 | | IOMETE iomete.com | None found | – | 60 C | – | no | 2026-11-04 | | ix ix.dev | None found | – | 39 D | – | no | 2026-11-04 | | Jet Admin jetadmin.io | None found | – | 65 C | – | no | 2026-11-04 | | JetBrains jetbrains.com | None found | – | 62 C | – | no | 2026-11-04 | | JFrog jfrog.com | None found | – | 70 B | – | no | 2026-11-04 | | K9s k9scli.io | None found | – | 42 D | – | no | 2026-11-04 | | Kanbanize kanbanize.com | None found | – | 43 D | – | no | 2026-11-04 | | Karate Labs karatelabs.io | None found | – | 63 C | – | no | 2026-11-04 | | Kashikoi getkashikoi.com | None found | – | 39 D | – | no | 2026-11-04 | | Keep(卡路里科技)-自律给我自由 google.keep.com | None found | – | 52 C | – | no | 2026-11-04 | | Keet trykeet.com | None found | – | 53 C | – | no | 2026-11-04 | | KERNEL kernel.sh | None found | – | 86 A | – | no | 2026-11-04 | | Keyframe Labs keyframelabs.com | None found | – | 65 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/none-found/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "None found, page 3 | Agent MCP Directory" description: "472 companies with MCP status none found. Not counted as having an MCP server. Page 3 of 5. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/none-found/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # None found, page 3 | Agent MCP Directory > 472 companies with MCP status none found. Not counted as having an MCP server. Page 3 of 5. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/none-found/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: none found, page 3 472 companies have the status none found. No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to. This page lists rows 201 to 300, from KeystoneJS to Porter. 10 of them have a CLI on record. ## Rows 201 to 300 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | KeystoneJS keystonejs.com | None found | – | 55 C | – | no | 2026-11-04 | | Kili Technology kili-technology.com | None found | – | 59 C | – | no | 2026-11-04 | | Kissflow kissflow.com | None found | – | 58 C | – | no | 2026-11-04 | | Kitemaker kitemaker.co | None found | – | 34 D | – | no | 2026-11-04 | | Koyeb koyeb.com | None found | – | 61 C | – | no | 2026-11-04 | | Kubecost kubecost.com | None found | – | 43 D | – | no | 2026-11-04 | | Lambda lambdalabs.com | None found | – | 44 D | – | no | 2026-11-04 | | Laminar laminar.sh | None found | – | 41 D | – | no | 2026-11-04 | | Lark getlark.ai | None found | – | 56 C | – | no | 2026-11-04 | | Last9 last9.io | None found | – | 73 B | – | no | 2026-11-04 | | Leantime leantime.io | None found | – | 52 C | – | no | 2026-11-04 | | Lemma uselemma.ai | None found | – | 66 C | – | no | 2026-11-04 | | Lightsprint lightsprint.ai | None found | – | 62 C | – | no | 2026-11-04 | | Lightstep lightstep.com | None found | – | 42 D | – | no | 2026-11-04 | | Lilac getlilac.com | None found | – | 67 C | – | no | 2026-11-04 | | Linode linode.com | None found | – | 53 C | – | no | 2026-11-04 | | LiteLLM litellm.ai | None found | – | 73 B | – | no | 2026-11-04 | | Llmdata llmdata.com | None found | – | 35 D | – | no | 2026-11-04 | | Loft loft.sh | None found | – | 53 C | – | no | 2026-11-04 | | Loggly loggly.com | None found | – | 52 C | – | no | 2026-11-04 | | LogicMonitor logicmonitor.com | None found | – | 46 D | – | no | 2026-11-04 | | Logseq logseq.com | None found | – | 38 D | – | no | 2026-11-04 | | Logz.io logz.io | None found | – | 58 C | – | no | 2026-11-04 | | Lotas AI lotas.ai | None found | – | 51 C | – | no | 2026-11-04 | | Luciq luciq.ai | None found | – | 77 B | – | no | 2026-11-04 | | Luel luel.ai | None found | – | 58 C | – | no | 2026-11-04 | | MagicBell magicbell.com | None found | – | 47 D | – | no | 2026-11-04 | | Magnitude magnitude.dev | None found | – | 74 B | – | no | 2026-11-04 | | Maitai trymaitai.com | None found | – | 60 C | – | no | 2026-11-04 | | Manicule manicule.dev | None found | – | 33 D | – | no | 2026-11-04 | | Massdriver massdriver.cloud | None found | – | 63 C | – | no | 2026-11-04 | | Mastra mastra.ai | None found | – | 78 B | – | no | 2026-11-04 | | Maven trymaven.com | None found | – | 61 C | – | no | 2026-11-04 | | MedicalNewsToday medicalnewstoday.com | None found | – | 75 B | – | no | 2026-11-04 | | Mendix mendix.com | None found | – | 72 B | – | no | 2026-11-04 | | Mergent mergent.co | None found | – | 59 C | – | no | 2026-11-04 | | Mergify mergify.com | None found | – | 75 B | yes | no | 2026-11-04 | | Metoro metoro.io | None found | – | 43 D | – | no | 2026-11-04 | | Microsoft Azure azure.microsoft.com | None found | – | 51 C | – | no | 2026-11-04 | | Middleware middleware.io | None found | – | 52 C | – | no | 2026-11-04 | | Minded minded.com | None found | – | 58 C | – | no | 2026-11-04 | | Mindee mindee.com | None found | – | 73 B | – | no | 2026-11-04 | | Mindsdb mindsdb.com | None found | – | 51 C | – | not read | 2026-11-04 | | Mito trymito.io | None found | – | 49 C | – | no | 2026-11-04 | | mlop mlop.ai | None found | – | 38 D | – | no | 2026-11-04 | | MobileBoost mobileboost.io | None found | – | 66 C | – | no | 2026-11-04 | | Moda moda.dev | None found | – | 85 B | – | no | 2026-11-04 | | Modal modal.com | None found | modal | 63 C | – | no | 2026-11-04 | | Modelence modelence.com | None found | – | 60 C | – | no | 2026-11-04 | | MongoDB mongodb.com | None found | – | 78 B | – | no | 2026-11-04 | | Moogsoft moogsoft.com | None found | – | 41 D | – | no | 2026-11-04 | | Moss moss.dev | None found | – | 81 B | – | no | 2026-11-04 | | MovingLake movinglake.com | None found | – | 39 D | – | no | 2026-11-04 | | MuleSoft mulesoft.com | None found | – | 36 D | – | no | 2026-11-04 | | Naive usenaive.ai | None found | – | 48 C | – | no | 2026-11-04 | | Nebius nebius.com | None found | – | 73 B | – | no | 2026-11-04 | | Nevercode nevercode.io | None found | – | 47 D | – | no | 2026-11-04 | | Nginx nginx.com | None found | – | 47 D | – | no | 2026-11-04 | | Noloco noloco.io | None found | – | 55 C | – | no | 2026-11-04 | | Notion HQ notionhq.com | None found | – | 56 C | – | no | 2026-11-04 | | Notte notte.cc | None found | – | 89 A | – | no | 2026-11-04 | | Nuanced nuanced.dev | None found | – | 49 C | – | no | 2026-11-04 | | Nullstone nullstone.io | None found | – | 42 D | – | no | 2026-11-04 | | Nyckel nyckel.com | None found | – | 64 C | – | no | 2026-11-04 | | Octoml octoml.ai | None found | – | 38 D | – | no | 2026-11-04 | | Ocular useocular.com | None found | – | 59 C | – | no | 2026-11-04 | | Odigos odigos.io | None found | – | 69 C | – | no | 2026-11-04 | | Okteto okteto.com | None found | – | 58 C | – | no | 2026-11-04 | | Ollama ollama.com | None found | – | 65 C | – | no | 2026-11-04 | | Omnistrate omnistrate.com | None found | – | 56 C | – | no | 2026-11-04 | | Onenote onenote.com | None found | – | 43 D | – | no | 2026-11-04 | | OpenAI openai.com | None found | @openai/codex | 58 C | yes | no | 2026-11-04 | | Openfoundry openfoundry.ai | None found | – | 37 D | – | no | 2026-11-04 | | OpenReplay openreplay.com | None found | – | 66 C | – | no | 2026-11-04 | | Opentext opentext.com | None found | – | 30 D | – | no | 2026-11-04 | | Opsgenie opsgenie.com | None found | – | 60 C | – | no | 2026-11-04 | | Opslane opslane.com | None found | – | 47 D | – | no | 2026-11-04 | | Opsramp opsramp.com | None found | – | 43 D | – | not read | 2026-11-04 | | Orthogonal orthogonal.com | None found | – | 66 C | – | no | 2026-11-04 | | Osmosis osmosis.ai | None found | – | 69 C | – | no | 2026-11-04 | | OutSystems outsystems.com | None found | – | 63 C | – | no | 2026-11-04 | | OVHcloud ovhcloud.com | None found | – | 58 C | – | no | 2026-11-04 | | PagerDuty pagerduty.com | None found | – | 71 B | – | no | 2026-11-04 | | PagerTree pagertree.com | None found | – | 48 C | – | no | 2026-11-04 | | Palenca palenca.com | None found | – | 42 D | – | not read | 2026-11-04 | | Pangolin pangolin.net | None found | – | 66 C | – | no | 2026-11-04 | | ParadeDB paradedb.com | None found | – | 76 B | – | no | 2026-11-04 | | Paragon useparagon.com | None found | – | 70 B | – | no | 2026-11-04 | | Parea parea.ai | None found | – | 49 C | – | no | 2026-11-04 | | Parse parse.bot | None found | – | 65 C | – | no | 2026-11-04 | | Payload payloadcms.com | None found | – | 61 C | – | no | 2026-11-04 | | PgDog pgdog.dev | None found | – | 51 C | – | no | 2026-11-04 | | Pingram pingram.io | None found | – | 88 A | – | not read | 2026-11-04 | | Pipefy pipefy.com | None found | – | 70 B | – | no | 2026-11-04 | | Pipekit pipekit.io | None found | – | 58 C | – | no | 2026-11-04 | | PlanetScale planetscale.com | None found | – | 79 B | – | no | 2026-11-04 | | Platform.sh platform.sh | None found | – | 56 C | – | no | 2026-11-04 | | Ploomber ploomber.io | None found | – | 34 D | – | not read | 2026-11-04 | | Portainer portainer.io | None found | – | 70 B | – | no | 2026-11-04 | | Porter porter.run | None found | – | 73 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/none-found/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "None found, page 4 | Agent MCP Directory" description: "472 companies with MCP status none found. Not counted as having an MCP server. Page 4 of 5. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/none-found/page/4 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # None found, page 4 | Agent MCP Directory > 472 companies with MCP status none found. Not counted as having an MCP server. Page 4 of 5. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/none-found/page/4 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: none found, page 4 472 companies have the status none found. No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to. This page lists rows 301 to 400, from Praxim to Superb AI. 10 of them have a CLI on record. ## Rows 301 to 400 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Praxim praxim.ai | None found | – | 39 D | – | no | 2026-11-04 | | Processmaker processmaker.com | None found | – | 45 D | – | no | 2026-11-04 | | Projectx projectx.cloud | None found | – | 36 D | – | no | 2026-11-04 | | Promptless promptless.ai | None found | – | 60 C | – | no | 2026-11-04 | | Pulumi pulumi.com | None found | – | 80 B | – | no | 2026-11-04 | | Pylon pylonump.com | None found | – | 56 C | – | no | 2026-11-04 | | Quantstruct quantstruct.com | None found | – | 53 C | – | no | 2026-11-04 | | Queryvary queryvary.com | None found | – | 34 D | – | not read | 2026-11-04 | | Quill quill.co | None found | – | 39 D | – | no | 2026-11-04 | | Rainforest QA rainforestqa.com | None found | – | 70 B | – | no | 2026-11-04 | | Rancher rancher.com | None found | – | 40 D | – | no | 2026-11-04 | | Random Labs randomlabs.ai | None found | – | 45 D | – | no | 2026-11-04 | | Rapid7 rapid7.com | None found | – | 62 C | – | no | 2026-11-04 | | Readdle readdle.com | None found | – | 45 D | – | no | 2026-11-04 | | ReadMe readme.com | None found | – | 64 C | – | no | 2026-11-04 | | Recall.ai recall.ai | None found | – | 73 B | – | no | 2026-11-04 | | Refine refine.dev | None found | – | 46 D | – | no | 2026-11-04 | | Reflect reflect.app | None found | – | 46 D | yes | no | 2026-11-04 | | Reflex reflex.dev | None found | – | 67 C | – | no | 2026-11-04 | | Release release.com | None found | – | 52 C | – | no | 2026-11-04 | | Relvy relvy.ai | None found | – | 42 D | – | no | 2026-11-04 | | Replicas replicas.dev | None found | – | 78 B | – | no | 2026-11-04 | | Replo replo.app | None found | – | 64 C | – | no | 2026-11-04 | | Rescuetime rescuetime.com | None found | – | 56 C | – | no | 2026-11-04 | | Respan respan.ai | None found | – | 72 B | – | no | 2026-11-04 | | Retool retool.com | None found | – | 78 B | – | no | 2026-11-04 | | Rev rev.com | None found | – | 48 C | – | no | 2026-11-04 | | Revyl revyl.ai | None found | – | 48 C | – | no | 2026-11-04 | | Robocorp robocorp.com | None found | – | 41 D | – | no | 2026-11-04 | | Rollbar rollbar.com | None found | – | 69 C | – | no | 2026-11-04 | | Rownd rownd.ai | None found | – | 34 D | – | no | 2026-11-04 | | Rulebricks rulebricks.com | None found | – | 59 C | – | no | 2026-11-04 | | Run run.ai | None found | – | 37 D | – | not read | 2026-11-04 | | RunAnywhere runanywhere.ai | None found | – | 72 B | – | no | 2026-11-04 | | Runcascade runcascade.com | None found | – | 45 D | – | no | 2026-11-04 | | RunLocal runlocal.ai | None found | – | 44 D | – | no | 2026-11-04 | | Runtm runtm.com | None found | – | 66 C | – | no | 2026-11-04 | | Runtrellis runtrellis.com | None found | – | 40 D | – | no | 2026-11-04 | | Ryvn ryvn.ai | None found | – | 60 C | – | no | 2026-11-04 | | S2 s2.dev | None found | – | 61 C | – | no | 2026-11-04 | | Salesforce salesforce.com | None found | @salesforce/cli | 51 C | – | no | 2026-11-04 | | SAP sap.com | None found | – | 52 C | – | not read | 2026-11-04 | | Scaleway scaleway.com | None found | – | 69 C | – | no | 2026-11-04 | | Scalr scalr.com | None found | – | 56 C | – | no | 2026-11-04 | | Scalyr scalyr.com | None found | – | 40 D | – | no | 2026-11-04 | | Scape scape.app | None found | – | 36 D | – | no | 2026-11-04 | | Semaphore semaphoreci.com | None found | – | 49 C | – | no | 2026-11-04 | | SF Tensor sf-tensor.com | None found | – | 38 D | – | no | 2026-11-04 | | Shaped shaped.ai | None found | – | 47 D | – | no | 2026-11-04 | | Shogun shogun.com | None found | – | 52 C | – | no | 2026-11-04 | | Shopify shopify.com | None found | @shopify/cli | 72 B | – | no | 2026-11-04 | | Shuttle shuttle.dev | None found | – | 47 D | – | no | 2026-11-04 | | SID AI sid.ai | None found | – | 35 D | – | no | 2026-11-04 | | SigmaMind AI sigmamind.ai | None found | – | 74 B | – | no | 2026-11-04 | | SigNoz signoz.io | None found | – | 71 B | – | no | 2026-11-04 | | Simplenote simplenote.com | None found | – | 40 D | – | no | 2026-11-04 | | Simvoly simvoly.com | None found | – | 54 C | – | no | 2026-11-04 | | Site24x7 site24x7.com | None found | – | 53 C | – | no | 2026-11-04 | | Sitecore sitecore.com | None found | – | 61 C | – | no | 2026-11-04 | | Skyhook skyhook.io | None found | – | 72 B | – | no | 2026-11-04 | | Smobi smobi.com | None found | – | 52 C | – | no | 2026-11-04 | | smol machines smolmachines.com | None found | – | 80 B | yes | no | 2026-11-04 | | Snorkel AI snorkel.ai | None found | – | 43 D | – | no | 2026-11-04 | | Snowflake snowflake.com | None found | snowflake-cli | 66 C | – | no | 2026-11-04 | | Snyk snyk.io | None found | – | 79 B | – | no | 2026-11-04 | | Softr softr.io | None found | – | 67 C | – | no | 2026-11-04 | | Sonar sonarsource.com | None found | – | 71 B | – | no | 2026-11-04 | | Sourcebot sourcebot.dev | None found | – | 65 C | – | no | 2026-11-04 | | SourceForge sourceforge.net | None found | – | 69 C | – | no | 2026-11-04 | | Sourcegraph sourcegraph.com | None found | – | 55 C | – | no | 2026-11-04 | | sourcehut sourcehut.org | None found | – | 46 D | – | no | 2026-11-04 | | Spacelift spacelift.io | None found | – | 62 C | – | no | 2026-11-04 | | Specific specific.dev | None found | – | 67 C | – | no | 2026-11-04 | | Speedscale speedscale.com | None found | – | 66 C | – | no | 2026-11-04 | | Spike spike.app | None found | – | 34 D | – | no | 2026-11-04 | | Spinnaker spinnaker.io | None found | – | 39 D | – | no | 2026-11-04 | | Split.io split.io | None found | – | 60 C | – | no | 2026-11-04 | | Spurtest spurtest.com | None found | – | 56 C | – | no | 2026-11-04 | | Sre sre.ai | None found | – | 50 C | – | no | 2026-11-04 | | SST sst.dev | None found | – | 63 C | – | no | 2026-11-04 | | StableBrowse stablebrowse.com | None found | – | 54 C | – | no | 2026-11-04 | | Stably stably.ai | None found | – | 79 B | – | no | 2026-11-04 | | StackBlitz stackblitz.com | None found | – | 46 D | – | no | 2026-11-04 | | Stackup stackup.fi | None found | – | 37 D | – | no | 2026-11-04 | | stagewise stagewise.io | None found | – | 71 B | – | no | 2026-11-04 | | Standard Notes standardnotes.com | None found | – | 37 D | – | no | 2026-11-04 | | StarSling starsling.dev | None found | – | 50 C | – | no | 2026-11-04 | | Statamic statamic.com | None found | – | 38 D | – | no | 2026-11-04 | | StatusCake statuscake.com | None found | – | 53 C | – | no | 2026-11-04 | | StatusGator statusgator.com | None found | – | 38 D | – | no | 2026-11-04 | | Statuspage statuspage.io | None found | – | 35 D | – | no | 2026-11-04 | | Storia storia.ai | None found | – | 43 D | – | not read | 2026-11-04 | | Storybook storybook.js.org | None found | – | 64 C | – | no | 2026-11-04 | | Strapi strapi.io | None found | – | 64 C | – | no | 2026-11-04 | | Struct struct.ai | None found | – | 67 C | – | no | 2026-11-04 | | Stytch stytch.com | None found | – | 63 C | – | no | 2026-11-04 | | SugarSync sugarsync.com | None found | – | 55 C | – | no | 2026-11-04 | | Sumologic sumologic.com | None found | – | 71 B | – | no | 2026-11-04 | | Sunpia sunpia.io | None found | – | 40 D | – | no | 2026-11-04 | | Superb AI superb-ai.com | None found | – | 65 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/none-found/page/4/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "None found, page 5 | Agent MCP Directory" description: "472 companies with MCP status none found. Not counted as having an MCP server. Page 5 of 5. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/none-found/page/5 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # None found, page 5 | Agent MCP Directory > 472 companies with MCP status none found. Not counted as having an MCP server. Page 5 of 5. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/none-found/page/5 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: none found, page 5 472 companies have the status none found. No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to. This page lists rows 401 to 472, from Supervisely to ZeroDev. 10 of them have a CLI on record. ## Rows 401 to 472 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Supervisely supervisely.com | None found | – | 65 C | – | no | 2026-11-04 | | Surge surge.app | None found | – | 72 B | – | no | 2026-11-04 | | Swarmia swarmia.com | None found | – | 60 C | – | no | 2026-11-04 | | Sweep sweep.dev | None found | – | 40 D | – | not read | 2026-11-04 | | T3 t3.chat | None found | – | 58 C | – | no | 2026-11-04 | | Tabnine tabnine.com | None found | – | 66 C | – | not read | 2026-11-04 | | Tailor tailor.tech | None found | – | 50 C | – | no | 2026-11-04 | | Tailscale tailscale.com | None found | – | 69 C | – | no | 2026-11-04 | | Taloflow taloflow.ai | None found | – | 39 D | – | no | 2026-11-04 | | Tana tana.inc | None found | – | 64 C | – | no | 2026-11-04 | | Temporal temporal.io | None found | – | 61 C | – | no | 2026-11-04 | | TensorPool tensorpool.dev | None found | – | 35 D | – | no | 2026-11-04 | | Termii termii.com | None found | – | 45 D | – | no | 2026-11-04 | | Terminal Use terminaluse.com | None found | – | 48 C | – | no | 2026-11-04 | | Terracotta tryterracotta.com | None found | – | 52 C | – | no | 2026-11-04 | | Terrateam terrateam.io | None found | – | 52 C | – | no | 2026-11-04 | | Texel.ai texel.ai | None found | – | 52 C | – | no | 2026-11-04 | | The Token Company thetokencompany.com | None found | – | 72 B | yes | no | 2026-11-04 | | Thunder Compute thundercompute.com | None found | – | 76 B | – | no | 2026-11-04 | | Thunkable thunkable.com | None found | – | 48 C | – | no | 2026-11-04 | | Tilda tilda.cc | None found | – | 49 C | – | no | 2026-11-04 | | Time Doctor timedoctor.com | None found | – | 37 D | – | no | 2026-11-04 | | Timely timely.com | None found | – | 58 C | – | no | 2026-11-04 | | Tiptap tiptap.dev | None found | – | 62 C | – | no | 2026-11-04 | | Toggl toggl.com | None found | – | 59 C | – | no | 2026-11-04 | | Trackjs trackjs.com | None found | – | 55 C | – | no | 2026-11-04 | | Trainloop AI trainloop.ai | None found | – | 51 C | – | no | 2026-11-04 | | Trainy trainy.ai | None found | – | 77 B | – | no | 2026-11-04 | | Travis CI travis-ci.com | None found | – | 53 C | – | no | 2026-11-04 | | Tray.ai tray.io | None found | – | 62 C | – | no | 2026-11-04 | | Trivy trivy.dev | None found | – | 34 D | – | no | 2026-11-04 | | Truffle AI trytruffle.ai | None found | – | 47 D | – | no | 2026-11-04 | | Truthsystems truthsystems.ai | None found | – | 37 D | – | no | 2026-11-04 | | Trynia trynia.ai | None found | – | 62 C | – | no | 2026-11-04 | | Trypillar trypillar.com | None found | – | 49 C | – | not read | 2026-11-04 | | Tumult tumult.com | None found | – | 35 D | – | no | 2026-11-04 | | Turso turso.tech | None found | – | 84 B | yes | no | 2026-11-04 | | Tusk usetusk.ai | None found | – | 56 C | – | no | 2026-11-04 | | Typewise typewise.app | None found | – | 75 B | – | no | 2026-11-04 | | Ubicloud ubicloud.com | None found | – | 49 C | – | no | 2026-11-04 | | UiPath uipath.com | None found | – | 62 C | – | no | 2026-11-04 | | unify unify.ai | None found | – | 42 D | – | no | 2026-11-04 | | Unsloth unsloth.ai | None found | – | 43 D | – | no | 2026-11-04 | | updown.io updown.io | None found | – | 33 D | – | no | 2026-11-04 | | v0 v0.dev | None found | – | 66 C | – | no | 2026-11-04 | | V7labs v7labs.com | None found | – | 72 B | – | no | 2026-11-04 | | VectorShift vectorshift.ai | None found | – | 69 C | – | no | 2026-11-04 | | Veryfi veryfi.com | None found | – | 69 C | – | no | 2026-11-04 | | vibe vibe.codes | None found | – | 39 D | – | no | 2026-11-04 | | VibeFlow vibeflow.ai | None found | – | 73 B | – | no | 2026-11-04 | | Vimmerse vimmerse.net | None found | – | 52 C | – | no | 2026-11-04 | | Virtualmin virtualmin.com | None found | – | 40 D | – | no | 2026-11-04 | | vocode vocode.dev | None found | – | 60 C | – | no | 2026-11-04 | | Voker voker.ai | None found | – | 62 C | – | no | 2026-11-04 | | Warp warp.dev | None found | – | 80 B | – | no | 2026-11-04 | | Wasmer wasmer.io | None found | – | 62 C | – | no | 2026-11-04 | | Waydev waydev.co | None found | – | 64 C | – | no | 2026-11-04 | | Webiny webiny.com | None found | – | 67 C | – | no | 2026-11-04 | | WeTransfer wetransfer.com | None found | – | 39 D | – | no | 2026-11-04 | | WeWeb weweb.io | None found | – | 62 C | – | no | 2026-11-04 | | WhyLabs whylabs.ai | None found | – | 47 D | – | no | 2026-11-04 | | Wild Moose AI wildmoose.ai | None found | – | 59 C | – | no | 2026-11-04 | | Windmill windmill.dev | None found | – | 56 C | – | no | 2026-11-04 | | Windsurf windsurf.com | None found | – | 57 C | – | no | 2026-11-04 | | Wiz wiz.io | None found | – | 58 C | – | no | 2026-11-04 | | Woodpecker CI woodpecker-ci.org | None found | – | 39 D | – | no | 2026-11-04 | | Workflowy workflowy.com | None found | – | 59 C | – | no | 2026-11-04 | | Wp wp.com | None found | – | 46 D | – | no | 2026-11-04 | | WP Engine wpengine.com | None found | – | 68 C | – | no | 2026-11-04 | | WunderGraph wundergraph.com | None found | – | 70 B | – | no | 2026-11-04 | | Zed zed.dev | None found | – | 57 C | – | no | 2026-11-04 | | ZeroDev zerodev.app | None found | – | 46 D | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/none-found/page/5/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP status sign-in required: 533 companies | Agent MCP Directory" description: "533 companies with MCP status sign-in required. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/sign-in site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP status sign-in required: 533 companies | Agent MCP Directory > 533 companies with MCP status sign-in required. Not counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/sign-in Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: sign-in required 533 companies have the status sign-in required. Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. This page lists rows 1 to 100, from 0xArchive to Confident AI. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 0xArchive 0xarchive.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 94 A | yes | not read | 2026-11-04 | | 3Dsellers 3dsellers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Aaly aaly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Account Executive Jobs accountexecutivejobs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Adkit adkit.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | Adlicio tryadlicio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | yes | not read | 2026-11-04 | | Ads Uploader adsuploader.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AgentData agentdata.run | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Agilitycms agilitycms.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ahrefs ahrefs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | AI Mail MCP aimailmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | aictrl aictrl.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Airbyte airbyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Airport Lounge List airportloungelist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Airtable airtable.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Airweave airweave.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 78 B | – | no | 2026-11-04 | | Akiflow akiflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Alai getalai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Alchemy alchemy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | AlfaNest alfanestlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AltoRank altorank.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Amplify amplify.is | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Amplitude amplitude.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | yes | no | 2026-11-04 | | Andi andiai.com | Sign-in required OAuth; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Anima animaapp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | AnomalyArmor anomalyarmor.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | yes | no | 2026-11-04 | | Ansvar ansvar.eu | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Antwork antwork.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | yes | not read | 2026-11-04 | | Any.do any.do | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | yes | no | 2026-11-04 | | Apify apify.com | Sign-in required OAuth DCR; tools not seen, not counted | apify-cli | 96 A+ | yes | no | 2026-11-04 | | APIVerve apiverve.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Apollo.io apollo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Appllama appllama.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 44 D | – | not read | 2026-11-04 | | AppmanAi appmanai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AppsFlyer appsflyer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Apricot apricot.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Arcmira arcmira.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Arkm arkm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Arrumou arrumou.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Artie artie.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Asana asana.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | ASO Atlas asoatlas.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | AssemblyAI assemblyai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | yes | no | 2026-11-04 | | Atlassian atlassian.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Attio attio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Audioscrape audioscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Autosana autosana.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Avalara avalara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | not read | 2026-11-04 | | aVenture aventure.vc | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | not read | 2026-11-04 | | Avo avo.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Axiom axiom.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | Basecamp basecamp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Basedash basedash.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Baserow baserow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Beancount.io beancount.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | beehiiv beehiiv.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | BeliefState beliefstate.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Bigdata.com bigdata.com | Sign-in required OAuth; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | Bird bird.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | no | 2026-11-04 | | Bitly bitly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Bitrise bitrise.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | BlindPay blindpay.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | BlogSEO blogseo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Box box.com | Sign-in required OAuth; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | brainattic brainattic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | briq briq.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Browserless browserless.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | yes | 2026-11-04 | | Browserstack browserstack.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Bubble bubble.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 40 D | – | no | 2026-11-04 | | Bugasura bugasura.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | not read | 2026-11-04 | | Buildkite buildkite.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | BulkPublish bulkpublish.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | Calendly calendly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | call4me call4.me | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Canva canva.com | Sign-in required OAuth DCR; tools not seen, not counted | @canva/cli | 42 D | – | no | 2026-11-04 | | Capacities capacities.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Carbon getcarbon.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Carrick carrick.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Causely causely.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Celigo celigo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | not read | 2026-11-04 | | CertScore.ai certscore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Charming charm.ing | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | yes | not read | 2026-11-04 | | Chatfuel chatfuel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 34 D | – | no | 2026-11-04 | | Chatway chatway.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Checkout.com checkout.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Chili Piper chilipiper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | Circleback circleback.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | CircleCI circleci.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | yes | 2026-11-04 | | Clean Notes cleannotes.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Clera getclera.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | ClickUp clickup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Close close.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | Cloudchipr cloudchipr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | Cloudglue cloudglue.dev | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Cloudinary cloudinary.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Cogram cogram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | CoinMarketCap coinmarketcap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | COLA Cloud colacloud.us | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Common Paper commonpaper.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | Confident AI confident-ai.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 90 A | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/sign-in/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Sign-in required, page 2 | Agent MCP Directory" description: "533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 2 of 6. Checked on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/status/sign-in/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Sign-in required, page 2 | Agent MCP Directory > 533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 2 of 6. Checked on 4 November 2026. Source: https://agentmcpdirectory.com/directory/status/sign-in/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: sign-in required, page 2 533 companies have the status sign-in required. Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. This page lists rows 101 to 200, from ConfigCat to Heroku. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | ConfigCat configcat.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 51 C | – | no | 2026-11-04 | | ConnectMachine connectmachine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Connie connie.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Contentful contentful.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | contentful-cli | 74 B | – | no | 2026-11-04 | | Conveo conveo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | CookieYes cookieyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | – | no | 2026-11-04 | | CoreNexis API corenexis.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | COROS coros.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | | Corsair corsair.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Cortex cortex.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Costory costory.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Coval coval.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 65 C | – | no | 2026-11-04 | | Cpln cpln.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Craft craft.do | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Crakseo crakseo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Cronitor cronitor.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | cubic cubic.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | CustomDomain™ customdomain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | cyon cyon.ch | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Cypress Cloud cypress.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Dabloons dabloons.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dart dartai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | yes | 2026-11-04 | | Datadog datadoghq.com | Sign-in required OAuth DCR; tools not seen, not counted | @datadog/datadog-ci | 69 C | – | no | 2026-11-04 | | DeepSource deepsource.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Depot depot.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Desktopcommander desktopcommander.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DevCycle devcycle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Dialer getdialer.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DialMCP dialmcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Didit One didit.me | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | – | no | 2026-11-04 | | DigitalOcean digitalocean.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 74 B | – | no | 2026-11-04 | | Divblox divblox.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DocNexus docnexus.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | DocSpring docspring.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Dodo Payments dodopayments.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | not read | 2026-11-04 | | Draftbit draftbit.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Dragoneye dragoneye.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | DSers dsers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | EAN-Search.org ean-search.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Easyship easyship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Edgaze edgaze.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Egnyte egnyte.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | ElevenFlo elevenflo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ElevenLabs elevenlabs.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Elfsight AI elfsight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Embrace embrace.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 38 D | – | no | 2026-11-04 | | EmpirioLabs AI empiriolabs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Encord encord.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 69 C | – | no | 2026-11-04 | | Eodly eodly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | not read | 2026-11-04 | | Epidemic Sound epidemicsound.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | eResource Scheduler eresourcescheduler.cloud | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Evermuse evermuse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Explorium explorium.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Expo expo.dev | Sign-in required OAuth DCR; tools not seen, not counted | eas-cli | 66 C | – | no | 2026-11-04 | | Extend extend.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | FairValid fairvalid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fastero fastero.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fathom fathom.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | Figma figma.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | FinancialFilings financialfilings.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fireflies.ai fireflies.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Firmafakta firmafakta.se | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flagsmith flagsmith.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 47 D | – | no | 2026-11-04 | | FlightQueue flightqueue.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | FlightSeatMap flightseatmap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Floot floot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | FlowLeap flowleap.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Flowra flowra.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Fly fly.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | no | 2026-11-04 | | FlyBest flybest.org | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Follore follore.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Formasty formasty.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | yes | not read | 2026-11-04 | | Frase frase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 89 A | yes | no | 2026-11-04 | | Freestyle freestyle.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | yes | no | 2026-11-04 | | Frihet frihet.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | FullEnrich fullenrich.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | not read | 2026-11-04 | | fynk fynk.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | not read | 2026-11-04 | | Gamedev gamedev.pl | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Gamma gamma.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | GitBook gitbook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 86 A | – | no | 2026-11-04 | | GitHub github.com | Sign-in required OAuth; tools not seen, not counted | – | 65 C | yes | no | 2026-11-04 | | Githubcopilot githubcopilot.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | GitLab gitlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | GlanceAI glance.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Glassflow glassflow.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Glif glif.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | yes | no | 2026-11-04 | | Globalping globalping.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | GoCardless gocardless.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Grafana grafana.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Granola granola.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Graphcms graphcms.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Graphify graphify.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | GrowthBook growthbook.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | Gryz gryz.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Guru getguru.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | Harness harness.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 75 B | – | no | 2026-11-04 | | Hcti hcti.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | HelixDB helix-db.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 82 B | yes | no | 2026-11-04 | | Hermoso hermoso.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Heroku heroku.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | heroku | 73 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/sign-in/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Sign-in required, page 3 | Agent MCP Directory" description: "533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 3 of 6. Checked on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/status/sign-in/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Sign-in required, page 3 | Agent MCP Directory > 533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 3 of 6. Checked on 4 November 2026. Source: https://agentmcpdirectory.com/directory/status/sign-in/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: sign-in required, page 3 533 companies have the status sign-in required. Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. This page lists rows 201 to 300, from Hitsteps to Notion. ## Rows 201 to 300 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Hitsteps hitsteps.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Honeycomb honeycomb.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | Hostinger hostinger.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 96 A+ | yes | yes | 2026-11-04 | | HubSpot hubspot.com | Sign-in required OAuth; tools not seen, not counted | @hubspot/cli | 72 B | – | no | 2026-11-04 | | Hubstaff hubstaff.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 45 D | – | no | 2026-11-04 | | Huddo huddo.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Hydrant hydrant.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | HypAware hypaware.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | HYPD AI hypd.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | not read | 2026-11-04 | | Hyperresearch hyperresearch.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | not read | 2026-11-04 | | Hypotize hypotize.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Icons8 icons8.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | IFTTT ifttt.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | imzala.net imzala.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | incident.io incident.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 64 C | – | no | 2026-11-04 | | Indeed indeed.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 25 F | – | no | 2026-11-04 | | Infobip infobip.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | InsForge insforge.dev | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | – | no | 2026-11-04 | | Instant instantdb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Intercom intercom.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | Interfere interfere.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Inttegro inttegro.com | Sign-in required OAuth; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Invideo invideo.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 54 C | – | not read | 2026-11-04 | | ISMS Copilot ismscopilot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | yes | not read | 2026-11-04 | | Jam.dev jam.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | JANCTION janction.jp | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Jitsu jitsu.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | no | 2026-11-04 | | Jotform jotform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | JumpCloud jumpcloud.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | JustCall justcall.host | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kajabi kajabi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | no | 2026-11-04 | | Kema kema-studio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kiln kiln3d.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kin kinlab.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Kinsta® kinsta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 72 B | – | no | 2026-11-04 | | Komodor komodor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Kong konghq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Kragos kragos.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lanesurf lanesurf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | yes | no | 2026-11-04 | | Layrcake layrcake.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lazybird lazybird.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Leadbase leadbase.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Leadpages leadpages.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | yes | no | 2026-11-04 | | Leash lea.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Letterly letterly.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LFG lfg.gm | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Limrun limrun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | Linear linear.app | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Lingo.dev lingo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | Listenetic listenetic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LiveCRM livecrm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | LLM Pulse llmpulse.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | | Local MCP local-mcp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Localcmd localcmd.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Locus paywithlocus.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | yes | no | 2026-11-04 | | LogRocket logrocket.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Longbridge longbridge.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | not read | 2026-11-04 | | Lucid lucid.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lumman lumman.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Lusha lusha.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | – | no | 2026-11-04 | | Luw.ai luw.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | mabl mabl.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Mailkite mailkite.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Make make.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Manufact manufact.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 83 B | yes | no | 2026-11-04 | | Mapbox mapbox.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | MCP Telegram mcp-telegram.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | MCPEmails mcpemails.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | mcprush.com mcprush.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Measuremy measuremy.site | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Medplum medplum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 43 D | – | no | 2026-11-04 | | Medusa medusajs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Mellow Hub mellow.world | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mem mem.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Memocore memocore.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mercado Pago mercadopago.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Microsoft 365 cloud.microsoft | Sign-in required OAuth; tools not seen, not counted | – | | – | no | 2026-11-04 | | Minds getminds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Minicor minicor.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 80 B | – | no | 2026-11-04 | | MiningBridge miningbridge.in | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Miro miro.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | no | 2026-11-04 | | Mnemoverse mnemoverse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Mobbin mobbin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | not read | 2026-11-04 | | Momentic momentic.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | monday monday.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 91 A | – | yes | 2026-11-04 | | MorningStar morningstar.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Mural mural.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 62 C | – | no | 2026-11-04 | | Mux mux.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | mypromind mypromind.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Nanonets nanonets.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Neon neon.com | Sign-in required OAuth DCR; tools not seen, not counted | neonctl | 88 A | yes | no | 2026-11-04 | | Neon neon.tech | Sign-in required OAuth DCR; tools not seen, not counted | – | 88 A | yes | no | 2026-11-04 | | Netlify netlify.com | Sign-in required OAuth DCR; tools not seen, not counted | netlify-cli | 92 A | yes | no | 2026-11-04 | | New Relic newrelic.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | ngrok ngrok.com | Sign-in required OAuth DCR; tools not seen, not counted | ngrok | 90 A | yes | no | 2026-11-04 | | Nimble nimble.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Nitrosend nitrosend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | – | not read | 2026-11-04 | | Nomas nomas.fyi | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Notion notion.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | – | no | 2026-11-04 | | Notion notion.so | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/sign-in/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Sign-in required, page 4 | Agent MCP Directory" description: "533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 4 of 6. Checked on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/status/sign-in/page/4 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Sign-in required, page 4 | Agent MCP Directory > 533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 4 of 6. Checked on 4 November 2026. Source: https://agentmcpdirectory.com/directory/status/sign-in/page/4 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: sign-in required, page 4 533 companies have the status sign-in required. Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. This page lists rows 301 to 400, from Novadata to ScreenVerb. ## Rows 301 to 400 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Novadata novadata.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Noveum noveum.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | not read | 2026-11-04 | | NVIDIA nvidia.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 77 B | – | no | 2026-11-04 | | Oakallow oakallow.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Octagon octagonai.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | OctoPerf octoperf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | Omnara omnara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | Omnidim omnidim.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 79 B | yes | not read | 2026-11-04 | | OneContext onecontext.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ONES ones.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | Onlook onlook.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 67 C | – | no | 2026-11-04 | | Openlayer openlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 82 B | – | no | 2026-11-04 | | OpenWork openworklabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | no | 2026-11-04 | | OpsLevel opslevel.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | not read | 2026-11-04 | | OpusClip opus.pro | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | Orangescrum orangescrum.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | yes | not read | 2026-11-04 | | OrgGen AI orggen.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Otter.ai otter.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Outlit outlit.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 85 B | yes | no | 2026-11-04 | | Outset outset.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | OwlCAD owlcad.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Oximy oximy.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 44 D | – | no | 2026-11-04 | | Paddle paddle.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Padlet padlet.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Pageree pageree.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PaidSync.ai paidsync.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Palisade palisade.email | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Pally pally.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | no | 2026-11-04 | | PandaDoc pandadoc.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 78 B | – | no | 2026-11-04 | | Pantheon pantheon.io | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Parad1gm parad1gm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Parallel parallel.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Parse.ly parsely.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Pathrule pathrule.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PAVE pavecfi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | PayPal paypal.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | no | 2026-11-04 | | Perspective AI getperspective.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | not read | 2026-11-04 | | Picsart picsart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Pipeboard pipeboard.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 70 B | – | not read | 2026-11-04 | | Pith pith.day | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Pixelesq pixelesq.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | not read | 2026-11-04 | | PixelFlow pixelflow.so | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Plaid plaid.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | Plori plori.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | not read | 2026-11-04 | | POEditor poeditor.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Polar Signals polarsignals.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Poly poly.app | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 39 D | – | no | 2026-11-04 | | Porkbun porkbun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 55 C | – | no | 2026-11-04 | | Port IO port.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | Posteverywhere posteverywhere.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 92 A | – | not read | 2026-11-04 | | PostHog posthog.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | Postman postman.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 80 B | – | no | 2026-11-04 | | Posy posy.page | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Precip precip.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | PredictLeads predictleads.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | Prembly prembly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | Prisma prisma.io | Sign-in required OAuth DCR; tools not seen, not counted | prisma | 82 B | yes | no | 2026-11-04 | | Process Street process.st | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | not read | 2026-11-04 | | ProLevelMax prolevelmax.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Prominara prominara.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | Prompeteer prompeteer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Publora publora.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 75 B | – | not read | 2026-11-04 | | Qualityclouds qualityclouds.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Qualityclouds qualityclouds.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Quicknode quicknode.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | no | 2026-11-04 | | Quillm quillm.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Quorum AI quorum.dog | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Railway railway.com | Sign-in required OAuth DCR; tools not seen, not counted | @railway/cli | 89 A | yes | not read | 2026-11-04 | | Ramp ramp.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Rampify rampify.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rankability rankability.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 63 C | – | not read | 2026-11-04 | | Raygun raygun.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | Read AI read.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 52 C | – | not read | 2026-11-04 | | Realeyes realeyes.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RegAI regai.tw | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Render render.com | Sign-in required OAuth; tools not seen, not counted | – | 82 B | yes | yes | 2026-11-04 | | ResumeQuick resumequick.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rivet rivet.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Roboflow roboflow.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 72 B | – | no | 2026-11-04 | | RoboSystems robosystems.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | RocketReach rocketreach.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 53 C | – | no | 2026-11-04 | | Rocketship deployrocketship.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Rootly rootly.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Rulebase rulebase.co | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Runcaptain runcaptain.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 57 C | – | no | 2026-11-04 | | Runcomfy runcomfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Runpulse runpulse.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 77 B | – | no | 2026-11-04 | | Rus.sh rus.sh | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sadiqoon sadiqoon.uk | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Saifs saifs.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Salvy salvy.com.br | Sign-in required OAuth DCR; tools not seen, not counted | – | 76 B | – | no | 2026-11-04 | | Sanity sanity.io | Sign-in required OAuth DCR; tools not seen, not counted | @sanity/cli | 72 B | – | no | 2026-11-04 | | Say It Again sayitagain.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sazabi sazabi.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Scavio scavio.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scorecard scorecard.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Scoutapm scoutapm.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Screenforge screenforge.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ScreensDesign screensdesign.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | ScreenVerb screenverb.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/sign-in/page/4/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Sign-in required, page 5 | Agent MCP Directory" description: "533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 5 of 6. Checked on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/status/sign-in/page/5 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Sign-in required, page 5 | Agent MCP Directory > 533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 5 of 6. Checked on 4 November 2026. Source: https://agentmcpdirectory.com/directory/status/sign-in/page/5 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: sign-in required, page 5 533 companies have the status sign-in required. Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. This page lists rows 401 to 500, from Scripe to UXKIN. ## Rows 401 to 500 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Scripe scripe.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | not read | 2026-11-04 | | SearchAPI searchapi.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 39 D | – | not read | 2026-11-04 | | SearchConsole.ai searchconsole.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Searcherries searcherries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sellfy sellfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | no | 2026-11-04 | | Semgrep semgrep.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | – | no | 2026-11-04 | | Sendmux sendmux.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | – | not read | 2026-11-04 | | SendPulse sendpulse.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 47 D | – | no | 2026-11-04 | | SentinelX sentinelx.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sentry sentry.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 65 C | – | not read | 2026-11-04 | | Sentry sentry.io | Sign-in required OAuth DCR; tools not seen, not counted | @sentry/cli | 79 B | – | no | 2026-11-04 | | Sequencer sequencer.media | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Serpstat serpstat.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Server4Agent server4agent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | ShapelessAI shapelessai.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Sherweb sherweb.com | Sign-in required OAuth; tools not seen, not counted | – | 53 C | – | not read | 2026-11-04 | | Shipbook shipbook.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shippo shippo.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 64 C | – | no | 2026-11-04 | | Short.io short.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Shortcut shortcut.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 85 B | yes | no | 2026-11-04 | | ShortSync shortsync.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SimpleBackups simplebackups.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SimplePDF simplepdf.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | yes | no | 2026-11-04 | | Simplescraper simplescraper.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Since.dev since.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sisense sisense.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | no | 2026-11-04 | | Sitelemetry sitelemetry.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sixtyfour sixtyfour.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 79 B | – | no | 2026-11-04 | | SkillDB skilldb.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | SKU.io sku.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Skydropx skydropx.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 41 D | – | no | 2026-11-04 | | Skyvern skyvern.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | no | 2026-11-04 | | Slack slack.com | Sign-in required OAuth; tools not seen, not counted | – | 59 C | – | no | 2026-11-04 | | SmartBear smartbear.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Social Growth Engineers socialgrowthengineers.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sociality.io sociality.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | not read | 2026-11-04 | | Socialync socialync.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Sofya sofya.co | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Spacefast spacefast.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 90 A | yes | not read | 2026-11-04 | | Spike spike.sh | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | SpriteCook spritecook.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | yes | not read | 2026-11-04 | | Square square.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 26 F | – | not read | 2026-11-04 | | Square squareup.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 57 C | – | no | 2026-11-04 | | Startup Ignition startupignition.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Statsig statsig.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Stillwind stillwind.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 55 C | – | no | 2026-11-04 | | StoriesIG storiesig.info | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | no | 2026-11-04 | | Streamkap streamkap.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Stripe stripe.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 74 B | yes | no | 2026-11-04 | | Structura structura.tools | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Studio99 studio99.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Studiomeyer studiomeyer.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 93 A | yes | not read | 2026-11-04 | | Supabase supabase.com | Sign-in required OAuth DCR; tools not seen, not counted | supabase | 93 A | yes | no | 2026-11-04 | | superglue superglue.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Supernova.io supernova.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | SuprSend suprsend.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 71 B | – | not read | 2026-11-04 | | Symbioza symbioza.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Synth AI usesynth.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Tallyfy tallyfy.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Tapcart tapcart.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | Taplio taplio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Taskfolk taskfolk.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Tavus tavus.io | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 76 B | – | no | 2026-11-04 | | Taxapp taxapp.nz | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Teamwork.com teamwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 68 C | – | no | 2026-11-04 | | Tempo tempo.new | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 68 C | – | no | 2026-11-04 | | Tenet Industries tenetindustries.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | | Tesorio tesorio.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | The Brains brains.ceo | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | The Bridge thebridge.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | The Context Company thecontext.company | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 58 C | – | no | 2026-11-04 | | ThoughtSpot thoughtspot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | | ThousandEyes thousandeyes.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 42 D | – | no | 2026-11-04 | | tl;dv tldv.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | not read | 2026-11-04 | | Todoist todoist.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 67 C | – | no | 2026-11-04 | | Todoist todoist.net | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Traveler.md traveler.md | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | yes | not read | 2026-11-04 | | Treza trezalabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | yes | not read | 2026-11-04 | | Truthifi truthifi.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Turkishtechlab turkishtechlab.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Twelfth twelfth.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | yes | not read | 2026-11-04 | | Twelve Data twelvedata.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | txscribe txscribe.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Typeform typeform.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 69 C | – | no | 2026-11-04 | | Uizze uizze.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ulapcybo ulapcybo.app | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Ultralayer ultralayer.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Unblocked getunblocked.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 87 A | – | not read | 2026-11-04 | | Unlayer unlayer.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 40 D | – | no | 2026-11-04 | | Unlimitless unlimitless.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Unsiloed AI unsiloed.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 60 C | – | no | 2026-11-04 | | Unstructured unstructured.io | Sign-in required OAuth DCR; tools not seen, not counted | – | 73 B | – | no | 2026-11-04 | | Upload-Post upload-post.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Upscrape upscrape.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Upsolve AI upsolve.ai | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | Uptime.com :) uptime.com | Sign-in required OAuth; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 59 C | – | no | 2026-11-04 | | UptimeRobot uptimerobot.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 83 B | – | no | 2026-11-04 | | Upwork upwork.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 48 C | – | no | 2026-11-04 | | UX Pilot uxpilot.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 50 C | – | not read | 2026-11-04 | | UXKIN uxkin.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/sign-in/page/5/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Sign-in required, page 6 | Agent MCP Directory" description: "533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 6 of 6. Checked on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/status/sign-in/page/6 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Sign-in required, page 6 | Agent MCP Directory > 533 companies with MCP status sign-in required. Not counted as having an MCP server. Page 6 of 6. Checked on 4 November 2026. Source: https://agentmcpdirectory.com/directory/status/sign-in/page/6 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: sign-in required, page 6 533 companies have the status sign-in required. Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. This page lists rows 501 to 533, from Valkyrlabs to Zoom. ## Rows 501 to 533 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Valkyrlabs valkyrlabs.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vanta vanta.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 66 C | – | no | 2026-11-04 | | Veles getveles.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 51 C | – | no | 2026-11-04 | | Vercel vercel.com | Sign-in required OAuth DCR; tools not seen, not counted | vercel | 91 A | yes | no | 2026-11-04 | | Veridu veridu.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | VeriTeknik veriteknik.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Versive getversive.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 84 B | – | no | 2026-11-04 | | VibeSEO vibeseo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vidova vidova.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 35 D | – | not read | 2026-11-04 | | Vike vike.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Visa visa.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 56 C | – | no | 2026-11-04 | | Vooban vooban.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Vultr vultr.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 62 C | – | no | 2026-11-04 | | Wall Marketing wall.marketing | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WarpBuild warpbuild.com | Sign-in required OAuth DCR; tools not seen, not counted; endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | – | 61 C | – | no | 2026-11-04 | | Watchgoose watchgoose.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 60 C | yes | not read | 2026-11-04 | | Webflow webflow.com | Sign-in required OAuth DCR; tools not seen, not counted | @webflow/webflow-cli | 78 B | – | not read | 2026-11-04 | | Webhound webhound.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 38 D | – | no | 2026-11-04 | | Whalesync whalesync.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 45 D | – | no | 2026-11-04 | | Whimsical whimsical.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 58 C | – | no | 2026-11-04 | | WhitePact whitepact.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Wix wix.com | Sign-in required OAuth DCR; tools not seen, not counted | @wix/cli | 64 C | – | no | 2026-11-04 | | WorkOS workos.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 86 A | yes | no | 2026-11-04 | | WP Agent getwpagent.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | WPWriter wpwriter.com | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | XMemo xmemo.dev | Sign-in required OAuth DCR; tools not seen, not counted | – | 81 B | – | not read | 2026-11-04 | | Zapier zapier.com | Sign-in required OAuth DCR; tools not seen, not counted | zapier-platform-cli | 84 B | – | no | 2026-11-04 | | Zenable zenable.io | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Zentrik zentrik.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | 66 C | – | not read | 2026-11-04 | | zeroheight zeroheight.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 37 D | – | no | 2026-11-04 | | Zine zine.ai | Sign-in required OAuth DCR; tools not seen, not counted | – | | – | not read | 2026-11-04 | | Zomato zomato.com | Sign-in required OAuth DCR; tools not seen, not counted | – | 16 F | – | not read | 2026-11-04 | | Zoom zoom.us | Sign-in required OAuth; tools not seen, not counted | – | 61 C | – | no | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/sign-in/page/6/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP status verified: 263 companies | Agent MCP Directory" description: "263 companies with MCP status verified. Counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/verified site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # MCP status verified: 263 companies | Agent MCP Directory > 263 companies with MCP status verified. Counted as having an MCP server. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/verified Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: verified 263 companies have the status verified. The endpoint answered a handshake with no credentials and listed its tools. This page lists rows 1 to 100, from 1102tools to GoSQLX. 7 of them have a CLI on record. Checked on 4 November 2026. ## Rows 1 to 100 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | 1102tools 1102tools.com | Verified no auth | – | | – | not read | 2026-11-04 | | 2extract 2extract.com | Verified no auth | – | | – | not read | 2026-11-04 | | Agent Ready agent-ready.dev | Verified no auth | – | 94 A | yes | yes | 2026-11-04 | | Agentalog agentalog.com | Verified no auth | – | | yes | not read | 2026-11-04 | | AgentBIT agentbit.app | Verified no auth | – | | yes | not read | 2026-11-04 | | AgenticWebScore agenticwebscore.com | Verified no auth | – | | yes | not read | 2026-11-04 | | aikstockdata aikstockdata.com | Verified no auth | – | | yes | not read | 2026-11-04 | | AIS Trail aistrail.com | Verified no auth | – | | – | not read | 2026-11-04 | | Allbirds allbirds.com | Verified no auth | – | 65 C | – | yes | 2026-11-04 | | Almxpp almxpp.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Alterlab alterlab.io | Verified no auth | – | | – | not read | 2026-11-04 | | Amazon Web Services aws.amazon.com | Verified no auth | awscli | 60 C | – | no | 2026-11-04 | | amCharts amcharts.com | Verified no auth | – | | – | not read | 2026-11-04 | | Antevo antevo.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Anurag anuragd.me | Verified no auth | – | 54 C | – | not read | 2026-11-04 | | Apex AI Academy apexai.academy | Verified no auth | – | | – | not read | 2026-11-04 | | APITube apitube.io | Verified no auth | – | | – | not read | 2026-11-04 | | Apollo GraphQL apollographql.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 80 B | – | no | 2026-11-04 | | App Store Tracker appstoretracker.com | Verified no auth | – | 43 D | – | not read | 2026-11-04 | | Astro astro.build | Verified no auth | – | 52 C | – | no | 2026-11-04 | | AthenaHQ athenahq.ai | Verified no auth | – | 67 C | – | no | 2026-11-04 | | Atom.com atom.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Autodesk autodesk.com | Verified no auth | – | 36 D | – | no | 2026-11-04 | | AWS api.aws | Verified no auth | – | | – | not read | 2026-11-04 | | Ball Ranks ballranks.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Barevalue barevalue.com | Verified no auth | – | | – | not read | 2026-11-04 | | Beglaubigt beglaubigt.de | Verified no auth | – | 49 C | – | no | 2026-11-04 | | BestPrice bestprice.gr | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | BGPT bgpt.pro | Verified no auth | – | | – | not read | 2026-11-04 | | Bibooks bibooks.org | Verified no auth | – | | – | not read | 2026-11-04 | | Bitmovin bitmovin.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | Bowmark bowmark.ai | Verified no auth | – | | – | not read | 2026-11-04 | | BreckenWander breckenwander.com | Verified no auth | – | | – | not read | 2026-11-04 | | Browser Use browser-use.com | Verified no auth | – | 91 A | yes | no | 2026-11-04 | | BuyWhere buywhere.ai | Verified no auth | – | | yes | not read | 2026-11-04 | | Casco casco.com | Verified no auth | – | 41 D | – | no | 2026-11-04 | | Catalystproject catalystproject.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Cerebrium cerebrium.ai | Verified no auth | – | 86 A | – | no | 2026-11-04 | | Chainstack chainstack.com | Verified no auth | – | 71 B | – | not read | 2026-11-04 | | Channel3 trychannel3.com | Verified no auth | – | 92 A | – | no | 2026-11-04 | | Ciphyr ciphyr.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Claude claude.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Clino clino.ch | Verified no auth | – | | – | not read | 2026-11-04 | | Cloudflare cloudflare.com | Verified no auth | wrangler | 82 B | yes | yes | 2026-11-04 | | Clueso clueso.io | Verified no auth | – | 78 B | – | no | 2026-11-04 | | Clutch.co clutch.co | Verified no auth | – | 21 F | – | no | 2026-11-04 | | Codex Reset codex-reset.com | Verified no auth | – | | yes | not read | 2026-11-04 | | CometChat cometchat.com | Verified no auth | – | 56 C | – | not read | 2026-11-04 | | Commsharbor commsharbor.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Context Awesome context-awesome.com | Verified no auth | – | | – | not read | 2026-11-04 | | Context7 context7.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | | Convex convex.dev | Verified no auth; endpoint found by subdomain guess, verified by connecting | convex | 71 B | – | not read | 2026-11-04 | | Courier courier.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 57 C | – | no | 2026-11-04 | | CryptoAPIs IO cryptoapis.io | Verified no auth | – | | – | not read | 2026-11-04 | | DC Hub dchub.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | Deed deed.page | Verified no auth | – | | yes | not read | 2026-11-04 | | DeepWiki deepwiki.com | Verified no auth | – | | – | not read | 2026-11-04 | | Designesy designesy.org | Verified no auth | – | | – | not read | 2026-11-04 | | Devin devin.ai | Verified no auth | – | 67 C | yes | not read | 2026-11-04 | | Digestseo digestseo.com | Verified no auth | – | | – | not read | 2026-11-04 | | Dm dm.de | Verified no auth | – | 51 C | – | no | 2026-11-04 | | DMCA.com dmca.com | Verified no auth | – | | – | no | 2026-11-04 | | Draw draw.io | Verified no auth | – | 13 F | – | not read | 2026-11-04 | | Dreamwork dreamworkhq.com | Verified no auth | – | | – | not read | 2026-11-04 | | DropTheHassle dropthehassle.com | Verified no auth | – | | – | not read | 2026-11-04 | | Dueback dueback.co | Verified no auth | – | | – | not read | 2026-11-04 | | Easy itseasy.co | Verified no auth | – | 87 A | – | no | 2026-11-04 | | EasyGerber easygerber.com | Verified no auth | – | | – | not read | 2026-11-04 | | Editalmd editalmd.com | Verified no auth | – | | yes | not read | 2026-11-04 | | emem emem.dev | Verified no auth | – | 85 B | – | not read | 2026-11-04 | | Epinu epinu.ai | Verified no auth | – | | – | not read | 2026-11-04 | | esimgomobile esimgomobile.com | Verified no auth | – | | – | not read | 2026-11-04 | | Etherscan etherscan.io | Verified no auth | – | | – | no | 2026-11-04 | | EveryCalc everycalc.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | Exa exa.ai | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Example4 example4.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Faxette faxette.com | Verified no auth | – | | – | not read | 2026-11-04 | | Faxforagents faxforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | Ferryhopper ferryhopper.com | Verified no auth | – | | – | not read | 2026-11-04 | | Fiber AI fiber.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | | Find-A-Domain findadomain.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Findabis findabis.com | Verified no auth | – | | – | not read | 2026-11-04 | | FlickDirect flickdirect.com | Verified no auth | – | | – | not read | 2026-11-04 | | Flightpowers flightpowers.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Footgun getfootgun.com | Verified no auth | – | | – | not read | 2026-11-04 | | Forter forter.com | Verified no auth | – | 92 A | yes | no | 2026-11-04 | | Fuentio fuentio.com | Verified no auth | – | | – | not read | 2026-11-04 | | Fund Momentum fundmomentum.vc | Verified no auth | – | | yes | not read | 2026-11-04 | | FusionAuth fusionauth.io | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Gaipagents gaipagents.com | Verified no auth | – | | yes | not read | 2026-11-04 | | GameAnalytics gameanalytics.com | Verified no auth | – | 80 B | – | no | 2026-11-04 | | GenMagic genmagic.co | Verified no auth | – | | yes | not read | 2026-11-04 | | Getappniche getappniche.com | Verified no auth | – | | – | not read | 2026-11-04 | | GetMattered getmattered.com | Verified no auth | – | | – | not read | 2026-11-04 | | GitMCP gitmcp.io | Verified no auth | – | 37 D | – | not read | 2026-11-04 | | Goldsky goldsky.com | Verified no auth | – | 81 B | – | not read | 2026-11-04 | | Gomdori gomdori.app | Verified no auth | – | | – | not read | 2026-11-04 | | Google google.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | Google Cloud googleapis.com | Verified no auth | – | | – | no | 2026-11-04 | | GoSQLX gosqlx.dev | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/verified/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Verified, page 2 | Agent MCP Directory" description: "263 companies with MCP status verified. Counted as having an MCP server. Page 2 of 3. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/verified/page/2 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Verified, page 2 | Agent MCP Directory > 263 companies with MCP status verified. Counted as having an MCP server. Page 2 of 3. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/verified/page/2 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: verified, page 2 263 companies have the status verified. The endpoint answered a handshake with no credentials and listed its tools. This page lists rows 101 to 200, from Greca House to Rta. 7 of them have a CLI on record. Checked on 4 November 2026. ## Rows 101 to 200 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | Greca House grecahouse.com | Verified no auth | – | | – | not read | 2026-11-04 | | GuruHotel guruhotel.com | Verified no auth | – | 71 B | – | no | 2026-11-04 | | Hands for Agents handsforagents.com | Verified no auth | – | | – | not read | 2026-11-04 | | HasData hasdata.com | Verified no auth | – | | – | not read | 2026-11-04 | | Helena helena.bio | Verified no auth | – | | – | not read | 2026-11-04 | | HemmaBo hemmabo.com | Verified no auth | – | | – | not read | 2026-11-04 | | Hexclave hexclave.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 85 B | yes | no | 2026-11-04 | | Hive Intelligence hiveintelligence.xyz | Verified no auth | – | | – | not read | 2026-11-04 | | Hookpulse hookpulse.net | Verified no auth | – | | yes | not read | 2026-11-04 | | hotglue hotglue.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Hugging Face huggingface.co | Verified no auth | huggingface_hub | 82 B | – | no | 2026-11-04 | | HVTracker hvtracker.net | Verified no auth | – | | – | not read | 2026-11-04 | | iDevice idevice.com | Verified no auth | – | | – | not read | 2026-11-04 | | iHatePosting ihateposting.com | Verified no auth | – | | – | not read | 2026-11-04 | | ImageKit imagekit.io | Verified no auth | – | 63 C | – | not read | 2026-11-04 | | Inamprotocol inamprotocol.org | Verified no auth | – | | – | not read | 2026-11-04 | | IndustryLens industry-lens.com | Verified no auth | – | | – | not read | 2026-11-04 | | Invokary invokary.com | Verified no auth | – | | – | not read | 2026-11-04 | | Isonavigator isonavigator.io | Verified no auth | – | | – | not read | 2026-11-04 | | Isto Intents istointents.com | Verified no auth | – | | – | not read | 2026-11-04 | | Javadocs.dev javadocs.dev | Verified no auth | – | 47 D | yes | not read | 2026-11-04 | | JobsPipe jobspipe.dev | Verified no auth | – | 96 A+ | yes | not read | 2026-11-04 | | JustClaw-It justclaw.it.com | Verified no auth | – | | – | not read | 2026-11-04 | | Kaiv kaiv.ai | Verified no auth | – | | – | not read | 2026-11-04 | | kari kari.com | Verified no auth | – | | – | not read | 2026-11-04 | | Keenable keenable.ai | Verified no auth | – | 68 C | yes | not read | 2026-11-04 | | Kodza kodza.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Kraken kraken.com | Verified no auth | – | 82 B | yes | no | 2026-11-04 | | Kujolang.ai kujolang.ai | Verified no auth | – | 55 C | – | not read | 2026-11-04 | | Lambdatest lambdatest.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Lazaretto lazaretto.dev | Verified no auth | – | | yes | not read | 2026-11-04 | | Lezzoo lezzoo.com | Verified no auth | – | 69 C | – | no | 2026-11-04 | | Liquilens liquilens.in | Verified no auth | – | 72 B | – | not read | 2026-11-04 | | LiveScore MCP livescoremcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Lodestarindex lodestarindex.com | Verified no auth | – | | – | not read | 2026-11-04 | | Ludo AI ludo.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Maatsii maatsii.com | Verified no auth | – | | – | not read | 2026-11-04 | | Macfax macfax.com | Verified no auth | – | | – | not read | 2026-11-04 | | Magic Hour magichour.ai | Verified no auth | – | 89 A | yes | no | 2026-11-04 | | Mailbuttons mailbuttons.com | Verified no auth | – | | – | not read | 2026-11-04 | | Mailrith mailrith.com | Verified no auth | – | 97 A+ | yes | not read | 2026-11-04 | | Manifold manifold.markets | Verified no auth | – | | – | not read | 2026-11-04 | | MAQAMI maqami.co | Verified no auth | – | | – | not read | 2026-11-04 | | Market Eyes Live marketeyeslive.com | Verified no auth | – | | – | not read | 2026-11-04 | | Mediawork mediawork.io | Verified no auth | – | | – | not read | 2026-11-04 | | Memxus memxus.com | Verified no auth | – | | – | not read | 2026-11-04 | | Microsoft microsoft.com | Verified no auth | – | 62 C | – | no | 2026-11-04 | | Microsoft Learn learn.microsoft.com | Verified no auth | azure-cli | 24 F | – | not read | 2026-11-04 | | Mintlify mintlify.com | Verified no auth | mint | 74 B | – | no | 2026-11-04 | | Mirabelloconsultancy mirabelloconsultancy.com | Verified no auth | – | | – | not read | 2026-11-04 | | MnogoReels mnogo-reels.ru | Verified no auth | – | | – | not read | 2026-11-04 | | MotionSpec motionspec.dev | Verified no auth | – | | – | not read | 2026-11-04 | | NegativeEV negativeev.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Neuronto neuronto.com | Verified no auth | – | | yes | not read | 2026-11-04 | | NewsCatcher newscatcherapi.com | Verified no auth | – | 63 C | – | no | 2026-11-04 | | Noonlaunch noonlaunch.com | Verified no auth | – | 61 C | yes | not read | 2026-11-04 | | Notaiochianese notaiochianese.it | Verified no auth | – | | – | not read | 2026-11-04 | | Nslookup nslookup.io | Verified no auth | – | | – | not read | 2026-11-04 | | NUM itsnum.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Obolusfinanz obolusfinanz.de | Verified no auth | – | | – | not read | 2026-11-04 | | Offline Protocol offlineprotocol.com | Verified no auth | – | | – | not read | 2026-11-04 | | Okfindex okfindex.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Okibi okibi.ai | Verified no auth | – | 35 D | – | no | 2026-11-04 | | OpenAccountants openaccountants.com | Verified no auth | – | 64 C | – | not read | 2026-11-04 | | OpenZeppelin openzeppelin.com | Verified no auth | – | 68 C | – | not read | 2026-11-04 | | Optionsahoy optionsahoy.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Ora ora.ai | Verified no auth | – | 95 A+ | yes | yes | 2026-11-04 | | Pageaudit pageaudit.online | Verified no auth | – | | yes | not read | 2026-11-04 | | PakBus pakbus.app | Verified no auth | – | | – | not read | 2026-11-04 | | PatchDesign.AI patchdesign.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Paytm paytm.com | Verified no auth | – | 52 C | – | no | 2026-11-04 | | Peek.com peek.com | Verified no auth | – | 39 D | – | not read | 2026-11-04 | | PensionHunter pensionhunter.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Pexafy pexafy.com | Verified no auth | – | | – | not read | 2026-11-04 | | PicSee picsee.io | Verified no auth | – | | – | not read | 2026-11-04 | | Pontofato pontofato.com | Verified no auth | – | | yes | not read | 2026-11-04 | | PostData postdata.cloud | Verified no auth | – | | – | not read | 2026-11-04 | | Postel postel.app | Verified no auth | – | | – | not read | 2026-11-04 | | Powmcp powmcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | Predictionmarketspicks predictionmarketspicks.com | Verified no auth | – | | – | not read | 2026-11-04 | | PreShiftIQ preshiftiq.com | Verified no auth | – | | – | not read | 2026-11-04 | | Primitive primitive.dev | Verified no auth | – | 96 A+ | yes | yes | 2026-11-04 | | Probativegrowth probativegrowth.com | Verified no auth | – | | – | not read | 2026-11-04 | | PropelAuth propelauth.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 58 C | – | no | 2026-11-04 | | Ptpge ptpge.org | Verified no auth | – | | – | not read | 2026-11-04 | | Pulse thepulse.markets | Verified no auth | – | | – | not read | 2026-11-04 | | Pushary pushary.com | Verified no auth | – | 79 B | – | not read | 2026-11-04 | | Radar Cnpj radar-cnpj.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Rapier rapier.website | Verified no auth | – | | – | not read | 2026-11-04 | | Redpanda redpanda.com | Verified no auth | – | 68 C | – | no | 2026-11-04 | | RegEvidenceHub regevidencehub.com | Verified no auth | – | | – | not read | 2026-11-04 | | Reka reka.ai | Verified no auth | – | 77 B | – | no | 2026-11-04 | | Relvato relvato.com | Verified no auth | – | | – | not read | 2026-11-04 | | Remote MCP remote-mcp.com | Verified no auth | – | | – | not read | 2026-11-04 | | ReplyOnTheFly replyonthefly.com | Verified no auth | – | | – | not read | 2026-11-04 | | ReputeMap reputemap.com | Verified no auth | – | | – | not read | 2026-11-04 | | Resemble AI resemble.ai | Verified no auth | – | 74 B | – | not read | 2026-11-04 | | RestaurantDoctorAI restaurantdoctorai.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Rokha rokha.ai | Verified no auth | – | | – | not read | 2026-11-04 | | Rta rta.lat | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/verified/page/2/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Verified, page 3 | Agent MCP Directory" description: "263 companies with MCP status verified. Counted as having an MCP server. Page 3 of 3. Checked on 4 November 2026. Each row links to its entry." canonical: https://agentmcpdirectory.com/directory/status/verified/page/3 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory lists" --- # Verified, page 3 | Agent MCP Directory > 263 companies with MCP status verified. Counted as having an MCP server. Page 3 of 3. Checked on 4 November 2026. Each row links to its entry. Source: https://agentmcpdirectory.com/directory/status/verified/page/3 Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP status: verified, page 3 263 companies have the status verified. The endpoint answered a handshake with no credentials and listed its tools. This page lists rows 201 to 263, from SanctionsKit to Ziptax. 7 of them have a CLI on record. Checked on 4 November 2026. ## Rows 201 to 263 | Company | MCP server | CLI | Ora score | OpenAPI | WebMCP | Last verified | | --- | --- | --- | --- | --- | --- | --- | | SanctionsKit sanctionskit.com | Verified no auth | – | | yes | not read | 2026-11-04 | | Scalix Cloud scalix.world | Verified no auth | – | | – | not read | 2026-11-04 | | Scento scento.com | Verified no auth | – | 82 B | – | not read | 2026-11-04 | | Scholar Sidekick scholar-sidekick.com | Verified no auth | – | 98 A+ | yes | not read | 2026-11-04 | | ScrapingBee scrapingbee.com | Verified no auth | – | 61 C | – | not read | 2026-11-04 | | Seam seam.co | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 53 C | – | no | 2026-11-04 | | Search Fragments searchfragments.com | Verified no auth | – | | – | not read | 2026-11-04 | | Seller Profit Doctor sellerprofitdoctor.com | Verified no auth | – | | – | not read | 2026-11-04 | | SEOmatic seomatic.ai | Verified no auth | – | 35 D | – | not read | 2026-11-04 | | SerpApi serpapi.com | Verified no auth | – | 59 C | – | not read | 2026-11-04 | | ShipStatic shipstatic.com | Verified no auth | – | | – | not read | 2026-11-04 | | Shortimize shortimize.com | Verified no auth | – | | – | not read | 2026-11-04 | | Siemens siemens.com | Verified no auth | – | 56 C | – | no | 2026-11-04 | | Sitepulsar sitepulsar.ai | Verified no auth | – | | yes | not read | 2026-11-04 | | SkyAccess skyaccess.com | Verified no auth | – | | – | not read | 2026-11-04 | | SlideForge slideforge.dev | Verified no auth | – | | – | not read | 2026-11-04 | | Soracom soracom.com | Verified no auth | – | | – | not read | 2026-11-04 | | Speakeroo speakeroo.app | Verified no auth | – | 73 B | – | not read | 2026-11-04 | | Spicrawl spicrawl.com | Verified no auth | – | | – | not read | 2026-11-04 | | SRIFT srift.app | Verified no auth | – | | yes | not read | 2026-11-04 | | Steellantern steellantern.com | Verified no auth | – | | – | not read | 2026-11-04 | | Studocu studocu.com | Verified no auth | – | 40 D | – | no | 2026-11-04 | | SubwayInfo NYC subwayinfo.nyc | Verified no auth | – | | yes | not read | 2026-11-04 | | Sugra sugra.ai | Verified no auth | – | 49 C | – | not read | 2026-11-04 | | SuperAnnotate superannotate.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 54 C | – | no | 2026-11-04 | | SurfacedBy AI surfacedby.com | Verified no auth | – | | – | not read | 2026-11-04 | | Svelte svelte.dev | Verified no auth | – | 58 C | – | not read | 2026-11-04 | | TableJourney tablejourney.com | Verified no auth | – | | yes | not read | 2026-11-04 | | TakeMeUp.cv takemeup.cv | Verified no auth | – | | – | not read | 2026-11-04 | | TapTax taptax.co.uk | Verified no auth | – | | – | not read | 2026-11-04 | | Techfabric techfabric.com | Verified no auth | – | | – | not read | 2026-11-04 | | Telnyx telnyx.com | Verified no auth | – | 99 A+ | yes | yes | 2026-11-04 | | TempGuru tempguru.co | Verified no auth | – | | – | not read | 2026-11-04 | | Terminal Tax terminal.tax | Verified no auth | – | | – | not read | 2026-11-04 | | The White Report thewhitereport.com | Verified no auth | – | | – | not read | 2026-11-04 | | There's An AI For That theresanaiforthat.com | Verified no auth | – | 9 F | – | not read | 2026-11-04 | | Tomiseregi tomiseregi.si | Verified no auth | – | | – | not read | 2026-11-04 | | TracePass tracepass.eu | Verified no auth | – | | yes | not read | 2026-11-04 | | trivago trivago.com | Verified no auth | – | 55 C | – | no | 2026-11-04 | | Turbo Notify turbonotify.com | Verified no auth | – | | – | not read | 2026-11-04 | | TweetSave tweetsave.org | Verified no auth | – | | – | not read | 2026-11-04 | | Twilio twilio.com | Verified no auth | twilio-cli | 85 B | – | no | 2026-11-04 | | Upstash upstash.com | Verified no auth | – | 91 A | – | no | 2026-11-04 | | Usercentrics usercentrics.eu | Verified no auth | – | | – | yes | 2026-11-04 | | Vaaya vaaya.ai | Verified no auth | – | 90 A | yes | not read | 2026-11-04 | | VibeMarketing vibemarketing.ninja | Verified no auth | – | | – | not read | 2026-11-04 | | Viridisconservation viridisconservation.com | Verified no auth | – | | – | not read | 2026-11-04 | | VISEON viseon.io | Verified no auth | – | | – | not read | 2026-11-04 | | Vybenetwork vybenetwork.com | Verified no auth | – | | – | not read | 2026-11-04 | | Web3Juice web3juice.com | Verified no auth | – | | – | not read | 2026-11-04 | | WebinarIgnition webinarignition.com | Verified no auth | – | | – | not read | 2026-11-04 | | WebZum webzum.com | Verified no auth | – | | – | not read | 2026-11-04 | | WITAN Markets witan.markets | Verified no auth | – | | yes | not read | 2026-11-04 | | Wolfram wolfram.com | Verified no auth | – | | – | no | 2026-11-04 | | WRDO wrdo.co.za | Verified no auth | – | 48 C | – | not read | 2026-11-04 | | Xenition xenition.com | Verified no auth | – | | – | not read | 2026-11-04 | | Xquik xquik.com | Verified no auth | – | 92 A | yes | not read | 2026-11-04 | | YouSpot youspot.com | Verified no auth | – | 98 A+ | yes | yes | 2026-11-04 | | ZeroEval zeroeval.com | Verified no auth; endpoint found by subdomain guess, verified by connecting | – | 65 C | – | no | 2026-11-04 | | Zinc zinc.com | Verified no auth | – | 81 B | yes | no | 2026-11-04 | | Zip-Codes.com zip-codes.com | Verified no auth | – | | – | not read | 2026-11-04 | | Zip1 zip1.io | Verified no auth | – | | – | not read | 2026-11-04 | | Ziptax zip.tax | Verified no auth | – | | – | not read | 2026-11-04 | Ora score is Ora's cached score and grade for the company's domain, read on 5 November 2026 from GET /api/score/{domain}, or from Ora's GET /api/leaderboard of the same day where that was read first (a vendor-published figure). A blank cell means Ora returned no cached score for the domain, or the domain was not read. MCP status - [Verified](https://agentmcpdirectory.com/directory/status/verified/) 263 - [Sign-in required, tools not seen, not counted](https://agentmcpdirectory.com/directory/status/sign-in/) 533 - [Credential wall](https://agentmcpdirectory.com/directory/status/credential-wall/) 19 - [No answer](https://agentmcpdirectory.com/directory/status/no-answer/) 47 - [No tools listed](https://agentmcpdirectory.com/directory/status/no-tools/) 2 - [None found](https://agentmcpdirectory.com/directory/status/none-found/) 472 Auth type - [No authentication](https://agentmcpdirectory.com/directory/auth/none/) 263 - [API key](https://agentmcpdirectory.com/directory/auth/api-key/) 19 - [OAuth with client registration](https://agentmcpdirectory.com/directory/auth/oauth-dcr/) 517 - [OAuth without client registration](https://agentmcpdirectory.com/directory/auth/oauth/) 16 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/status/verified/page/3/index.md) ## Sources - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 - [Ora API reference, including GET /api/score/{domain}](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=list), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "StatusCake MCP server | Agent MCP Directory" description: "Does StatusCake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/statuscake-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # StatusCake MCP server | Agent MCP Directory > Does StatusCake have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/statuscake-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # StatusCake: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for StatusCake (statuscake.com), so the connector had nothing to connect to. Ora's cached score for statuscake.com is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | StatusCake (registry title: statuscake.com) | | --- | --- | | Domain | statuscake.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 20 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for statuscake.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for StatusCake. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for statuscake.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for StatusCake. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/statuscake-com/index.md) ## Sources - [Ora score page for statuscake.com](https://ora.ai/score/statuscake.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 October 2026, read from GET /api/leaderboard) - [Where StatusCake was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [StatusCake website](https://statuscake.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "StatusGator MCP server | Agent MCP Directory" description: "Does StatusGator have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/statusgator-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # StatusGator MCP server | Agent MCP Directory > Does StatusGator have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/statusgator-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # StatusGator: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for StatusGator (statusgator.com), so the connector had nothing to connect to. Ora's cached score for statusgator.com is 38, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | StatusGator (registry title: statusgator.com) | | --- | --- | | Domain | statusgator.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 38, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for statusgator.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for StatusGator. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for statusgator.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for StatusGator. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: statusgator.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/statusgator-com/index.md) ## Sources - [Ora score page for statusgator.com](https://ora.ai/score/statusgator.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where StatusGator was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [StatusGator website](https://statusgator.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Statuspage MCP server | Agent MCP Directory" description: "Does Statuspage have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/statuspage-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Statuspage MCP server | Agent MCP Directory > Does Statuspage have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/statuspage-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Statuspage: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Statuspage (statuspage.io), so the connector had nothing to connect to. Ora's cached score for statuspage.io is 35, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Statuspage (registry title: statuspage.io) | | --- | --- | | Domain | statuspage.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 820 on the list of 4 November 2026 | | Ora score | 35, grade D; Ora scanned the domain on 11 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for statuspage.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Statuspage. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for statuspage.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Statuspage. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/statuspage-io/index.md) ## Sources - [Ora score page for statuspage.io](https://ora.ai/score/statuspage.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 August 2026, read from GET /api/score) - [Where Statuspage was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Statuspage website](https://statuspage.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Steellantern MCP server | Agent MCP Directory" description: "Steellantern has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/steellantern-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Steellantern MCP server | Agent MCP Directory > Steellantern has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/steellantern-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Steellantern: MCP server, CLI and agent surfaces Yes: Steellantern runs a public MCP server at fluxproof.steellantern.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: fluxproof\_preflight, fluxproof\_get\_free\_key, fluxproof\_offer. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Steellantern (registry title: FluxProof) | | --- | --- | | Domain | steellantern.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for steellantern.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://fluxproof.steellantern.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | fluxproof 0.1.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 258 ms over 1 attempt | ### Tools listed 6 tools - fluxproof\_preflight - fluxproof\_get\_free\_key - fluxproof\_offer - fluxproof\_create\_monitor - fluxproof\_check\_now - fluxproof\_list\_changes ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:42Z https://fluxproof.steellantern.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 840 ms - 20:04:40Z https://fluxproof.steellantern.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 258 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://fluxproof.steellantern.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Steellantern. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/steellantern-com/index.md) ## Sources - [Steellantern website](https://steellantern.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Stillwind MCP server | Agent MCP Directory" description: "Stillwind: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/stillwind-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Stillwind MCP server | Agent MCP Directory > Stillwind: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/stillwind-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Stillwind: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Stillwind; the connector's guess at mcp.stillwind.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Stillwind (registry title: stillwind.ai) | | --- | --- | | Domain | stillwind.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 55, grade C; Ora scanned the domain on 17 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for stillwind.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.stillwind.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 538 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:41Z https://mcp.stillwind.ai/mcp sent initialize result auth-required (HTTP 401) 293 ms - 20:04:41Z https://mcp.stillwind.ai/mcp sent initialize result auth-required (HTTP 401) 538 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", resource_metadata="https://mcp.stillwind.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.stillwind.ai | | Authorization server metadata | mcp.stillwind.ai | | Registration endpoint | https://mcp.stillwind.ai/register | ### The sign-in route, step by step 1. Request `https://mcp.stillwind.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.stillwind.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.stillwind.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Stillwind. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stillwind-ai/index.md) ## Sources - [Ora score page for stillwind.ai](https://ora.ai/score/stillwind.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 September 2026, read from GET /api/leaderboard) - [Where Stillwind was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Stillwind website](https://stillwind.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Storia MCP server | Agent MCP Directory" description: "Does Storia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/storia-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Storia MCP server | Agent MCP Directory > Does Storia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/storia-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Storia: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Storia (storia.ai), so the connector had nothing to connect to. Ora's cached score for storia.ai is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Storia (registry title: storia.ai) | | --- | --- | | Domain | storia.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for storia.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Storia. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for storia.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Storia. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/storia-ai/index.md) ## Sources - [Ora score page for storia.ai](https://ora.ai/score/storia.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Storia was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "StoriesIG MCP server | Agent MCP Directory" description: "StoriesIG: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/storiesig-info site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # StoriesIG MCP server | Agent MCP Directory > StoriesIG: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/storiesig-info Site: Agent MCP Directory Last reviewed: 2026-11-05 # StoriesIG: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for StoriesIG at api-wh.storiesig.info answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | StoriesIG (registry title: StoriesIG Instagram MCP Server) | | --- | --- | | Domain | storiesig.info | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 8,124 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for storiesig.info when asked on 5 November 2026 | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api-wh.storiesig.info/instagram/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 813 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:14Z https://api-wh.storiesig.info/instagram/mcp sent initialize result auth-required (HTTP 401) 625 ms - 20:01:53Z https://api-wh.storiesig.info/instagram/mcp sent initialize result auth-required (HTTP 401) 813 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", resource_metadata="https://api-wh.storiesig.info/.well-known/oauth-protected-resource/instagram/mcp" | | Protected resource metadata | api-wh.storiesig.info | | Authorization server metadata | auth-gate.multitool.cloud | | Registration endpoint | https://auth-gate.multitool.cloud/storiesig/oidc/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api-wh.storiesig.info/instagram/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api-wh.storiesig.info/.well-known/oauth-protected-resource/instagram/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth-gate.multitool.cloud/storiesig/oidc/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for StoriesIG. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: info.storiesig/instagram-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/storiesig-info/index.md) ## Sources - [Where StoriesIG was found](https://registry.modelcontextprotocol.io/v0/servers?search=info.storiesig%2Finstagram-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=storiesig), read 4 November 2026 - [StoriesIG website](https://storiesig.info), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Storyblok MCP server | Agent MCP Directory" description: "Storyblok answered the MCP handshake and listed no tools, so it is not counted. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/storyblok-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Storyblok MCP server | Agent MCP Directory > Storyblok answered the MCP handshake and listed no tools, so it is not counted. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/storyblok-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Storyblok: MCP server, CLI and agent surfaces Not counted. No source names an endpoint for Storyblok; the connector's guess at mcp.storyblok.com completed the handshake on 4 November 2026 but listed no tools, so there is nothing for an agent to call. Ora's cached score for storyblok.com is 67, grade C, read on 5 November 2026. ## Fact sheet | Company | Storyblok | | --- | --- | | Domain | storyblok.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No tools listed | | Ora score | 67, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for storyblok.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.storyblok.com/mcp | | --- | --- | | How it was found | mcp.storyblok.com was tried as a guess and answered; see the result below | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Storyblok 0.4.3 | | Capabilities | tools | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 601 ms over 1 attempt | | Result | tools/list: no response (HTTP 401) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:42Z https://mcp.storyblok.com/mcp sent initialize, notifications/initialized, tools/list result initialized-no-tools (HTTP 200) 531 ms - 20:04:41Z https://mcp.storyblok.com/mcp sent initialize, notifications/initialized, tools/list result initialized-no-tools (HTTP 200) 601 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.storyblok.com/mcp`. The connector could not tell what it wants: tools/list: no response (HTTP 401). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Storyblok. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/storyblok-com/index.md) ## Sources - [Ora score page for storyblok.com](https://ora.ai/score/storyblok.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/leaderboard) - [Where Storyblok was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Storyblok website](https://storyblok.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Storybook MCP server | Agent MCP Directory" description: "Does Storybook have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/storybook-js-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Storybook MCP server | Agent MCP Directory > Does Storybook have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/storybook-js-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Storybook: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Storybook (storybook.js.org), so the connector had nothing to connect to. Ora's cached score for storybook.js.org is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Storybook | | --- | --- | | Domain | storybook.js.org | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for storybook.js.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Storybook. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for storybook.js.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Storybook. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/storybook-js-org/index.md) ## Sources - [Ora score page for storybook.js.org](https://ora.ai/score/storybook.js.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 October 2026, read from GET /api/leaderboard) - [Where Storybook was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Storybook website](https://storybook.js.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Strapi MCP server | Agent MCP Directory" description: "Does Strapi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/strapi-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Strapi MCP server | Agent MCP Directory > Does Strapi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/strapi-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Strapi: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Strapi (strapi.io), so the connector had nothing to connect to. Ora's cached score for strapi.io is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Strapi | | --- | --- | | Domain | strapi.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for strapi.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Strapi. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for strapi.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Strapi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/strapi-io/index.md) ## Sources - [Ora score page for strapi.io](https://ora.ai/score/strapi.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Where Strapi was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Strapi website](https://strapi.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Streamkap MCP server | Agent MCP Directory" description: "Streamkap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/streamkap-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Streamkap MCP server | Agent MCP Directory > Streamkap: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/streamkap-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Streamkap: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Streamkap at mcp.streamkap.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Streamkap | | --- | --- | | Domain | streamkap.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for streamkap.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.streamkap.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,078 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:43Z https://mcp.streamkap.com/mcp sent initialize result auth-required (HTTP 401) 1189 ms - 20:04:41Z https://mcp.streamkap.com/mcp sent initialize result auth-required (HTTP 401) 1078 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.streamkap.com/mcp/.well-known/oauth-protected-resource", error="invalid_token", error_description="Provide either an OAuth Bearer token (Authorization: Bearer ) or X-Streamkap-Client-ID and X-Streamkap-Client-Secret headers." | | Protected resource metadata | mcp.streamkap.com | | Authorization server metadata | mcp.streamkap.com | | Registration endpoint | https://mcp.streamkap.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.streamkap.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.streamkap.com/mcp/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.streamkap.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Streamkap. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.streamkap/tools | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/streamkap-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=streamkap), read 4 November 2026 - [Streamkap website](https://streamkap.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Stripe MCP server | Agent MCP Directory" description: "Stripe: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/stripe-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Stripe MCP server | Agent MCP Directory > Stripe: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/stripe-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Stripe: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Stripe at mcp.stripe.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Stripe | | --- | --- | | Domain | stripe.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 205 on the list of 4 November 2026 | | Ora score | 74, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for stripe.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.stripe.com | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:06 UTC | | Handshake time | 1,083 ms over 1 attempt | | Documentation | docs.stripe.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:55:53Z https://mcp.stripe.com sent initialize result auth-required (HTTP 401) 1027 ms - 20:01:28Z https://mcp.stripe.com sent initialize result auth-required (HTTP 401) 1052 ms - 20:06:07Z https://mcp.stripe.com sent initialize result auth-required (HTTP 401) 1083 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.stripe.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.stripe.com | | Authorization server metadata | access.stripe.com | | Registration endpoint | https://access.stripe.com/mcp/oauth2/register | | Auth as listed by a registry | OAuth2.1 API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.stripe.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.stripe.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://access.stripe.com/mcp/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Stripe. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: raw.githubusercontent.com (JSON, via vendor docs). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.stripe/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stripe-com/index.md) ## Sources - [Stripe MCP documentation](https://docs.stripe.com/mcp), read 4 November 2026 - [Ora score page for stripe.com](https://ora.ai/score/stripe.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=stripe), read 4 November 2026 - [Stripe website](https://stripe.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Struct MCP server | Agent MCP Directory" description: "Does Struct have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/struct-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Struct MCP server | Agent MCP Directory > Does Struct have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/struct-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Struct: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Struct (struct.ai), so the connector had nothing to connect to. Ora's cached score for struct.ai is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Struct (registry title: struct.ai) | | --- | --- | | Domain | struct.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for struct.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Struct. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for struct.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Struct. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/struct-ai/index.md) ## Sources - [Ora score page for struct.ai](https://ora.ai/score/struct.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Struct was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Struct website](https://struct.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Structura MCP server | Agent MCP Directory" description: "Structura: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/structura-tools site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Structura MCP server | Agent MCP Directory > Structura: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/structura-tools Site: Agent MCP Directory Last reviewed: 2026-11-05 # Structura: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Structura at mcp.structura.tools answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Structura | | --- | --- | | Domain | structura.tools | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for structura.tools when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.structura.tools/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 597 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:43Z https://mcp.structura.tools/ sent initialize result auth-required (HTTP 401) 736 ms - 20:04:41Z https://mcp.structura.tools/ sent initialize result auth-required (HTTP 401) 597 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer | | Protected resource metadata | mcp.structura.tools | | Authorization server metadata | mcp.structura.tools | | Registration endpoint | https://mcp.structura.tools/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.structura.tools/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.structura.tools/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.structura.tools/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Structura. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/structura-tools/index.md) ## Sources - [Structura website](https://structura.tools), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Studio99 MCP server | Agent MCP Directory" description: "Studio99: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/studio99-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Studio99 MCP server | Agent MCP Directory > Studio99: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/studio99-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Studio99: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Studio99 at mcp.studio99.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Studio99 (registry title: Calligraphy Maker by Studio99) | | --- | --- | | Domain | studio99.app | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for studio99.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.studio99.app/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 896 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:43Z https://mcp.studio99.app/api/mcp sent initialize result auth-required (HTTP 401) 1069 ms - 20:04:42Z https://mcp.studio99.app/api/mcp sent initialize result auth-required (HTTP 401) 896 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.studio99.app/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.studio99.app | | Authorization server metadata | mcp.studio99.app | | Registration endpoint | https://mcp.studio99.app/api/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.studio99.app/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.studio99.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.studio99.app/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Studio99. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.studio99/calligraphy | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/studio99-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=studio99), read 4 November 2026 - [Studio99 website](https://studio99.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Studiomeyer MCP server | Agent MCP Directory" description: "Studiomeyer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/studiomeyer-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Studiomeyer MCP server | Agent MCP Directory > Studiomeyer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/studiomeyer-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Studiomeyer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Studiomeyer at meetmyagent.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Studiomeyer (registry title: MeetMyAgent) | | --- | --- | | Domain | studiomeyer.io | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 93, grade A; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for studiomeyer.io, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://meetmyagent.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 503 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:43Z https://meetmyagent.io/mcp sent initialize result auth-required (HTTP 401) 585 ms - 20:04:42Z https://meetmyagent.io/mcp sent initialize result auth-required (HTTP 401) 503 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://meetmyagent.io/.well-known/oauth-protected-resource" | | Protected resource metadata | meetmyagent.io | | Authorization server metadata | meetmyagent.io | | Registration endpoint | https://meetmyagent.io/v1/auth/oauth/register | ### The sign-in route, step by step 1. Request `https://meetmyagent.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://meetmyagent.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://meetmyagent.io/v1/auth/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Studiomeyer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: studiomeyer.io (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/studiomeyer-io/index.md) ## Sources - [Ora score page for studiomeyer.io](https://ora.ai/score/studiomeyer.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Studiomeyer website](https://studiomeyer.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Studocu MCP server | Agent MCP Directory" description: "Studocu has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/studocu-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Studocu MCP server | Agent MCP Directory > Studocu has an open MCP server with 18 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/studocu-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Studocu: MCP server, CLI and agent surfaces Yes: Studocu runs a public MCP server at agent-os-mcp.alpha.studocu.com that listed 18 tools to a client with no credentials on 4 November 2026. Examples: search-documents, search-institutions, search-courses. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for studocu.com is 40, grade D, read on 5 November 2026. ## Fact sheet | Company | Studocu | | --- | --- | | Domain | studocu.com | | Category | Education (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 4,126 on the list of 4 November 2026 | | Ora score | 40, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for studocu.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agent-os-mcp.alpha.studocu.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | agent-os-service 0.0.1 | | Capabilities | resources, tools | | Tools | 18 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,487 ms over 1 attempt | ### Tools listed 18 tools - search-documents - search-institutions - search-courses - get-course-syllabus - agent-os-session - read-artifact - read-detached-document - get-context - get-project-state - get-course-mastery - write-artifact - add-document-sources - create-project - update-project - request-creation - read-memory - write-memory - delete-memory ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:04Z https://agent-os-mcp.alpha.studocu.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 884 ms - 20:01:41Z https://agent-os-mcp.alpha.studocu.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1487 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://agent-os-mcp.alpha.studocu.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Studocu. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.studocu/studocu | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/studocu-com/index.md) ## Sources - [Ora score page for studocu.com](https://ora.ai/score/studocu.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/score) - [Where Studocu was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.studocu%2Fstudocu), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=studocu), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Stytch MCP server | Agent MCP Directory" description: "Does Stytch have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/stytch-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Stytch MCP server | Agent MCP Directory > Does Stytch have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/stytch-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Stytch: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Stytch (stytch.com), so the connector had nothing to connect to. Ora's cached score for stytch.com is 63, grade C, read on 5 November 2026. The company was added from the awesome-remote-mcp-servers list. ## Fact sheet | Company | Stytch | | --- | --- | | Domain | stytch.com | | Category | Identity & Auth (Ora leaderboard category) | | MCP server | None found | | Ora score | 63, grade C; Ora scanned the domain on 31 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for stytch.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Stytch. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for stytch.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Listed | ## CLI No CLI is on record for Stytch. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/stytch-com/index.md) ## Sources - [Ora score page for stytch.com](https://ora.ai/score/stytch.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 August 2026, read from GET /api/leaderboard) - [Where Stytch was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Stytch website](https://stytch.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Submit a company or an MCP endpoint | Agent MCP Directory" description: "How a company is added to the directory: send a domain and an MCP endpoint, and a read-only connector verifies it by connecting before publishing." canonical: https://agentmcpdirectory.com/directory/submit site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Directory" --- # Submit a company or an MCP endpoint | Agent MCP Directory > How a company is added to the directory: send a domain and an MCP endpoint, and a read-only connector verifies it by connecting before publishing. Source: https://agentmcpdirectory.com/directory/submit Site: Agent MCP Directory Last reviewed: 2026-11-04 # Submit a company Send a company domain and a public MCP endpoint, and a read-only connector will try the handshake before anything is published. The form on this page is not connected to a backend yet, so it posts nowhere; this page explains the process that will apply once it is. ## The form The form is not connected yet. It posts nowhere, nothing you type here is stored, and no submission can be received until a backend exists. This page says so rather than pretending. ## What happens to a submission 1. The connector requests the endpoint without a token, from a read-only client. It sends only the methods on [the allowlist](https://agentmcpdirectory.com/method/#allowlist). 2. It records the transport, protocol version, auth type and the OAuth metadata the endpoint publishes. 3. If the endpoint answers without credentials, it lists tools, resources and prompts. It never calls a tool and never signs in. 4. Only then is a row published, with the date and the connector log. An endpoint that does not answer is recorded as not counted, with the reason. ## What to send - The company domain. - The public endpoint URL, for example `https://mcp.example.com/mcp`. - The CLI package name and registry, if there is one. - A documentation link that names the endpoint. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/submit/index.md) ## Sources - [MCP specification](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "SubwayInfo NYC MCP server | Agent MCP Directory" description: "SubwayInfo NYC has an open MCP server with 26 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/subwayinfo-nyc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SubwayInfo NYC MCP server | Agent MCP Directory > SubwayInfo NYC has an open MCP server with 26 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/subwayinfo-nyc Site: Agent MCP Directory Last reviewed: 2026-11-05 # SubwayInfo NYC: MCP server, CLI and agent surfaces Yes: SubwayInfo NYC runs a public MCP server at subwayinfo.nyc that listed 26 tools to a client with no credentials on 4 November 2026. Examples: mta\_get\_arrivals, mta\_get\_line\_status, mta\_list\_alerts. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | SubwayInfo NYC | | --- | --- | | Domain | subwayinfo.nyc | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for subwayinfo.nyc when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://subwayinfo.nyc/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | mta-subway-mcp-server 1.0.0 | | Capabilities | resources, tools, prompts | | Tools | 26 | | Resources | 2 | | Prompts | 3 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 332 ms over 1 attempt | ### Tools listed 26 tools - mta\_get\_arrivals - mta\_get\_line\_status - mta\_list\_alerts - mta\_search\_stations - mta\_get\_station\_info - mta\_get\_tunnel\_connectivity - mta\_plan\_trip - mta\_get\_planned\_work - bus\_list\_alerts - bus\_get\_arrivals - bus\_get\_route\_info - bus\_search\_stops - ferry\_get\_arrivals - ferry\_list\_alerts - ferry\_search\_landings - ferry\_get\_routes - bike\_get\_station\_status - bike\_search\_stations - bike\_get\_availability\_summary - rail\_get\_departures - rail\_list\_alerts - rail\_search\_stations - rail\_get\_station\_info - transit\_ask - search - fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:44Z https://subwayinfo.nyc/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 790 ms - 20:04:41Z https://subwayinfo.nyc/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 332 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://subwayinfo.nyc/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SubwayInfo NYC. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: subwayinfo.nyc (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Yes: ckbk/subwayinfo-nyc | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/subwayinfo-nyc/index.md) ## Sources - [Where SubwayInfo NYC was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [SubwayInfo NYC website](https://subwayinfo.nyc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SugarSync MCP server | Agent MCP Directory" description: "Does SugarSync have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sugarsync-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SugarSync MCP server | Agent MCP Directory > Does SugarSync have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sugarsync-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SugarSync: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for SugarSync (sugarsync.com), so the connector had nothing to connect to. Ora's cached score for sugarsync.com is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | SugarSync (registry title: sugarsync.com) | | --- | --- | | Domain | sugarsync.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 30 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sugarsync.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for SugarSync. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sugarsync.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for SugarSync. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sugarsync-com/index.md) ## Sources - [Ora score page for sugarsync.com](https://ora.ai/score/sugarsync.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 September 2026, read from GET /api/leaderboard) - [Where SugarSync was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SugarSync website](https://sugarsync.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sugra MCP server | Agent MCP Directory" description: "Sugra has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sugra-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sugra MCP server | Agent MCP Directory > Sugra has an open MCP server with 11 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/sugra-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sugra: MCP server, CLI and agent surfaces Yes: Sugra runs a public MCP server at mcp.sugra.ai that listed 11 tools to a client with no credentials on 4 November 2026. Examples: sugra\_entity\_screen, sugra\_entity\_lookup, search\_endpoints. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for sugra.ai is 49, grade C, read on 5 November 2026. ## Fact sheet | Company | Sugra (registry title: Sugra MCP) | | --- | --- | | Domain | sugra.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 49, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sugra.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sugra.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | sugra-api 0.13.0 | | Capabilities | experimental, prompts, resources, tools | | Tools | 11 | | Resources | 8 | | Prompts | 6 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,634 ms over 1 attempt | ### Tools listed 11 tools - sugra\_entity\_screen - sugra\_entity\_lookup - search\_endpoints - describe\_endpoint - call\_endpoint - list\_toolsets - fetch\_data - list\_sources - resolve\_entity - get\_snapshot - get\_timeseries ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:45Z https://mcp.sugra.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1725 ms - 20:04:43Z https://mcp.sugra.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1634 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.sugra.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Sugra. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.sugra/api-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sugra-ai/index.md) ## Sources - [Ora score page for sugra.ai](https://ora.ai/score/sugra.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=sugra), read 4 November 2026 - [Sugra website](https://sugra.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sumologic MCP server | Agent MCP Directory" description: "Does Sumologic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sumologic-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sumologic MCP server | Agent MCP Directory > Does Sumologic have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sumologic-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sumologic: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sumologic (sumologic.com), so the connector had nothing to connect to. Ora's cached score for sumologic.com is 71, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sumologic (registry title: sumologic.com) | | --- | --- | | Domain | sumologic.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 71, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sumologic.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sumologic. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sumologic.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sumologic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: sumologic.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sumologic-com/index.md) ## Sources - [Ora score page for sumologic.com](https://ora.ai/score/sumologic.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Sumologic was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sumologic website](https://sumologic.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sunpia MCP server | Agent MCP Directory" description: "Does Sunpia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sunpia-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sunpia MCP server | Agent MCP Directory > Does Sunpia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sunpia-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sunpia: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sunpia (sunpia.io), so the connector had nothing to connect to. Ora's cached score for sunpia.io is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sunpia (registry title: sunpia.io) | | --- | --- | | Domain | sunpia.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sunpia.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sunpia. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sunpia.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sunpia. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sunpia-io/index.md) ## Sources - [Ora score page for sunpia.io](https://ora.ai/score/sunpia.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Sunpia was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Sunpia website](https://sunpia.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Supabase MCP server | Agent MCP Directory" description: "Supabase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/supabase-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Supabase MCP server | Agent MCP Directory > Supabase: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/supabase-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Supabase: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Supabase at mcp.supabase.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Supabase | | --- | --- | | Domain | supabase.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,781 on the list of 4 November 2026 | | Ora score | 93, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for supabase.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.supabase.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 375 ms over 1 attempt | | Documentation | supabase.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:06Z https://mcp.supabase.com/mcp sent initialize result auth-required (HTTP 401) 329 ms - 20:01:43Z https://mcp.supabase.com/mcp sent initialize result auth-required (HTTP 401) 375 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.supabase.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.supabase.com | | Authorization server metadata | api.supabase.com | | Registration endpoint | https://api.supabase.com/platform/oauth/apps/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.supabase.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.supabase.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.supabase.com/platform/oauth/apps/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | supabase on npm (page) | | --- | --- | | Exists | yes | | Latest version | 3.0.0 | | Last publish | 2 November 2026 | | Command names | supabase | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: supabase.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.supabase/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/supabase-com/index.md) ## Sources - [Supabase MCP documentation](https://supabase.com/docs/guides/getting-started/mcp), read 4 November 2026 - [Ora score page for supabase.com](https://ora.ai/score/supabase.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=supabase), read 4 November 2026 - [Supabase website](https://supabase.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SuperAnnotate MCP server | Agent MCP Directory" description: "SuperAnnotate has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/superannotate-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SuperAnnotate MCP server | Agent MCP Directory > SuperAnnotate has an open MCP server with 10 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/superannotate-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SuperAnnotate: MCP server, CLI and agent surfaces Yes: SuperAnnotate runs a public MCP server at mcp.superannotate.com, found by guessing the subdomain, and it listed 10 tools to a client with no credentials on 4 November 2026. Examples: get\_project\_metadata, list\_projects, get\_folder\_metadata. It speaks streamable-http, protocol 2025-11-25. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | SuperAnnotate (registry title: superannotate.com) | | --- | --- | | Domain | superannotate.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 54, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for superannotate.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.superannotate.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | SuperAnnotate 3.4.5 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 10 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,700 ms over 1 attempt | ### Tools listed 10 tools - get\_project\_metadata - list\_projects - get\_folder\_metadata - list\_folders - get\_item\_metadata - list\_items - set\_item\_status - get\_item\_annotations - set\_item\_annotations - list\_workflow\_statuses ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:45Z https://mcp.superannotate.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1661 ms - 20:04:44Z https://mcp.superannotate.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1700 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.superannotate.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SuperAnnotate. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/superannotate-com/index.md) ## Sources - [Ora score page for superannotate.com](https://ora.ai/score/superannotate.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/score) - [Where SuperAnnotate was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [SuperAnnotate website](https://superannotate.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Superb AI MCP server | Agent MCP Directory" description: "Does Superb AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/superb-ai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Superb AI MCP server | Agent MCP Directory > Does Superb AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/superb-ai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Superb AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Superb AI (superb-ai.com), so the connector had nothing to connect to. Ora's cached score for superb-ai.com is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Superb AI (registry title: superb-ai.com) | | --- | --- | | Domain | superb-ai.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for superb-ai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Superb AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for superb-ai.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Superb AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/superb-ai-com/index.md) ## Sources - [Ora score page for superb-ai.com](https://ora.ai/score/superb-ai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Superb AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Superb AI website](https://superb-ai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "superglue MCP server | Agent MCP Directory" description: "superglue: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/superglue-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # superglue MCP server | Agent MCP Directory > superglue: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/superglue-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # superglue: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for superglue at api.superglue.cloud answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | superglue (registry title: NetSuite MCP by superglue) | | --- | --- | | Domain | superglue.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 67, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for superglue.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.superglue.cloud/mcp/netsuite | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,667 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:46Z https://api.superglue.cloud/mcp/netsuite sent initialize result auth-required (HTTP 401) 1641 ms - 20:04:44Z https://api.superglue.cloud/mcp/netsuite sent initialize result auth-required (HTTP 401) 1667 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.superglue.cloud/mcp/netsuite/.well-known/oauth-protected-resource" | | Protected resource metadata | api.superglue.cloud | | Authorization server metadata | api.superglue.cloud | | Registration endpoint | https://api.superglue.cloud/oauth/register | ### The sign-in route, step by step 1. Request `https://api.superglue.cloud/mcp/netsuite` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.superglue.cloud/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.superglue.cloud/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for superglue. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.superglue/netsuite, ai.superglue/sage-intacct | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/superglue-ai/index.md) ## Sources - [Ora score page for superglue.ai](https://ora.ai/score/superglue.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where superglue was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.superglue%2Fnetsuite), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=superglue), read 4 November 2026 - [superglue website](https://superglue.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Supernova.io MCP server | Agent MCP Directory" description: "Supernova.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/supernova-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Supernova.io MCP server | Agent MCP Directory > Supernova.io: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/supernova-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Supernova.io: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Supernova.io; the connector's guess at mcp.supernova.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Supernova.io | | --- | --- | | Domain | supernova.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 30 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for supernova.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.supernova.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 736 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:45Z https://mcp.supernova.io/mcp sent initialize result auth-required (HTTP 401) 727 ms - 20:04:43Z https://mcp.supernova.io/mcp sent initialize result auth-required (HTTP 401) 736 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://mcp.supernova.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.supernova.io | | Authorization server metadata | mcp.supernova.io | | Registration endpoint | https://mcp.supernova.io/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.supernova.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.supernova.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.supernova.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Supernova.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/supernova-io/index.md) ## Sources - [Ora score page for supernova.io](https://ora.ai/score/supernova.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 August 2026, read from GET /api/leaderboard) - [Where Supernova.io was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Supernova.io website](https://supernova.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Supervisely MCP server | Agent MCP Directory" description: "Does Supervisely have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/supervisely-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Supervisely MCP server | Agent MCP Directory > Does Supervisely have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/supervisely-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Supervisely: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Supervisely (supervisely.com), so the connector had nothing to connect to. Ora's cached score for supervisely.com is 65, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Supervisely (registry title: supervisely.com) | | --- | --- | | Domain | supervisely.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 65, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for supervisely.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Supervisely. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for supervisely.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Supervisely. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/supervisely-com/index.md) ## Sources - [Ora score page for supervisely.com](https://ora.ai/score/supervisely.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Supervisely was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Supervisely website](https://supervisely.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SuprSend MCP server | Agent MCP Directory" description: "SuprSend: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/suprsend-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SuprSend MCP server | Agent MCP Directory > SuprSend: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/suprsend-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SuprSend: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for SuprSend at mcp.suprsend.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | SuprSend | | --- | --- | | Domain | suprsend.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 71, grade B; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for suprsend.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.suprsend.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 800 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:47Z https://mcp.suprsend.com/mcp sent initialize result auth-required (HTTP 401) 1937 ms - 20:04:44Z https://mcp.suprsend.com/mcp sent initialize result auth-required (HTTP 401) 800 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.suprsend.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.suprsend.com | | Authorization server metadata | auth.suprsend.com | | Registration endpoint | https://auth.suprsend.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.suprsend.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.suprsend.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.suprsend.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SuprSend. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.suprsend/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/suprsend-com/index.md) ## Sources - [Ora score page for suprsend.com](https://ora.ai/score/suprsend.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=suprsend), read 4 November 2026 - [SuprSend website](https://suprsend.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "SurfacedBy AI MCP server | Agent MCP Directory" description: "SurfacedBy AI has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/surfacedby-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SurfacedBy AI MCP server | Agent MCP Directory > SurfacedBy AI has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/surfacedby-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # SurfacedBy AI: MCP server, CLI and agent surfaces Yes: SurfacedBy AI runs a public MCP server at api.surfacedby.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: surfacedby\_inspect\_page\_evidence, surfacedby\_analyze\_answer\_evidence, surfacedby\_check\_ai\_crawler\_access. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | SurfacedBy AI (registry title: SurfacedBy AI Visibility & GEO Audit) | | --- | --- | | Domain | surfacedby.com | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for surfacedby.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.surfacedby.com/api/v1/mcp/public/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | SurfacedBy AI Visibility Audit 1.28.1 | | Capabilities | experimental, prompts, resources, tools | | Tools | 5 | | Resources | 2 | | Prompts | 4 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,952 ms over 1 attempt | ### Tools listed 5 tools - surfacedby\_inspect\_page\_evidence - surfacedby\_analyze\_answer\_evidence - surfacedby\_check\_ai\_crawler\_access - surfacedby\_get\_ai\_source\_landscape - surfacedby\_plan\_ai\_visibility\_audit ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:47Z https://api.surfacedby.com/api/v1/mcp/public/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1978 ms - 20:04:45Z https://api.surfacedby.com/api/v1/mcp/public/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1952 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.surfacedby.com/api/v1/mcp/public/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SurfacedBy AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.surfacedby/ai-visibility | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/surfacedby-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=surfacedby), read 4 November 2026 - [SurfacedBy AI website](https://surfacedby.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Surge MCP server | Agent MCP Directory" description: "Does Surge have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/surge-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Surge MCP server | Agent MCP Directory > Does Surge have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/surge-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Surge: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Surge (surge.app), so the connector had nothing to connect to. Ora's cached score for surge.app is 72, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Surge (registry title: surge.app) | | --- | --- | | Domain | surge.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for surge.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Surge. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for surge.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Surge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/surge-app/index.md) ## Sources - [Ora score page for surge.app](https://ora.ai/score/surge.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/leaderboard) - [Where Surge was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Surge website](https://surge.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Svelte MCP server | Agent MCP Directory" description: "Svelte has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/svelte-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Svelte MCP server | Agent MCP Directory > Svelte has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/svelte-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Svelte: MCP server, CLI and agent surfaces Yes: Svelte runs a public MCP server at mcp.svelte.dev that listed 4 tools to a client with no credentials on 4 November 2026. Examples: get-documentation, list-sections, playground-link. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for svelte.dev is 58, grade C, read on 5 November 2026. ## Fact sheet | Company | Svelte (registry title: Svelte MCP) | | --- | --- | | Domain | svelte.dev | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 58, grade C; Ora scanned the domain on 13 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for svelte.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.svelte.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | Svelte MCP 0.0.1 | | Capabilities | tools, prompts, resources, completions | | Tools | 4 | | Resources | 205 | | Prompts | 1 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,324 ms over 1 attempt | ### Tools listed 4 tools - get-documentation - list-sections - playground-link - svelte-autofixer ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:47Z https://mcp.svelte.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1404 ms - 20:04:44Z https://mcp.svelte.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1324 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.svelte.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Svelte. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.svelte/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/svelte-dev/index.md) ## Sources - [Ora score page for svelte.dev](https://ora.ai/score/svelte.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 13 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=svelte), read 4 November 2026 - [Svelte website](https://svelte.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Svix MCP server | Agent MCP Directory" description: "Svix has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/svix-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Svix MCP server | Agent MCP Directory > Svix has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/svix-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Svix: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Svix; the connector tried mcp.svix.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). ## Fact sheet | Company | Svix (registry title: svix.com) | | --- | --- | | Domain | svix.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 69, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for svix.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.svix.com/mcp | | --- | --- | | How it was found | mcp.svix.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 647 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 no content-type) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:46Z https://mcp.svix.com/mcp sent initialize result no-answer (HTTP 404) 516 ms - 20:04:44Z https://mcp.svix.com/mcp sent initialize result no-answer (HTTP 404) 647 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.svix.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 no content-type). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Svix. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/svix-com/index.md) ## Sources - [Ora score page for svix.com](https://ora.ai/score/svix.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Svix was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Svix website](https://svix.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Swarmia MCP server | Agent MCP Directory" description: "Does Swarmia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/swarmia-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Swarmia MCP server | Agent MCP Directory > Does Swarmia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/swarmia-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Swarmia: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Swarmia (swarmia.com), so the connector had nothing to connect to. Ora's cached score for swarmia.com is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Swarmia (registry title: swarmia.com) | | --- | --- | | Domain | swarmia.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 5 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for swarmia.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Swarmia. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for swarmia.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Swarmia. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/swarmia-com/index.md) ## Sources - [Ora score page for swarmia.com](https://ora.ai/score/swarmia.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 October 2026, read from GET /api/leaderboard) - [Where Swarmia was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Swarmia website](https://swarmia.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Sweep MCP server | Agent MCP Directory" description: "Does Sweep have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/sweep-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sweep MCP server | Agent MCP Directory > Does Sweep have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/sweep-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sweep: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Sweep (sweep.dev), so the connector had nothing to connect to. Ora's cached score for sweep.dev is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Sweep | | --- | --- | | Domain | sweep.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 40, grade D; Ora scanned the domain on 23 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for sweep.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Sweep. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for sweep.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Sweep. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sweep-dev/index.md) ## Sources - [Ora score page for sweep.dev](https://ora.ai/score/sweep.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 August 2026, read from GET /api/leaderboard) - [Where Sweep was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Symbioza MCP server | Agent MCP Directory" description: "Symbioza: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/symbioza-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Symbioza MCP server | Agent MCP Directory > Symbioza: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/symbioza-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Symbioza: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Symbioza at symbioza.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Symbioza | | --- | --- | | Domain | symbioza.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for symbioza.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://symbioza.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 464 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:47Z https://symbioza.dev/mcp sent initialize result auth-required (HTTP 401) 1100 ms - 20:04:44Z https://symbioza.dev/mcp sent initialize result auth-required (HTTP 401) 464 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://symbioza.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | symbioza.dev | | Authorization server metadata | unique-system-07.authkit.app | | Registration endpoint | https://unique-system-07.authkit.app/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://symbioza.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://symbioza.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://unique-system-07.authkit.app/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Symbioza. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.symbioza/symbioza | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/symbioza-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=symbioza), read 4 November 2026 - [Symbioza website](https://symbioza.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "T3 MCP server | Agent MCP Directory" description: "Does T3 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/t3-chat site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # T3 MCP server | Agent MCP Directory > Does T3 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/t3-chat Site: Agent MCP Directory Last reviewed: 2026-11-05 # T3: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for T3 (t3.chat), so the connector had nothing to connect to. Ora's cached score for t3.chat is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | T3 (registry title: t3.chat) | | --- | --- | | Domain | t3.chat | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for t3.chat, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for T3. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for t3.chat, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for T3. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/t3-chat/index.md) ## Sources - [Ora score page for t3.chat](https://ora.ai/score/t3.chat?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/leaderboard) - [Where T3 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TableJourney MCP server | Agent MCP Directory" description: "TableJourney has an open MCP server with 21 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tablejourney-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TableJourney MCP server | Agent MCP Directory > TableJourney has an open MCP server with 21 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tablejourney-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # TableJourney: MCP server, CLI and agent surfaces Yes: TableJourney runs a public MCP server at tablejourney.com that listed 21 tools to a client with no credentials on 4 November 2026. Examples: search\_places, plan\_day, place. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | TableJourney (registry title: TableJourney food travel) | | --- | --- | | Domain | tablejourney.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for tablejourney.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://tablejourney.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | tablejourney 1.0 | | Capabilities | experimental, prompts, resources, tools | | Tools | 21 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,446 ms over 1 attempt | ### Tools listed 21 tools - search\_places - plan\_day - place - festivals - experiences - stays - car\_hire - tickets - things\_to\_do - dishes - itineraries - cities - partner\_join - partner\_confirm - partner\_add\_email - partner\_signin\_code - partner\_signin - partner\_link - partner\_stats - partner\_payout\_method - partner\_confirm\_payout ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:48Z https://tablejourney.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1693 ms - 20:04:46Z https://tablejourney.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1446 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://tablejourney.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for TableJourney. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: tablejourney.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tablejourney/food-travel | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tablejourney-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tablejourney), read 4 November 2026 - [TableJourney website](https://tablejourney.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tabnine MCP server | Agent MCP Directory" description: "Does Tabnine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tabnine-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tabnine MCP server | Agent MCP Directory > Does Tabnine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tabnine-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tabnine: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tabnine (tabnine.com), so the connector had nothing to connect to. Ora's cached score for tabnine.com is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tabnine | | --- | --- | | Domain | tabnine.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tabnine.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tabnine. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tabnine.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tabnine. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tabnine-com/index.md) ## Sources - [Ora score page for tabnine.com](https://ora.ai/score/tabnine.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/leaderboard) - [Where Tabnine was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tailor MCP server | Agent MCP Directory" description: "Does Tailor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tailor-tech site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tailor MCP server | Agent MCP Directory > Does Tailor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tailor-tech Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tailor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tailor (tailor.tech), so the connector had nothing to connect to. Ora's cached score for tailor.tech is 50, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tailor (registry title: tailor.tech) | | --- | --- | | Domain | tailor.tech | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 50, grade C; Ora scanned the domain on 11 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tailor.tech, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tailor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tailor.tech, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tailor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tailor-tech/index.md) ## Sources - [Ora score page for tailor.tech](https://ora.ai/score/tailor.tech?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 September 2026, read from GET /api/leaderboard) - [Where Tailor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tailor website](https://tailor.tech), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tailscale MCP server | Agent MCP Directory" description: "Does Tailscale have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tailscale-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tailscale MCP server | Agent MCP Directory > Does Tailscale have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tailscale-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tailscale: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tailscale (tailscale.com), so the connector had nothing to connect to. Ora's cached score for tailscale.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tailscale | | --- | --- | | Domain | tailscale.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 926 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 22 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for tailscale.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tailscale. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tailscale.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tailscale. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tailscale-com/index.md) ## Sources - [Ora score page for tailscale.com](https://ora.ai/score/tailscale.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 September 2026, read from GET /api/score) - [Where Tailscale was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tailscale website](https://tailscale.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TakeMeUp.cv MCP server | Agent MCP Directory" description: "TakeMeUp.cv has an open MCP server with 54 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/takemeup-cv site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TakeMeUp.cv MCP server | Agent MCP Directory > TakeMeUp.cv has an open MCP server with 54 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/takemeup-cv Site: Agent MCP Directory Last reviewed: 2026-11-05 # TakeMeUp.cv: MCP server, CLI and agent surfaces Yes: TakeMeUp.cv runs a public MCP server at takemeup.cv that listed 54 tools to a client with no credentials on 4 November 2026. Examples: list\_takemeup\_guides, search\_takemeup\_guides, get\_takemeup\_guide. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | TakeMeUp.cv (registry title: TakeMeUp.cv: CV & Resume Builder) | | --- | --- | | Domain | takemeup.cv | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for takemeup.cv when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://takemeup.cv/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | takemeup 0.3.1 | | Capabilities | tools | | Tools | 54 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 644 ms over 1 attempt | ### Tools listed 54 tools; the first 40 names are recorded - list\_takemeup\_guides - search\_takemeup\_guides - get\_takemeup\_guide - list\_takemeup\_cv\_templates - get\_takemeup\_locale\_cv\_rules - get\_takemeup\_pricing - list\_takemeup\_addons - list\_my\_takemeup\_cvs - get\_takemeup\_cv - get\_my\_takemeup\_billing - get\_takemeup\_ai\_consent - get\_takemeup\_download\_access - get\_takemeup\_addon\_runs - analyze\_takemeup\_cv\_ats - check\_takemeup\_cv\_gdpr - export\_takemeup\_cv\_yaml - create\_takemeup\_cv - create\_takemeup\_cv\_from\_role - save\_takemeup\_cv - set\_takemeup\_cv\_template - run\_takemeup\_authenticity - match\_takemeup\_cv\_to\_job - rewrite\_takemeup\_cv - generate\_takemeup\_cover\_letter - run\_takemeup\_interview\_prep - explain\_takemeup\_career\_gaps - run\_takemeup\_career\_gps - check\_takemeup\_resume\_aging - detect\_takemeup\_buzzwords - generate\_takemeup\_cv\_summary - generate\_takemeup\_linkedin - translate\_takemeup\_cv - roast\_takemeup\_cv - run\_takemeup\_market\_pulse - extract\_takemeup\_jd\_from\_url - export\_takemeup\_europass - create\_takemeup\_share\_link - create\_takemeup\_stealth\_cv - revoke\_takemeup\_stealth\_cv - subscribe\_takemeup\_job\_alerts ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:48Z https://takemeup.cv/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1044 ms - 20:04:45Z https://takemeup.cv/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 644 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://takemeup.cv/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for TakeMeUp.cv. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: cv.takemeup/takemeup | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/takemeup-cv/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=takemeup), read 4 November 2026 - [TakeMeUp.cv website](https://takemeup.cv), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tallyfy MCP server | Agent MCP Directory" description: "Tallyfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/tallyfy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tallyfy MCP server | Agent MCP Directory > Tallyfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/tallyfy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tallyfy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Tallyfy at mcp.tallyfy.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Tallyfy (registry title: Tallyfy Workflow Automation) | | --- | --- | | Domain | tallyfy.com | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for tallyfy.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tallyfy.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,318 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:48Z https://mcp.tallyfy.com/ sent initialize result auth-required (HTTP 401) 1295 ms - 20:04:46Z https://mcp.tallyfy.com/ sent initialize result auth-required (HTTP 401) 1318 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://mcp.tallyfy.com", resource_metadata="https://mcp.tallyfy.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="No bearer token was presented. This endpoint requires an OAuth 2.1 access token. Discover the authorization server at https://mcp.tallyfy.com/.well-known/oauth-protected-resource, complete the OAuth flow, then retry the request with an Authorization: Bearer header." | | Protected resource metadata | mcp.tallyfy.com | | Authorization server metadata | mcp.tallyfy.com | | Registration endpoint | https://mcp.tallyfy.com/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.tallyfy.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tallyfy.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.tallyfy.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tallyfy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tallyfy/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tallyfy-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tallyfy), read 4 November 2026 - [Tallyfy website](https://tallyfy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Taloflow MCP server | Agent MCP Directory" description: "Does Taloflow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/taloflow-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Taloflow MCP server | Agent MCP Directory > Does Taloflow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/taloflow-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Taloflow: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Taloflow (taloflow.ai), so the connector had nothing to connect to. Ora's cached score for taloflow.ai is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Taloflow (registry title: taloflow.ai) | | --- | --- | | Domain | taloflow.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for taloflow.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Taloflow. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for taloflow.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Taloflow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/taloflow-ai/index.md) ## Sources - [Ora score page for taloflow.ai](https://ora.ai/score/taloflow.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Taloflow was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Taloflow website](https://taloflow.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tana MCP server | Agent MCP Directory" description: "Does Tana have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/tana-inc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tana MCP server | Agent MCP Directory > Does Tana have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/tana-inc Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tana: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tana (tana.inc), so the connector had nothing to connect to. Ora's cached score for tana.inc is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tana (registry title: tana.inc) | | --- | --- | | Domain | tana.inc | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tana.inc, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tana. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tana.inc, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tana. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tana-inc/index.md) ## Sources - [Ora score page for tana.inc](https://ora.ai/score/tana.inc?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/leaderboard) - [Where Tana was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tana website](https://tana.inc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tapcart MCP server | Agent MCP Directory" description: "Tapcart: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing." canonical: https://agentmcpdirectory.com/directory/tapcart-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tapcart MCP server | Agent MCP Directory > Tapcart: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Marketing. Source: https://agentmcpdirectory.com/directory/tapcart-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tapcart: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Tapcart at mcp.tapcart.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Tapcart | | --- | --- | | Domain | tapcart.com | | Category | Marketing (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 56, grade C; Ora scanned the domain on 7 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tapcart.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tapcart.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,278 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:49Z https://mcp.tapcart.com/mcp sent initialize result auth-required (HTTP 401) 739 ms - 20:04:47Z https://mcp.tapcart.com/mcp sent initialize result auth-required (HTTP 401) 1278 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.tapcart.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.tapcart.com | | Authorization server metadata | mcp.tapcart.com | | Registration endpoint | https://mcp.tapcart.com/mcp/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.tapcart.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tapcart.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.tapcart.com/mcp/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tapcart. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tapcart/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tapcart-com/index.md) ## Sources - [Ora score page for tapcart.com](https://ora.ai/score/tapcart.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 August 2026, read from GET /api/leaderboard) - [Where Tapcart was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.tapcart%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tapcart), read 4 November 2026 - [Tapcart website](https://tapcart.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Taplio MCP server | Agent MCP Directory" description: "Taplio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/taplio-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Taplio MCP server | Agent MCP Directory > Taplio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/taplio-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Taplio: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Taplio at mcp.taplio.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Taplio (registry title: Taplio for LinkedIn) | | --- | --- | | Domain | taplio.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for taplio.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.taplio.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 802 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:49Z https://mcp.taplio.com/ sent initialize result auth-required (HTTP 401) 1071 ms - 20:04:46Z https://mcp.taplio.com/ sent initialize result auth-required (HTTP 401) 802 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="taplio:mcp", resource_metadata="https://mcp.taplio.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.taplio.com | | Authorization server metadata | mcp.taplio.com | | Registration endpoint | https://mcp.taplio.com/register | ### The sign-in route, step by step 1. Request `https://mcp.taplio.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.taplio.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.taplio.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Taplio. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/taplio-com/index.md) ## Sources - [Where Taplio was found](https://github.com/mcp/TaplioOfficial/taplio-linkedin-mcp), read 4 November 2026 - [Taplio website](https://taplio.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TapTax MCP server | Agent MCP Directory" description: "TapTax has an open MCP server with 49 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/taptax-co-uk site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TapTax MCP server | Agent MCP Directory > TapTax has an open MCP server with 49 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/taptax-co-uk Site: Agent MCP Directory Last reviewed: 2026-11-05 # TapTax: MCP server, CLI and agent surfaces Yes: TapTax runs a public MCP server at api.taptax.co.uk that listed 49 tools to a client with no credentials on 4 November 2026. Examples: estimate\_self\_employed\_tax, check\_tax\_code, check\_mtd\_status. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | TapTax | | --- | --- | | Domain | taptax.co.uk | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for taptax.co.uk when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.taptax.co.uk/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | taptax 1.1.0 | | Capabilities | tools, resources | | Tools | 49 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,314 ms over 1 attempt | ### Tools listed 49 tools; the first 40 names are recorded - estimate\_self\_employed\_tax - check\_tax\_code - check\_mtd\_status - get\_mtd\_deadlines - calculate\_take\_home\_pay - calculate\_gross\_salary\_for\_take\_home - calculate\_salary\_sacrifice - calculate\_pro\_rata\_salary - convert\_hourly\_rate\_to\_salary - convert\_salary\_to\_hourly\_rate - calculate\_student\_loan\_repayment - calculate\_child\_benefit\_charge - calculate\_tax\_on\_multiple\_incomes - calculate\_pension\_tax\_relief - calculate\_dividend\_tax - compare\_salary\_and\_dividends - compare\_limited\_company\_and\_sole\_trader - calculate\_corporation\_tax - calculate\_contractor\_day\_rate - compare\_inside\_and\_outside\_ir35 - calculate\_cis\_deduction - plan\_quarterly\_tax\_set\_aside - calculate\_mileage\_allowance - estimate\_self\_assessment\_penalties - calculate\_vat - check\_vat\_registration - check\_vat\_reverse\_charge - calculate\_markup - calculate\_profit\_margin - calculate\_invoice\_due\_date - calculate\_late\_payment\_interest - calculate\_capital\_gains\_tax - calculate\_rental\_income\_tax - calculate\_savings\_interest\_tax - calculate\_stamp\_duty - prepare\_business\_document - generate\_invoice\_numbers - get\_tax\_position - list\_transactions - get\_mileage\_summary ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:50Z https://api.taptax.co.uk/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1564 ms - 20:04:47Z https://api.taptax.co.uk/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1314 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.taptax.co.uk/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for TapTax. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/taptax-co-uk/index.md) ## Sources - [TapTax website](https://taptax.co.uk), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Taskfolk MCP server | Agent MCP Directory" description: "Taskfolk: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/taskfolk-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Taskfolk MCP server | Agent MCP Directory > Taskfolk: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/taskfolk-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Taskfolk: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Taskfolk at taskfolk.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Taskfolk | | --- | --- | | Domain | taskfolk.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for taskfolk.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://taskfolk.ai/api/mcp/v1 | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 602 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:49Z https://taskfolk.ai/api/mcp/v1 sent initialize result auth-required (HTTP 401) 537 ms - 20:04:47Z https://taskfolk.ai/api/mcp/v1 sent initialize result auth-required (HTTP 401) 602 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="taskfolk-product", resource_metadata="https://taskfolk.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | taskfolk.ai | | Authorization server metadata | taskfolk.ai | | Registration endpoint | https://taskfolk.ai/api/oauth/register | ### The sign-in route, step by step 1. Request `https://taskfolk.ai/api/mcp/v1` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://taskfolk.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://taskfolk.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Taskfolk. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: taskfolk.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.taskfolk/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/taskfolk-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=taskfolk), read 4 November 2026 - [Taskfolk website](https://taskfolk.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tavus MCP server | Agent MCP Directory" description: "Tavus: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tavus-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tavus MCP server | Agent MCP Directory > Tavus: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tavus-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tavus: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Tavus; the connector's guess at mcp.tavus.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Tavus (registry title: tavus.io) | | --- | --- | | Domain | tavus.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 76, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tavus.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tavus.io/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 165 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:49Z https://mcp.tavus.io/mcp sent initialize result auth-required (HTTP 401) 283 ms - 20:04:46Z https://mcp.tavus.io/mcp sent initialize result auth-required (HTTP 401) 165 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing, expired, or invalid access token", resource_metadata="https://mcp.tavus.io/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.tavus.io | | Authorization server metadata | mcp.tavus.io | | Registration endpoint | https://mcp.tavus.io/register | ### The sign-in route, step by step 1. Request `https://mcp.tavus.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tavus.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.tavus.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tavus. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tavus-io/index.md) ## Sources - [Ora score page for tavus.io](https://ora.ai/score/tavus.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Tavus was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tavus website](https://tavus.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Taxapp MCP server | Agent MCP Directory" description: "Taxapp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/taxapp-nz site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Taxapp MCP server | Agent MCP Directory > Taxapp: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/taxapp-nz Site: Agent MCP Directory Last reviewed: 2026-11-05 # Taxapp: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Taxapp at mcp.taxapp.nz answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Taxapp (registry title: taxapp.nz) | | --- | --- | | Domain | taxapp.nz | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for taxapp.nz when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.taxapp.nz/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 4,375 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:56Z https://mcp.taxapp.nz/mcp sent initialize result auth-required (HTTP 401) 6535 ms - 20:04:51Z https://mcp.taxapp.nz/mcp sent initialize result auth-required (HTTP 401) 4375 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.taxapp.nz/.well-known/oauth-protected-resource/mcp", scope="taxapp" | | Protected resource metadata | mcp.taxapp.nz | | Authorization server metadata | api.taxapp.nz | | Registration endpoint | https://api.taxapp.nz/api/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.taxapp.nz/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.taxapp.nz/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.taxapp.nz/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Taxapp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/taxapp-nz/index.md) ## Sources - [Taxapp website](https://taxapp.nz), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Teamwork.com MCP server | Agent MCP Directory" description: "Teamwork.com: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/teamwork-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Teamwork.com MCP server | Agent MCP Directory > Teamwork.com: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/teamwork-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Teamwork.com: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Teamwork.com at mcp.ai.teamwork.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Teamwork.com | | --- | --- | | Domain | teamwork.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 68, grade C; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for teamwork.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.ai.teamwork.com/sse | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | sse | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 918 ms over 2 attempts | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 4 connections on 4 November 2026, read-only methods only - 19:59:51Z https://mcp.ai.teamwork.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result initialized-no-tools (HTTP 200) 1664 ms - 19:59:52Z https://mcp.ai.teamwork.com/sse sent initialize result auth-required (HTTP 401) 950 ms - 20:04:51Z https://mcp.ai.teamwork.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result initialized-no-tools (HTTP 200) 4284 ms - 20:04:52Z https://mcp.ai.teamwork.com/sse sent initialize result auth-required (HTTP 401) 918 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.ai.teamwork.com | | Authorization server metadata | teamwork.com | | Registration endpoint | https://www.teamwork.com/developer/api/v1/apps/register.json | ### The sign-in route, step by step 1. Request `https://mcp.ai.teamwork.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.teamwork.com/developer/api/v1/apps/register.json` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Teamwork.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: teamwork.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Found: teamwork.com/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: teamwork.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.teamwork/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/teamwork-com/index.md) ## Sources - [Ora score page for teamwork.com](https://ora.ai/score/teamwork.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where Teamwork.com was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.teamwork%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=teamwork), read 4 November 2026 - [Teamwork.com website](https://teamwork.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Techfabric MCP server | Agent MCP Directory" description: "Techfabric has an open MCP server with 36 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/techfabric-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Techfabric MCP server | Agent MCP Directory > Techfabric has an open MCP server with 36 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/techfabric-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Techfabric: MCP server, CLI and agent surfaces Yes: Techfabric runs a public MCP server at www.techfabric.com that listed 36 tools to a client with no credentials on 4 November 2026. Examples: search, get\_page, list\_posts. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Techfabric (registry title: Databricks Field Guide by TechFabric) | | --- | --- | | Domain | techfabric.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for techfabric.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.techfabric.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | techfabric-blog 1.6.0 | | Capabilities | tools, prompts, resources, extensions, completions | | Tools | 36 | | Resources | 374 | | Prompts | 21 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,284 ms over 1 attempt | ### Tools listed 36 tools - search - get\_page - list\_posts - get\_services - explore\_post - compare\_case\_studies - assess\_databricks\_readiness - quiz\_me - visualize - get\_brief - lint\_draft - check\_draft - submit\_draft - update\_draft - list\_drafts - get\_status - review\_before\_publishing - publish\_draft - preview\_draft - revise\_post - start\_post - check\_outline - propose\_edits - apply\_edits - ask\_author - social\_post\_kit - lint\_social - reddit\_post\_kit - post\_performance - suggest\_links\_and\_topics - preview\_diagram - get\_brief\_pool - propose\_brief - open\_editor - request\_image\_upload - place\_image ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:51Z https://www.techfabric.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2100 ms - 20:04:48Z https://www.techfabric.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1284 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.techfabric.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Techfabric. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.techfabric.databricks/field-guide, com.techfabric/techfabric | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/techfabric-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=techfabric), read 4 November 2026 - [Techfabric website](https://techfabric.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Telnyx MCP server | Agent MCP Directory" description: "Telnyx has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/telnyx-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Telnyx MCP server | Agent MCP Directory > Telnyx has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/telnyx-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Telnyx: MCP server, CLI and agent surfaces Yes: Telnyx runs a public MCP server at api.telnyx.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: get\_api\_endpoint\_schema, list\_api\_endpoints, invoke\_api\_endpoint. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for telnyx.com is 99, grade A+, read on 5 November 2026. ## Fact sheet | Company | Telnyx | | --- | --- | | Domain | telnyx.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 99, grade A+; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for telnyx.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.telnyx.com/v2/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | telnyx_api 3.0.0 | | Capabilities | tools, logging, resources | | Tools | 6 | | Resources | 3 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,162 ms over 1 attempt | ### Tools listed 6 tools - get\_api\_endpoint\_schema - list\_api\_endpoints - invoke\_api\_endpoint - open\_number\_intelligence - open\_usage\_cost\_explorer - open\_voice\_monitor ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:51Z https://api.telnyx.com/v2/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1126 ms - 20:04:48Z https://api.telnyx.com/v2/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1162 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://api.telnyx.com/v2/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Telnyx. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: telnyx.com (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: telnyx.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: telnyx.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: telnyx.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/telnyx-com/index.md) ## Sources - [Ora score page for telnyx.com](https://ora.ai/score/telnyx.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where Telnyx was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Telnyx website](https://telnyx.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TempGuru MCP server | Agent MCP Directory" description: "TempGuru has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tempguru-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TempGuru MCP server | Agent MCP Directory > TempGuru has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tempguru-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # TempGuru: MCP server, CLI and agent surfaces Yes: TempGuru runs a public MCP server at mcp.tempguru.co that listed 12 tools to a client with no credentials on 4 November 2026. Examples: plan\_staffing, save\_staffing\_plan, get\_plan. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | TempGuru (registry title: TempGuru Event Staffing) | | --- | --- | | Domain | tempguru.co | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for tempguru.co when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tempguru.co/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | tempguru-mcp 1.7.3 | | Capabilities | tools, resources, prompts | | Tools | 12 | | Resources | 8 | | Prompts | 2 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,408 ms over 1 attempt | ### Tools listed 12 tools - plan\_staffing - save\_staffing\_plan - get\_plan - get\_cities - get\_roles - check\_availability - get\_role\_pricing - get\_compliance\_by\_state - get\_policies - get\_rate\_benchmark - request\_quote - get\_quote\_status ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:51Z https://mcp.tempguru.co/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1588 ms - 20:04:49Z https://mcp.tempguru.co/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1408 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.tempguru.co/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for TempGuru. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: co.tempguru/event-staffing | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tempguru-co/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tempguru), read 4 November 2026 - [TempGuru website](https://tempguru.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tempo MCP server | Agent MCP Directory" description: "Tempo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tempo-new site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tempo MCP server | Agent MCP Directory > Tempo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tempo-new Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tempo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Tempo; the connector's guess at mcp.tempo.new answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Tempo (registry title: tempo.new) | | --- | --- | | Domain | tempo.new | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 68, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tempo.new, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tempo.new/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,129 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:52Z https://mcp.tempo.new/mcp sent initialize result auth-required (HTTP 401) 1747 ms - 20:04:49Z https://mcp.tempo.new/mcp sent initialize result auth-required (HTTP 401) 1129 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.tempo.new/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.tempo.new | | Authorization server metadata | clerk.auth.tempo.build | | Registration endpoint | https://clerk.auth.tempo.build/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.tempo.new/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tempo.new/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.auth.tempo.build/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tempo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tempo-new/index.md) ## Sources - [Ora score page for tempo.new](https://ora.ai/score/tempo.new?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Tempo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tempo website](https://tempo.new), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Temporal MCP server | Agent MCP Directory" description: "Does Temporal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/temporal-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Temporal MCP server | Agent MCP Directory > Does Temporal have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/temporal-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Temporal: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Temporal (temporal.io), so the connector had nothing to connect to. Ora's cached score for temporal.io is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Temporal | | --- | --- | | Domain | temporal.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for temporal.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Temporal. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for temporal.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Temporal. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/temporal-io/index.md) ## Sources - [Ora score page for temporal.io](https://ora.ai/score/temporal.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Temporal was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Temporal website](https://temporal.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tenet Industries MCP server | Agent MCP Directory" description: "Tenet Industries: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/tenetindustries-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tenet Industries MCP server | Agent MCP Directory > Tenet Industries: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/tenetindustries-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tenet Industries: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Tenet Industries at tenetindustries.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Tenet Industries | | --- | --- | | Domain | tenetindustries.com | | Category | Hardware & Robotics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 58, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tenetindustries.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://tenetindustries.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 428 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:52Z https://tenetindustries.com/mcp sent initialize result auth-required (HTTP 401) 608 ms - 20:04:49Z https://tenetindustries.com/mcp sent initialize result auth-required (HTTP 401) 428 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://tenetindustries.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | tenetindustries.com | | Authorization server metadata | tenetindustries.com | | Registration endpoint | https://tenetindustries.com/register | ### The sign-in route, step by step 1. Request `https://tenetindustries.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://tenetindustries.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://tenetindustries.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tenet Industries. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: tenetindustries.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tenetindustries/tenet | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tenetindustries-com/index.md) ## Sources - [Ora score page for tenetindustries.com](https://ora.ai/score/tenetindustries.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Tenet Industries was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.tenetindustries%2Ftenet), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tenetindustries), read 4 November 2026 - [Tenet Industries website](https://tenetindustries.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TensorPool MCP server | Agent MCP Directory" description: "Does TensorPool have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tensorpool-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TensorPool MCP server | Agent MCP Directory > Does TensorPool have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tensorpool-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # TensorPool: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for TensorPool (tensorpool.dev), so the connector had nothing to connect to. Ora's cached score for tensorpool.dev is 35, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | TensorPool (registry title: tensorpool.dev) | | --- | --- | | Domain | tensorpool.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 35, grade D; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tensorpool.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for TensorPool. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tensorpool.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for TensorPool. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tensorpool-dev/index.md) ## Sources - [Ora score page for tensorpool.dev](https://ora.ai/score/tensorpool.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 September 2026, read from GET /api/leaderboard) - [Where TensorPool was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [TensorPool website](https://tensorpool.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Termii MCP server | Agent MCP Directory" description: "Does Termii have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/termii-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Termii MCP server | Agent MCP Directory > Does Termii have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/termii-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Termii: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Termii (termii.com), so the connector had nothing to connect to. Ora's cached score for termii.com is 45, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Termii (registry title: termii.com) | | --- | --- | | Domain | termii.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 45, grade D; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for termii.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Termii. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for termii.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Termii. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/termii-com/index.md) ## Sources - [Ora score page for termii.com](https://ora.ai/score/termii.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Termii was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Termii website](https://termii.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Terminal Tax MCP server | Agent MCP Directory" description: "Terminal Tax has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/terminal-tax site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Terminal Tax MCP server | Agent MCP Directory > Terminal Tax has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/terminal-tax Site: Agent MCP Directory Last reviewed: 2026-11-05 # Terminal Tax: MCP server, CLI and agent surfaces Yes: Terminal Tax runs a public MCP server at mcp.terminal.tax that listed 3 tools to a client with no credentials on 4 November 2026. Examples: create\_filing\_session, get\_packet\_schema, continue\_filing\_session. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Terminal Tax | | --- | --- | | Domain | terminal.tax | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for terminal.tax when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.terminal.tax/v1/hosted-mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | terminal-tax 0.337.0 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,402 ms over 1 attempt | ### Tools listed 3 tools - create\_filing\_session - get\_packet\_schema - continue\_filing\_session ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:54Z https://mcp.terminal.tax/v1/hosted-mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2021 ms - 20:04:50Z https://mcp.terminal.tax/v1/hosted-mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1402 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.terminal.tax/v1/hosted-mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Terminal Tax. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/terminal-tax/index.md) ## Sources - [Terminal Tax website](https://terminal.tax), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Terminal Use MCP server | Agent MCP Directory" description: "Does Terminal Use have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/terminaluse-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Terminal Use MCP server | Agent MCP Directory > Does Terminal Use have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/terminaluse-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Terminal Use: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Terminal Use (terminaluse.com), so the connector had nothing to connect to. Ora's cached score for terminaluse.com is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Terminal Use (registry title: terminaluse.com) | | --- | --- | | Domain | terminaluse.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 8 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for terminaluse.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Terminal Use. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for terminaluse.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Terminal Use. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/terminaluse-com/index.md) ## Sources - [Ora score page for terminaluse.com](https://ora.ai/score/terminaluse.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 September 2026, read from GET /api/leaderboard) - [Where Terminal Use was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Terminal Use website](https://terminaluse.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Terrateam MCP server | Agent MCP Directory" description: "Does Terrateam have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/terrateam-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Terrateam MCP server | Agent MCP Directory > Does Terrateam have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/terrateam-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Terrateam: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Terrateam (terrateam.io), so the connector had nothing to connect to. Ora's cached score for terrateam.io is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Terrateam (registry title: terrateam.io) | | --- | --- | | Domain | terrateam.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 1 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for terrateam.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Terrateam. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for terrateam.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Terrateam. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/terrateam-io/index.md) ## Sources - [Ora score page for terrateam.io](https://ora.ai/score/terrateam.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 September 2026, read from GET /api/leaderboard) - [Where Terrateam was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Terrateam website](https://terrateam.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tesorio MCP server | Agent MCP Directory" description: "Tesorio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/tesorio-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tesorio MCP server | Agent MCP Directory > Tesorio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/tesorio-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tesorio: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Tesorio at mcp.tesorio.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Tesorio (registry title: tesorio.com) | | --- | --- | | Domain | tesorio.com | | Category | Payments & Fintech (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 38, grade D; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tesorio.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tesorio.com/v1/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,090 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:54Z https://mcp.tesorio.com/v1/mcp sent initialize result auth-required (HTTP 401) 1245 ms - 20:04:50Z https://mcp.tesorio.com/v1/mcp sent initialize result auth-required (HTTP 401) 1090 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.tesorio.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.tesorio.com | | Authorization server metadata | mcp.tesorio.com | | Registration endpoint | https://mcp.tesorio.com/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.tesorio.com/v1/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tesorio.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.tesorio.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tesorio. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tesorio/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tesorio-com/index.md) ## Sources - [Ora score page for tesorio.com](https://ora.ai/score/tesorio.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/leaderboard) - [Where Tesorio was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.tesorio%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tesorio), read 4 November 2026 - [Tesorio website](https://tesorio.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "testRigor MCP server | Agent MCP Directory" description: "testRigor: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/testrigor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # testRigor MCP server | Agent MCP Directory > testRigor: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/testrigor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # testRigor: MCP server, CLI and agent surfaces Not counted. The endpoint listed for testRigor at api2.testrigor.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | testRigor (registry title: testrigor.com) | | --- | --- | | Domain | testrigor.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Credential wall | | Ora score | 56, grade C; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for testrigor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api2.testrigor.com/api/v1/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,117 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:54Z https://api2.testrigor.com/api/v1/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1228 ms - 20:04:50Z https://api2.testrigor.com/api/v1/mcp sent initialize result auth-required-no-oauth (HTTP 401) 1117 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://api2.testrigor.com/api/v1/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for testRigor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.testrigor/mcp-server | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/testrigor-com/index.md) ## Sources - [Ora score page for testrigor.com](https://ora.ai/score/testrigor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/leaderboard) - [Where testRigor was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.testrigor%2Fmcp-server), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=testrigor), read 4 November 2026 - [testRigor website](https://testrigor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Texel.ai MCP server | Agent MCP Directory" description: "Does Texel.ai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/texel-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Texel.ai MCP server | Agent MCP Directory > Does Texel.ai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/texel-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Texel.ai: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Texel.ai (texel.ai), so the connector had nothing to connect to. Ora's cached score for texel.ai is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Texel.ai | | --- | --- | | Domain | texel.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 9 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for texel.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Texel.ai. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for texel.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Texel.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/texel-ai/index.md) ## Sources - [Ora score page for texel.ai](https://ora.ai/score/texel.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 October 2026, read from GET /api/leaderboard) - [Where Texel.ai was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Texel.ai website](https://texel.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "The Bridge MCP server | Agent MCP Directory" description: "The Bridge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/thebridge-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # The Bridge MCP server | Agent MCP Directory > The Bridge: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/thebridge-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # The Bridge: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for The Bridge at api.thebridge.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | The Bridge | | --- | --- | | Domain | thebridge.dev | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for thebridge.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.thebridge.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 672 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:54Z https://api.thebridge.dev/mcp sent initialize result auth-required (HTTP 401) 597 ms - 20:04:51Z https://api.thebridge.dev/mcp sent initialize result auth-required (HTTP 401) 672 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | Protected resource metadata | api.thebridge.dev | | Authorization server metadata | api.thebridge.dev | | Registration endpoint | https://api.thebridge.dev/mcp/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.thebridge.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.thebridge.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.thebridge.dev/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for The Bridge. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.thebridge/bridge | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thebridge-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=thebridge), read 4 November 2026 - [The Bridge website](https://thebridge.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "The Context Company MCP server | Agent MCP Directory" description: "The Context Company: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/thecontext-company site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # The Context Company MCP server | Agent MCP Directory > The Context Company: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/thecontext-company Site: Agent MCP Directory Last reviewed: 2026-11-05 # The Context Company: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for The Context Company; the connector's guess at mcp.thecontext.company answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | The Context Company | | --- | --- | | Domain | thecontext.company | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 58, grade C; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for thecontext.company, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.thecontext.company/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 911 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:55Z https://mcp.thecontext.company/mcp sent initialize result auth-required (HTTP 401) 1878 ms - 20:04:51Z https://mcp.thecontext.company/mcp sent initialize result auth-required (HTTP 401) 911 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://api.thecontext.company/.well-known/oauth-protected-resource" | | Protected resource metadata | api.thecontext.company | | Authorization server metadata | auth.thecontextcompany.com | | Registration endpoint | https://auth.thecontextcompany.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.thecontext.company/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.thecontext.company/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.thecontextcompany.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for The Context Company. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thecontext-company/index.md) ## Sources - [Ora score page for thecontext.company](https://ora.ai/score/thecontext.company?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/leaderboard) - [Where The Context Company was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [The Context Company website](https://thecontext.company), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Kollektiv MCP server | Agent MCP Directory" description: "Kollektiv has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/thekollektiv-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Kollektiv MCP server | Agent MCP Directory > Kollektiv has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/thekollektiv-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kollektiv: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for Kollektiv (mcp.thekollektiv.ai), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: ENOTFOUND. The row is kept so the claim is visible and can be re-checked next edition. ## Fact sheet | Company | Kollektiv | | --- | --- | | Domain | thekollektiv.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for thekollektiv.ai when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.thekollektiv.ai/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 3 ms over 1 attempt | | Result | ENOTFOUND | ### Connector log 3 connections on 4 November 2026, read-only methods only - 19:59:54Z https://mcp.thekollektiv.ai/sse sent initialize result no-answer 82 ms - 20:04:51Z https://mcp.thekollektiv.ai/sse sent initialize result no-answer 3 ms - 20:04:51Z https://mcp.thekollektiv.ai/mcp sent initialize result no-answer 5 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | Oauth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.thekollektiv.ai/sse`. The connector could not tell what it wants: ENOTFOUND. 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Kollektiv. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thekollektiv-ai/index.md) ## Sources - [Where Kollektiv was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Kollektiv website](https://thekollektiv.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Theneo MCP server | Agent MCP Directory" description: "Theneo has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/theneo-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Theneo MCP server | Agent MCP Directory > Theneo has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/theneo-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Theneo: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Theneo; the connector tried mcp.theneo.io as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 502, GET HTTP 502 text/html; charset=utf-8). ## Fact sheet | Company | Theneo (registry title: theneo.io) | | --- | --- | | Domain | theneo.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 67, grade C; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for theneo.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.theneo.io/mcp | | --- | --- | | How it was found | mcp.theneo.io was tried as a guess and did not answer | | HTTP status | 502 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 417 ms over 2 attempts | | Result | no MCP answer (POST HTTP 502, GET HTTP 502 text/html; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:55Z https://mcp.theneo.io/mcp sent initialize result no-answer (HTTP 502) 465 ms - 20:04:51Z https://mcp.theneo.io/mcp sent initialize result no-answer (HTTP 502) 417 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.theneo.io/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 502, GET HTTP 502 text/html; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Theneo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/theneo-io/index.md) ## Sources - [Ora score page for theneo.io](https://ora.ai/score/theneo.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/leaderboard) - [Where Theneo was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Theneo website](https://theneo.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Pulse MCP server | Agent MCP Directory" description: "Pulse has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/thepulse-markets site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Pulse MCP server | Agent MCP Directory > Pulse has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/thepulse-markets Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pulse: MCP server, CLI and agent surfaces Yes: Pulse runs a public MCP server at mcp.thepulse.markets that listed 9 tools to a client with no credentials on 4 November 2026. Examples: get\_index\_price, get\_index\_batch, list\_index\_assets. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Pulse (registry title: Pulse Verity) | | --- | --- | | Domain | thepulse.markets | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for thepulse.markets when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.thepulse.markets/api/index/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | pulse-verity 1.1.0 | | Capabilities | tools | | Tools | 9 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,277 ms over 1 attempt | ### Tools listed 9 tools - get\_index\_price - get\_index\_batch - list\_index\_assets - get\_recorded\_print - verify\_print - get\_account\_status - get\_index\_history - get\_upgrade\_options - submit\_verity\_feedback ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:56Z https://mcp.thepulse.markets/api/index/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2046 ms - 20:04:52Z https://mcp.thepulse.markets/api/index/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1277 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.thepulse.markets/api/index/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Pulse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thepulse-markets/index.md) ## Sources - [Where Pulse was found](https://github.com/mcp/PulseBet/pulse-verity), read 4 November 2026 - [Pulse website](https://thepulse.markets), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "There's An AI For That MCP server | Agent MCP Directory" description: "There's An AI For That has an open MCP server with 37 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/theresanaiforthat-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # There's An AI For That MCP server | Agent MCP Directory > There's An AI For That has an open MCP server with 37 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/theresanaiforthat-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # There's An AI For That: MCP server, CLI and agent surfaces Yes: There's An AI For That runs a public MCP server at theresanaiforthat.com that listed 37 tools to a client with no credentials on 4 November 2026. Examples: search\_tools, get\_tool, search\_deals. It speaks streamable-http, protocol 2026-07-28. Ora's cached score for theresanaiforthat.com is 9, grade F, read on 5 November 2026. ## Fact sheet | Company | There's An AI For That | | --- | --- | | Domain | theresanaiforthat.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 9, grade F; Ora scanned the domain on 23 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for theresanaiforthat.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://theresanaiforthat.com/mcp-server/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | There's An AI For That 1.5.0 | | Capabilities | tools | | Tools | 37 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,115 ms over 1 attempt | ### Tools listed 37 tools - search\_tools - get\_tool - search\_deals - get\_deal - search\_tasks - get\_task - search\_models - get\_model - search\_companies - get\_company - search\_robots - get\_robot - search\_devices - get\_device - search\_organizations - get\_organization - search\_investors - get\_investor - search\_countries - get\_country - search\_events - get\_event - search\_fundraises - get\_fundraise - search\_papers - get\_paper - search\_repositories - get\_repository - search\_mcps - get\_mcp - search\_news - get\_news - search\_breakthroughs - get\_breakthrough - list\_features - list\_feature\_tools - list\_feature\_models ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:56Z https://theresanaiforthat.com/mcp-server/ sent initialize, notifications/initialized, tools/list result initialized-no-tools (HTTP 200) 1153 ms - 20:04:52Z https://theresanaiforthat.com/mcp-server/ sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1115 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://theresanaiforthat.com/mcp-server/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for There's An AI For That. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.theresanaiforthat/taaft | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/theresanaiforthat-com/index.md) ## Sources - [Ora score page for theresanaiforthat.com](https://ora.ai/score/theresanaiforthat.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=theresanaiforthat), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "The Token Company MCP server | Agent MCP Directory" description: "Does The Token Company have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/thetokencompany-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # The Token Company MCP server | Agent MCP Directory > Does The Token Company have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/thetokencompany-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # The Token Company: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for The Token Company (thetokencompany.com), so the connector had nothing to connect to. Ora's cached score for thetokencompany.com is 72, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | The Token Company (registry title: thetokencompany.com) | | --- | --- | | Domain | thetokencompany.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for thetokencompany.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for The Token Company. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for thetokencompany.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for The Token Company. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: thetokencompany.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thetokencompany-com/index.md) ## Sources - [Ora score page for thetokencompany.com](https://ora.ai/score/thetokencompany.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where The Token Company was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [The Token Company website](https://thetokencompany.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "The White Report MCP server | Agent MCP Directory" description: "The White Report has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/thewhitereport-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # The White Report MCP server | Agent MCP Directory > The White Report has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/thewhitereport-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # The White Report: MCP server, CLI and agent surfaces Yes: The White Report runs a public MCP server at thewhitereport.com that listed 12 tools to a client with no credentials on 4 November 2026. Examples: get\_latest, search\_articles, get\_article. It speaks streamable-http, protocol 2026-07-28. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | The White Report | | --- | --- | | Domain | thewhitereport.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for thewhitereport.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://thewhitereport.com/mcp.php | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2026-07-28 | | Server | white-report 0.1.0 | | Capabilities | tools | | Tools | 12 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 3,250 ms over 1 attempt | ### Tools listed 12 tools - get\_latest - search\_articles - get\_article - get\_ticker - get\_scoreboard - calls\_list - calls\_get - calls\_since - event\_briefs\_list - event\_brief\_get - telemetry\_latest - telemetry\_series ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:59Z https://thewhitereport.com/mcp.php sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 3778 ms - 20:04:54Z https://thewhitereport.com/mcp.php sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 3250 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://thewhitereport.com/mcp.php` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for The White Report. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thewhitereport-com/index.md) ## Sources - [The White Report website](https://thewhitereport.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ThoughtSpot MCP server | Agent MCP Directory" description: "ThoughtSpot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/thoughtspot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ThoughtSpot MCP server | Agent MCP Directory > ThoughtSpot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/thoughtspot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ThoughtSpot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ThoughtSpot at agent.thoughtspot.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ThoughtSpot | | --- | --- | | Domain | thoughtspot.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 61, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for thoughtspot.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agent.thoughtspot.app/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 432 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:56Z https://agent.thoughtspot.app/mcp sent initialize result auth-required (HTTP 401) 703 ms - 20:04:52Z https://agent.thoughtspot.app/mcp sent initialize result auth-required (HTTP 401) 432 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token" | | Authorization server metadata | agent.thoughtspot.app | | Registration endpoint | https://agent.thoughtspot.app/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://agent.thoughtspot.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://agent.thoughtspot.app/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ThoughtSpot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thoughtspot-com/index.md) ## Sources - [Ora score page for thoughtspot.com](https://ora.ai/score/thoughtspot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/leaderboard) - [Where ThoughtSpot was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [ThoughtSpot website](https://thoughtspot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ThousandEyes MCP server | Agent MCP Directory" description: "ThousandEyes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/thousandeyes-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ThousandEyes MCP server | Agent MCP Directory > ThousandEyes: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/thousandeyes-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ThousandEyes: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for ThousandEyes at api.thousandeyes.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | ThousandEyes (registry title: ThousandEyes MCP) | | --- | --- | | Domain | thousandeyes.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,194 on the list of 4 November 2026 | | Ora score | 42, grade D; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for thousandeyes.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.thousandeyes.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,031 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:59Z https://api.thousandeyes.com/mcp sent initialize result auth-required (HTTP 401) 976 ms - 20:01:35Z https://api.thousandeyes.com/mcp sent initialize result auth-required (HTTP 401) 1031 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.thousandeyes.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.thousandeyes.com | | Authorization server metadata | api.thousandeyes.com | | Registration endpoint | https://api.thousandeyes.com/v7/oauth2/clients | ### The sign-in route, step by step 1. Request `https://api.thousandeyes.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.thousandeyes.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.thousandeyes.com/v7/oauth2/clients` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ThousandEyes. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.thousandeyes/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thousandeyes-com/index.md) ## Sources - [Ora score page for thousandeyes.com](https://ora.ai/score/thousandeyes.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/score) - [Where ThousandEyes was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.thousandeyes%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=thousandeyes), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Thunder Compute MCP server | Agent MCP Directory" description: "Does Thunder Compute have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/thundercompute-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Thunder Compute MCP server | Agent MCP Directory > Does Thunder Compute have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/thundercompute-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Thunder Compute: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Thunder Compute (thundercompute.com), so the connector had nothing to connect to. Ora's cached score for thundercompute.com is 76, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Thunder Compute (registry title: thundercompute.com) | | --- | --- | | Domain | thundercompute.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 76, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for thundercompute.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Thunder Compute. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for thundercompute.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Thunder Compute. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thundercompute-com/index.md) ## Sources - [Ora score page for thundercompute.com](https://ora.ai/score/thundercompute.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Thunder Compute was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Thunder Compute website](https://thundercompute.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Thunkable MCP server | Agent MCP Directory" description: "Does Thunkable have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/thunkable-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Thunkable MCP server | Agent MCP Directory > Does Thunkable have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/thunkable-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Thunkable: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Thunkable (thunkable.com), so the connector had nothing to connect to. Ora's cached score for thunkable.com is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Thunkable (registry title: thunkable.com) | | --- | --- | | Domain | thunkable.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for thunkable.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Thunkable. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for thunkable.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Thunkable. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/thunkable-com/index.md) ## Sources - [Ora score page for thunkable.com](https://ora.ai/score/thunkable.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Thunkable was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Thunkable website](https://thunkable.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TickTick MCP server | Agent MCP Directory" description: "TickTick has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/ticktick-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TickTick MCP server | Agent MCP Directory > TickTick has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/ticktick-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # TickTick: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for TickTick; the connector tried mcp.ticktick.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | TickTick (registry title: ticktick.com) | | --- | --- | | Domain | ticktick.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Tranco rank | 8,005 on the list of 4 November 2026 | | Ora score | 61, grade C; Ora scanned the domain on 31 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for ticktick.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.ticktick.com/mcp | | --- | --- | | How it was found | mcp.ticktick.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,496 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:14Z https://mcp.ticktick.com/mcp sent initialize result no-answer (HTTP 404) 1422 ms - 20:01:53Z https://mcp.ticktick.com/mcp sent initialize result no-answer (HTTP 404) 1496 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.ticktick.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for TickTick. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: ticktick.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ticktick-com/index.md) ## Sources - [Ora score page for ticktick.com](https://ora.ai/score/ticktick.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 August 2026, read from GET /api/score) - [Where TickTick was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [TickTick website](https://ticktick.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tilda MCP server | Agent MCP Directory" description: "Does Tilda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tilda-cc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tilda MCP server | Agent MCP Directory > Does Tilda have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tilda-cc Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tilda: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tilda (tilda.cc), so the connector had nothing to connect to. Ora's cached score for tilda.cc is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tilda (registry title: tilda.cc) | | --- | --- | | Domain | tilda.cc | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 12 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tilda.cc, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tilda. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tilda.cc, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tilda. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tilda-cc/index.md) ## Sources - [Ora score page for tilda.cc](https://ora.ai/score/tilda.cc?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 12 October 2026, read from GET /api/leaderboard) - [Where Tilda was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tilda website](https://tilda.cc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Time Doctor MCP server | Agent MCP Directory" description: "Does Time Doctor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/timedoctor-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Time Doctor MCP server | Agent MCP Directory > Does Time Doctor have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/timedoctor-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Time Doctor: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Time Doctor (timedoctor.com), so the connector had nothing to connect to. Ora's cached score for timedoctor.com is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Time Doctor (registry title: timedoctor.com) | | --- | --- | | Domain | timedoctor.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 6 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for timedoctor.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Time Doctor. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for timedoctor.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Time Doctor. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/timedoctor-com/index.md) ## Sources - [Ora score page for timedoctor.com](https://ora.ai/score/timedoctor.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 August 2026, read from GET /api/leaderboard) - [Where Time Doctor was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Time Doctor website](https://timedoctor.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Timely MCP server | Agent MCP Directory" description: "Does Timely have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/timely-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Timely MCP server | Agent MCP Directory > Does Timely have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/timely-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Timely: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Timely (timely.com), so the connector had nothing to connect to. Ora's cached score for timely.com is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Timely (registry title: timely.com) | | --- | --- | | Domain | timely.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 19 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for timely.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Timely. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for timely.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Timely. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/timely-com/index.md) ## Sources - [Ora score page for timely.com](https://ora.ai/score/timely.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 August 2026, read from GET /api/leaderboard) - [Where Timely was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Timely website](https://timely.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tiptap MCP server | Agent MCP Directory" description: "Does Tiptap have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tiptap-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tiptap MCP server | Agent MCP Directory > Does Tiptap have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tiptap-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tiptap: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tiptap (tiptap.dev), so the connector had nothing to connect to. Ora's cached score for tiptap.dev is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tiptap (registry title: tiptap.dev) | | --- | --- | | Domain | tiptap.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 30 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tiptap.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tiptap. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tiptap.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tiptap. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tiptap-dev/index.md) ## Sources - [Ora score page for tiptap.dev](https://ora.ai/score/tiptap.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 September 2026, read from GET /api/leaderboard) - [Where Tiptap was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tiptap website](https://tiptap.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "tl;dv MCP server | Agent MCP Directory" description: "tl;dv: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tldv-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # tl;dv MCP server | Agent MCP Directory > tl;dv: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tldv-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # tl;dv: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for tl;dv at mcp.tldv.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | tl;dv | | --- | --- | | Domain | tldv.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 51, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for tldv.io, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tldv.io/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 615 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:57Z https://mcp.tldv.io/mcp sent initialize result auth-required (HTTP 401) 546 ms - 20:04:53Z https://mcp.tldv.io/mcp sent initialize result auth-required (HTTP 401) 615 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.tldv.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.tldv.io | | Authorization server metadata | keycloak.tldv.io | | Registration endpoint | https://keycloak.tldv.io/realms/mcp.tldv.io/clients-registrations/openid-connect | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.tldv.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tldv.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://keycloak.tldv.io/realms/mcp.tldv.io/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for tl;dv. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tldv-io/index.md) ## Sources - [Ora score page for tldv.io](https://ora.ai/score/tldv.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/score) - [Where tl;dv was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [tl;dv website](https://tldv.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Todoist (todoist.com) MCP server | Agent MCP Directory" description: "Todoist (todoist.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/todoist-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Todoist (todoist.com) MCP server | Agent MCP Directory > Todoist (todoist.com): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/todoist-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Todoist: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Todoist at ai.todoist.net answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Todoist (registry title: Doist) | | --- | --- | | Domain | todoist.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,099 on the list of 4 November 2026 | | Ora score | 67, grade C; Ora scanned the domain on 7 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for todoist.com, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.todoist.net/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,710 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:05Z https://ai.todoist.net/mcp sent initialize result auth-required (HTTP 401) 1598 ms - 20:01:41Z https://ai.todoist.net/mcp sent initialize result auth-required (HTTP 401) 1710 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://ai.todoist.net/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | ai.todoist.net | | Authorization server metadata | todoist.com | | Registration endpoint | https://todoist.com/oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://ai.todoist.net/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://ai.todoist.net/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://todoist.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Todoist. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: todoist.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/todoist-com/index.md) ## Sources - [Ora score page for todoist.com](https://ora.ai/score/todoist.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 October 2026, read from GET /api/score) - [Where Todoist was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Todoist website](https://todoist.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Todoist (todoist.net) MCP server | Agent MCP Directory" description: "Todoist (todoist.net): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/todoist-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Todoist (todoist.net) MCP server | Agent MCP Directory > Todoist (todoist.net): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/todoist-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # Todoist: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Todoist at ai.todoist.net answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Todoist | | --- | --- | | Domain | todoist.net | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for todoist.net when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.todoist.net/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,618 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:58Z https://ai.todoist.net/mcp sent initialize result auth-required (HTTP 401) 1666 ms - 20:04:54Z https://ai.todoist.net/mcp sent initialize result auth-required (HTTP 401) 1618 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://ai.todoist.net/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | ai.todoist.net | | Authorization server metadata | todoist.com | | Registration endpoint | https://todoist.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://ai.todoist.net/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://ai.todoist.net/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://todoist.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Todoist. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/todoist-net/index.md) ## Sources - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Toggl MCP server | Agent MCP Directory" description: "Does Toggl have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/toggl-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Toggl MCP server | Agent MCP Directory > Does Toggl have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/toggl-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Toggl: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Toggl (toggl.com), so the connector had nothing to connect to. Ora's cached score for toggl.com is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Toggl (registry title: toggl.com) | | --- | --- | | Domain | toggl.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for toggl.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Toggl. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for toggl.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Toggl. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/toggl-com/index.md) ## Sources - [Ora score page for toggl.com](https://ora.ai/score/toggl.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where Toggl was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Toggl website](https://toggl.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tomiseregi MCP server | Agent MCP Directory" description: "Tomiseregi has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tomiseregi-si site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tomiseregi MCP server | Agent MCP Directory > Tomiseregi has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tomiseregi-si Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tomiseregi: MCP server, CLI and agent surfaces Yes: Tomiseregi runs a public MCP server at god-prompt-mcp.tomi-seregi99.workers.dev that listed 7 tools to a client with no credentials on 4 November 2026. Examples: get\_god\_prompt, get\_core\_skill, get\_protocols. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Tomiseregi (registry title: GodPrompt MCP Server) | | --- | --- | | Domain | tomiseregi.si | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for tomiseregi.si when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://god-prompt-mcp.tomi-seregi99.workers.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | god-prompt-mcp 1.0.44 | | Capabilities | tools, resources, extensions | | Tools | 7 | | Resources | 4 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 186 ms over 1 attempt | ### Tools listed 7 tools - get\_god\_prompt - get\_core\_skill - get\_protocols - get\_gates - get\_anti\_patterns - classify\_task - get\_version ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:57Z https://god-prompt-mcp.tomi-seregi99.workers.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 286 ms - 20:04:53Z https://god-prompt-mcp.tomi-seregi99.workers.dev/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 186 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://god-prompt-mcp.tomi-seregi99.workers.dev/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tomiseregi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tomiseregi-si/index.md) ## Sources - [Where Tomiseregi was found](https://github.com/mcp/AKzar1el/god-prompt-mcp), read 4 November 2026 - [Tomiseregi website](https://tomiseregi.si), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TracePass MCP server | Agent MCP Directory" description: "TracePass has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tracepass-eu site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TracePass MCP server | Agent MCP Directory > TracePass has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tracepass-eu Site: Agent MCP Directory Last reviewed: 2026-11-05 # TracePass: MCP server, CLI and agent surfaces Yes: TracePass runs a public MCP server at ai.tracepass.eu that listed 8 tools to a client with no credentials on 4 November 2026. Examples: tracepass\_products, tracepass\_passports, tracepass\_passport\_fields. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | TracePass | | --- | --- | | Domain | tracepass.eu | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for tracepass.eu when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://ai.tracepass.eu/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | tracepass 1.24.0 | | Capabilities | tools, resources, prompts | | Tools | 8 | | Resources | 2 | | Prompts | 5 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 866 ms over 1 attempt | ### Tools listed 8 tools - tracepass\_products - tracepass\_passports - tracepass\_passport\_fields - tracepass\_passport\_parties - tracepass\_epcis - tracepass\_templates - tracepass\_scope - tracepass\_passport\_lifecycle ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:58Z https://ai.tracepass.eu/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 962 ms - 20:04:54Z https://ai.tracepass.eu/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 866 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://ai.tracepass.eu/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for TracePass. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.tracepass.eu (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: eu.tracepass/compliance, eu.tracepass/tracepass | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Yes: malinoto/tracepass-mcp-server | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tracepass-eu/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tracepass), read 4 November 2026 - [TracePass website](https://tracepass.eu), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Trackjs MCP server | Agent MCP Directory" description: "Does Trackjs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trackjs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Trackjs MCP server | Agent MCP Directory > Does Trackjs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trackjs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Trackjs: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Trackjs (trackjs.com), so the connector had nothing to connect to. Ora's cached score for trackjs.com is 55, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Trackjs (registry title: trackjs.com) | | --- | --- | | Domain | trackjs.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 55, grade C; Ora scanned the domain on 11 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trackjs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Trackjs. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trackjs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Trackjs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trackjs-com/index.md) ## Sources - [Ora score page for trackjs.com](https://ora.ai/score/trackjs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 October 2026, read from GET /api/leaderboard) - [Where Trackjs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Trackjs website](https://trackjs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Trainloop AI MCP server | Agent MCP Directory" description: "Does Trainloop AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trainloop-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Trainloop AI MCP server | Agent MCP Directory > Does Trainloop AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trainloop-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Trainloop AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Trainloop AI (trainloop.ai), so the connector had nothing to connect to. Ora's cached score for trainloop.ai is 51, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Trainloop AI | | --- | --- | | Domain | trainloop.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 51, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trainloop.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Trainloop AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trainloop.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Trainloop AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trainloop-ai/index.md) ## Sources - [Ora score page for trainloop.ai](https://ora.ai/score/trainloop.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Trainloop AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Trainloop AI website](https://trainloop.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Trainy MCP server | Agent MCP Directory" description: "Does Trainy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trainy-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Trainy MCP server | Agent MCP Directory > Does Trainy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trainy-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Trainy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Trainy (trainy.ai), so the connector had nothing to connect to. Ora's cached score for trainy.ai is 77, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Trainy (registry title: trainy.ai) | | --- | --- | | Domain | trainy.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 77, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trainy.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Trainy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trainy.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Trainy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trainy-ai/index.md) ## Sources - [Ora score page for trainy.ai](https://ora.ai/score/trainy.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Trainy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Trainy website](https://trainy.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Traveler.md MCP server | Agent MCP Directory" description: "Traveler.md: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/traveler-md site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Traveler.md MCP server | Agent MCP Directory > Traveler.md: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/traveler-md Site: Agent MCP Directory Last reviewed: 2026-11-05 # Traveler.md: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Traveler.md at mcp.traveler.md answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Traveler.md | | --- | --- | | Domain | traveler.md | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 28 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for traveler.md, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.traveler.md/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,401 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:59Z https://mcp.traveler.md/mcp sent initialize result auth-required (HTTP 401) 1770 ms - 20:04:55Z https://mcp.traveler.md/mcp sent initialize result auth-required (HTTP 401) 1401 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.traveler.md/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.traveler.md | | Authorization server metadata | connect.traveler.md | | Registration endpoint | https://connect.traveler.md/v1/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.traveler.md/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.traveler.md/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://connect.traveler.md/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Traveler.md. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: traveler.md (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/traveler-md/index.md) ## Sources - [Ora score page for traveler.md](https://ora.ai/score/traveler.md?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 August 2026, read from GET /api/score) - [Traveler.md website](https://traveler.md), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Travis CI MCP server | Agent MCP Directory" description: "Does Travis CI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/travis-ci-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Travis CI MCP server | Agent MCP Directory > Does Travis CI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/travis-ci-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Travis CI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Travis CI (travis-ci.com), so the connector had nothing to connect to. Ora's cached score for travis-ci.com is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Travis CI (registry title: travis-ci.com) | | --- | --- | | Domain | travis-ci.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 16 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for travis-ci.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Travis CI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for travis-ci.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Travis CI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/travis-ci-com/index.md) ## Sources - [Ora score page for travis-ci.com](https://ora.ai/score/travis-ci.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 September 2026, read from GET /api/leaderboard) - [Where Travis CI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Travis CI website](https://travis-ci.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tray.ai MCP server | Agent MCP Directory" description: "Does Tray.ai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tray-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tray.ai MCP server | Agent MCP Directory > Does Tray.ai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tray-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tray.ai: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tray.ai (tray.io), so the connector had nothing to connect to. Ora's cached score for tray.io is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tray.ai (registry title: tray.io) | | --- | --- | | Domain | tray.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 10 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tray.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tray.ai. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tray.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tray.ai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tray-io/index.md) ## Sources - [Ora score page for tray.io](https://ora.ai/score/tray.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 September 2026, read from GET /api/leaderboard) - [Where Tray.ai was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tray.ai website](https://tray.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Treza MCP server | Agent MCP Directory" description: "Treza: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trezalabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Treza MCP server | Agent MCP Directory > Treza: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/trezalabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Treza: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Treza at www.trezalabs.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Treza | | --- | --- | | Domain | trezalabs.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for trezalabs.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.trezalabs.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 932 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:01Z https://www.trezalabs.com/api/mcp sent initialize result auth-required (HTTP 401) 2565 ms - 20:04:55Z https://www.trezalabs.com/api/mcp sent initialize result auth-required (HTTP 401) 932 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", scope="pipelines:read pipelines:run pipelines:write keys:provision", resource_metadata="https://www.trezalabs.com/.well-known/oauth-protected-resource" | | Protected resource metadata | www.trezalabs.com | | Authorization server metadata | www.trezalabs.com | | Registration endpoint | https://www.trezalabs.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://www.trezalabs.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.trezalabs.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.trezalabs.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Treza. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.trezalabs.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trezalabs-com/index.md) ## Sources - [Treza website](https://trezalabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "trivago MCP server | Agent MCP Directory" description: "trivago has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trivago-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # trivago MCP server | Agent MCP Directory > trivago has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/trivago-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # trivago: MCP server, CLI and agent surfaces Yes: trivago runs a public MCP server at mcp.trivago.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: trivago-accommodation-radius-search, trivago-accommodation-search, trivago-destination-price-trends. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for trivago.com is 55, grade C, read on 5 November 2026. ## Fact sheet | Company | trivago | | --- | --- | | Domain | trivago.com | | Category | Travel & Hospitality (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 55, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for trivago.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.trivago.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | trivago Accommodation Search 0.6.0 | | Capabilities | resources, tools | | Tools | 3 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 831 ms over 1 attempt | ### Tools listed 3 tools - trivago-accommodation-radius-search - trivago-accommodation-search - trivago-destination-price-trends ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:00Z https://mcp.trivago.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 962 ms - 20:04:55Z https://mcp.trivago.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 831 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.trivago.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for trivago. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.trivago.mcp/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trivago-com/index.md) ## Sources - [Ora score page for trivago.com](https://ora.ai/score/trivago.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where trivago was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.trivago.mcp%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=trivago), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Trivy MCP server | Agent MCP Directory" description: "Does Trivy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trivy-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Trivy MCP server | Agent MCP Directory > Does Trivy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trivy-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Trivy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Trivy (trivy.dev), so the connector had nothing to connect to. Ora's cached score for trivy.dev is 34, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Trivy (registry title: trivy.dev) | | --- | --- | | Domain | trivy.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 34, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trivy.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Trivy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trivy.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Trivy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trivy-dev/index.md) ## Sources - [Ora score page for trivy.dev](https://ora.ai/score/trivy.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Trivy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Trivy website](https://trivy.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Truthifi MCP server | Agent MCP Directory" description: "Truthifi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/truthifi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Truthifi MCP server | Agent MCP Directory > Truthifi: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/truthifi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Truthifi: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Truthifi at api.truthifi.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Truthifi | | --- | --- | | Domain | truthifi.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for truthifi.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.truthifi.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,220 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:01Z https://api.truthifi.com/mcp sent initialize result auth-required (HTTP 401) 1702 ms - 20:04:56Z https://api.truthifi.com/mcp sent initialize result auth-required (HTTP 401) 1220 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="mcp", resource_metadata="https://api.truthifi.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | api.truthifi.com | | Authorization server metadata | api.truthifi.com | | Registration endpoint | https://api.truthifi.com/oauth/register | ### The sign-in route, step by step 1. Request `https://api.truthifi.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.truthifi.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.truthifi.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Truthifi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.truthifi/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/truthifi-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=truthifi), read 4 November 2026 - [Truthifi website](https://truthifi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Truthsystems MCP server | Agent MCP Directory" description: "Does Truthsystems have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/truthsystems-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Truthsystems MCP server | Agent MCP Directory > Does Truthsystems have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/truthsystems-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Truthsystems: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Truthsystems (truthsystems.ai), so the connector had nothing to connect to. Ora's cached score for truthsystems.ai is 37, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Truthsystems (registry title: truthsystems.ai) | | --- | --- | | Domain | truthsystems.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 37, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for truthsystems.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Truthsystems. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for truthsystems.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Truthsystems. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/truthsystems-ai/index.md) ## Sources - [Ora score page for truthsystems.ai](https://ora.ai/score/truthsystems.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Truthsystems was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Truthsystems website](https://truthsystems.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Adlicio MCP server | Agent MCP Directory" description: "Adlicio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/tryadlicio-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Adlicio MCP server | Agent MCP Directory > Adlicio: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/tryadlicio-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Adlicio: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Adlicio at mcp.tryadlicio.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Adlicio | | --- | --- | | Domain | tryadlicio.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 64, grade C; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for tryadlicio.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tryadlicio.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 513 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:00Z https://mcp.tryadlicio.com/mcp sent initialize result auth-required (HTTP 401) 630 ms - 20:04:55Z https://mcp.tryadlicio.com/mcp sent initialize result auth-required (HTTP 401) 513 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required for Adlicio MCP", resource_metadata="https://mcp.tryadlicio.com/.well-known/oauth-protected-resource/mcp", scope="mcp:tools" | | Protected resource metadata | mcp.tryadlicio.com | | Authorization server metadata | mcp.tryadlicio.com | | Registration endpoint | https://mcp.tryadlicio.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.tryadlicio.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tryadlicio.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.tryadlicio.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Adlicio. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: tryadlicio.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tryadlicio/adlicio | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tryadlicio-com/index.md) ## Sources - [Ora score page for tryadlicio.com](https://ora.ai/score/tryadlicio.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tryadlicio), read 4 November 2026 - [Adlicio website](https://tryadlicio.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ardent MCP server | Agent MCP Directory" description: "Does Ardent have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tryardent-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ardent MCP server | Agent MCP Directory > Does Ardent have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tryardent-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ardent: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ardent (tryardent.com), so the connector had nothing to connect to. Ora's cached score for tryardent.com is 71, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ardent (registry title: tryardent.com) | | --- | --- | | Domain | tryardent.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 71, grade B; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tryardent.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ardent. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tryardent.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ardent. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tryardent-com/index.md) ## Sources - [Ora score page for tryardent.com](https://ora.ai/score/tryardent.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where Ardent was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ardent website](https://tryardent.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Channel3 MCP server | Agent MCP Directory" description: "Channel3 has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trychannel3-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Channel3 MCP server | Agent MCP Directory > Channel3 has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/trychannel3-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Channel3: MCP server, CLI and agent surfaces Yes: Channel3 runs a public MCP server at mcp.trychannel3.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: search\_products, get\_products, browse\_products. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for trychannel3.com is 92, grade A, read on 5 November 2026. ## Fact sheet | Company | Channel3 (registry title: Channel3 Shopping) | | --- | --- | | Domain | trychannel3.com | | Category | E-commerce (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 92, grade A; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for trychannel3.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.trychannel3.com/ | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Channel3 4.0.0 | | Capabilities | tools, prompts, resources | | Tools | 6 | | Resources | 1 | | Prompts | 6 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 370 ms over 1 attempt | ### Tools listed 6 tools - search\_products - get\_products - browse\_products - get\_similar - get\_details - get\_price\_history ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:01Z https://mcp.trychannel3.com/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 730 ms - 20:04:56Z https://mcp.trychannel3.com/ sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 370 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.trychannel3.com/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Channel3. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.trychannel3/shopping | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trychannel3-com/index.md) ## Sources - [Ora score page for trychannel3.com](https://ora.ai/score/trychannel3.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Where Channel3 was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.trychannel3%2Fshopping), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=trychannel3), read 4 November 2026 - [Channel3 website](https://trychannel3.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Keet MCP server | Agent MCP Directory" description: "Does Keet have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/trykeet-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Keet MCP server | Agent MCP Directory > Does Keet have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/trykeet-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Keet: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Keet (trykeet.com), so the connector had nothing to connect to. Ora's cached score for trykeet.com is 53, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Keet (registry title: trykeet.com) | | --- | --- | | Domain | trykeet.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 53, grade C; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trykeet.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Keet. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trykeet.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Keet. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trykeet-com/index.md) ## Sources - [Ora score page for trykeet.com](https://ora.ai/score/trykeet.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/leaderboard) - [Where Keet was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Keet website](https://trykeet.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Maitai MCP server | Agent MCP Directory" description: "Does Maitai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trymaitai-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Maitai MCP server | Agent MCP Directory > Does Maitai have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trymaitai-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Maitai: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Maitai (trymaitai.com), so the connector had nothing to connect to. Ora's cached score for trymaitai.com is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Maitai (registry title: trymaitai.com) | | --- | --- | | Domain | trymaitai.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trymaitai.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Maitai. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trymaitai.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Maitai. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trymaitai-com/index.md) ## Sources - [Ora score page for trymaitai.com](https://ora.ai/score/trymaitai.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where Maitai was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Maitai website](https://trymaitai.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Maven MCP server | Agent MCP Directory" description: "Does Maven have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trymaven-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Maven MCP server | Agent MCP Directory > Does Maven have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trymaven-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Maven: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Maven (trymaven.com), so the connector had nothing to connect to. Ora's cached score for trymaven.com is 61, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Maven (registry title: trymaven.com) | | --- | --- | | Domain | trymaven.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 61, grade C; Ora scanned the domain on 5 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trymaven.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Maven. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trymaven.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Maven. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trymaven-com/index.md) ## Sources - [Ora score page for trymaven.com](https://ora.ai/score/trymaven.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 September 2026, read from GET /api/leaderboard) - [Where Maven was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Maven website](https://trymaven.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Mito MCP server | Agent MCP Directory" description: "Does Mito have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/trymito-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Mito MCP server | Agent MCP Directory > Does Mito have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/trymito-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mito: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Mito (trymito.io), so the connector had nothing to connect to. Ora's cached score for trymito.io is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Mito (registry title: trymito.io) | | --- | --- | | Domain | trymito.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trymito.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Mito. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trymito.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Mito. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trymito-io/index.md) ## Sources - [Ora score page for trymito.io](https://ora.ai/score/trymito.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/leaderboard) - [Where Mito was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Mito website](https://trymito.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Trynia MCP server | Agent MCP Directory" description: "Does Trynia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trynia-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Trynia MCP server | Agent MCP Directory > Does Trynia have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trynia-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Trynia: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Trynia (trynia.ai), so the connector had nothing to connect to. Ora's cached score for trynia.ai is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Trynia (registry title: trynia.ai) | | --- | --- | | Domain | trynia.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 1 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trynia.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Trynia. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trynia.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Trynia. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trynia-ai/index.md) ## Sources - [Ora score page for trynia.ai](https://ora.ai/score/trynia.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 October 2026, read from GET /api/leaderboard) - [Where Trynia was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Oids MCP server | Agent MCP Directory" description: "Oids: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/tryoids-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Oids MCP server | Agent MCP Directory > Oids: a credential wall with no OAuth metadata, so Agent MCP Directory does not count it as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/tryoids-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Oids: MCP server, CLI and agent surfaces Not counted. The endpoint listed for Oids at api.tryoids.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns. ## Fact sheet | Company | Oids | | --- | --- | | Domain | tryoids.com | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Credential wall | | Ora score | none: Ora returned no cached score for tryoids.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.tryoids.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 403 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 541 ms over 1 attempt | The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives. ### Connector log 4 connections on 4 November 2026, read-only methods only - 20:00:01Z https://api.tryoids.com/mcp sent initialize result auth-required-no-oauth (HTTP 403) 703 ms - 20:00:01Z https://mcp.tryoids.com/mcp sent initialize result no-answer 15 ms - 20:04:57Z https://api.tryoids.com/mcp sent initialize result auth-required-no-oauth (HTTP 403) 541 ms - 20:04:57Z https://mcp.tryoids.com/mcp sent initialize result no-answer 3 ms ## Authentication | Auth type | API key | | --- | --- | ### The sign-in route, step by step 1. Request `https://api.tryoids.com/mcp` without a token. It answers with a credential challenge but no OAuth metadata. 2. Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself. 3. Send the key in the header the vendor documents and retry. The connector sends no key. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Oids. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tryoids/agentcitywars, com.tryoids/agentsanddragons, com.tryoids/oids | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tryoids-com/index.md) ## Sources - [Where Oids was found](https://github.com/mcp/oidsdev/oids), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tryoids), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Trypillar MCP server | Agent MCP Directory" description: "Does Trypillar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trypillar-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Trypillar MCP server | Agent MCP Directory > Does Trypillar have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trypillar-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Trypillar: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Trypillar (trypillar.com), so the connector had nothing to connect to. Ora's cached score for trypillar.com is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Trypillar (registry title: trypillar.com) | | --- | --- | | Domain | trypillar.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trypillar.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Trypillar. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trypillar.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Trypillar. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trypillar-com/index.md) ## Sources - [Ora score page for trypillar.com](https://ora.ai/score/trypillar.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Trypillar was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Terracotta MCP server | Agent MCP Directory" description: "Does Terracotta have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tryterracotta-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Terracotta MCP server | Agent MCP Directory > Does Terracotta have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tryterracotta-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Terracotta: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Terracotta (tryterracotta.com), so the connector had nothing to connect to. Ora's cached score for tryterracotta.com is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Terracotta (registry title: tryterracotta.com) | | --- | --- | | Domain | tryterracotta.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tryterracotta.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Terracotta. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tryterracotta.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Terracotta. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tryterracotta-com/index.md) ## Sources - [Ora score page for tryterracotta.com](https://ora.ai/score/tryterracotta.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/leaderboard) - [Where Terracotta was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Terracotta website](https://tryterracotta.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Truffle AI MCP server | Agent MCP Directory" description: "Does Truffle AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/trytruffle-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Truffle AI MCP server | Agent MCP Directory > Does Truffle AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/trytruffle-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Truffle AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Truffle AI (trytruffle.ai), so the connector had nothing to connect to. Ora's cached score for trytruffle.ai is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Truffle AI (registry title: trytruffle.ai) | | --- | --- | | Domain | trytruffle.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for trytruffle.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Truffle AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for trytruffle.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Truffle AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/trytruffle-ai/index.md) ## Sources - [Ora score page for trytruffle.ai](https://ora.ai/score/trytruffle.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Truffle AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Truffle AI website](https://trytruffle.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tumult MCP server | Agent MCP Directory" description: "Does Tumult have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tumult-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tumult MCP server | Agent MCP Directory > Does Tumult have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/tumult-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tumult: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tumult (tumult.com), so the connector had nothing to connect to. Ora's cached score for tumult.com is 35, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tumult (registry title: tumult.com) | | --- | --- | | Domain | tumult.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 35, grade D; Ora scanned the domain on 3 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for tumult.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tumult. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for tumult.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tumult. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tumult-com/index.md) ## Sources - [Ora score page for tumult.com](https://ora.ai/score/tumult.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 October 2026, read from GET /api/leaderboard) - [Where Tumult was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tumult website](https://tumult.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Turbo Notify MCP server | Agent MCP Directory" description: "Turbo Notify has an open MCP server with 36 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/turbonotify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Turbo Notify MCP server | Agent MCP Directory > Turbo Notify has an open MCP server with 36 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/turbonotify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Turbo Notify: MCP server, CLI and agent surfaces Yes: Turbo Notify runs a public MCP server at mcp.turbonotify.com that listed 36 tools to a client with no credentials on 4 November 2026. Examples: send\_text, send\_media, send\_location. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Turbo Notify (registry title: Turbo Notify: WhatsApp for AI agents) | | --- | --- | | Domain | turbonotify.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for turbonotify.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.turbonotify.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | turbo-notify 0.1.0 | | Capabilities | experimental, prompts, resources, tools | | Tools | 36 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 3,674 ms over 1 attempt | ### Tools listed 36 tools - send\_text - send\_media - send\_location - send\_contact\_card - send\_calendar\_event - send\_cta\_button - reply\_to\_message - edit\_text\_message - edit\_media\_caption - edit\_calendar\_event - cancel\_calendar\_event - delete\_message - react\_to\_message - send\_typing\_indicator - mark\_as\_read - list\_messages - get\_message - get\_message\_status - get\_message\_receipts - get\_message\_reactions - get\_message\_responses - get\_message\_quota - list\_contacts - get\_contact - get\_contact\_profile\_picture - refresh\_contact - get\_contact\_quota - list\_groups - get\_group - get\_group\_picture - list\_numbers - get\_number - connect\_number - disconnect\_number - get\_usage - list\_events ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:05Z https://mcp.turbonotify.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3619 ms - 20:05:00Z https://mcp.turbonotify.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3674 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.turbonotify.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Turbo Notify. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.turbonotify/whatsapp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/turbonotify-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=turbonotify), read 4 November 2026 - [Turbo Notify website](https://turbonotify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Turkishtechlab MCP server | Agent MCP Directory" description: "Turkishtechlab: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/turkishtechlab-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Turkishtechlab MCP server | Agent MCP Directory > Turkishtechlab: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/turkishtechlab-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Turkishtechlab: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Turkishtechlab at mcp.turkishtechlab.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Turkishtechlab (registry title: Turkish Technology) | | --- | --- | | Domain | turkishtechlab.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for turkishtechlab.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.turkishtechlab.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 602 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:02Z https://mcp.turkishtechlab.com/mcp sent initialize result auth-required (HTTP 401) 747 ms - 20:04:57Z https://mcp.turkishtechlab.com/mcp sent initialize result auth-required (HTTP 401) 602 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Turkish Airlines MCP", resource_metadata="https://mcp.turkishtechlab.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.turkishtechlab.com | | Authorization server metadata | mcp.turkishtechlab.com | | Registration endpoint | https://mcp.turkishtechlab.com/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.turkishtechlab.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.turkishtechlab.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.turkishtechlab.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Turkishtechlab. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/turkishtechlab-com/index.md) ## Sources - [Where Turkishtechlab was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Turkishtechlab website](https://turkishtechlab.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Turso MCP server | Agent MCP Directory" description: "Does Turso have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/turso-tech site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Turso MCP server | Agent MCP Directory > Does Turso have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/turso-tech Site: Agent MCP Directory Last reviewed: 2026-11-05 # Turso: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Turso (turso.tech), so the connector had nothing to connect to. Ora's cached score for turso.tech is 84, grade B, read on 5 November 2026. An OpenAPI file is published. ## Fact sheet | Company | Turso | | --- | --- | | Domain | turso.tech | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 84, grade B; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for turso.tech, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Turso. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for turso.tech, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Turso. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: turso.tech (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: turso.tech/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: turso.tech/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/turso-tech/index.md) ## Sources - [Ora score page for turso.tech](https://ora.ai/score/turso.tech?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/leaderboard) - [Where Turso was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Turso website](https://turso.tech), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "TweetSave MCP server | Agent MCP Directory" description: "TweetSave has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/tweetsave-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # TweetSave MCP server | Agent MCP Directory > TweetSave has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/tweetsave-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # TweetSave: MCP server, CLI and agent surfaces Yes: TweetSave runs a public MCP server at mcp.tweetsave.org that listed 5 tools to a client with no credentials on 4 November 2026. Examples: tweetsave\_get\_tweet, tweetsave\_get\_thread, tweetsave\_to\_blog. It speaks sse, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | TweetSave | | --- | --- | | Domain | tweetsave.org | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for tweetsave.org when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tweetsave.org/sse | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | sse | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | tweetsave-mcp-server 1.0.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 870 ms over 2 attempts | ### Tools listed 5 tools - tweetsave\_get\_tweet - tweetsave\_get\_thread - tweetsave\_to\_blog - tweetsave\_batch - tweetsave\_extract\_media ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:03Z https://mcp.tweetsave.org/sse sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 791 ms - 20:04:57Z https://mcp.tweetsave.org/sse sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 870 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.tweetsave.org/sse` over sse. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for TweetSave. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tweetsave-org/index.md) ## Sources - [Where TweetSave was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [TweetSave website](https://tweetsave.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Twelfth MCP server | Agent MCP Directory" description: "Twelfth: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM." canonical: https://agentmcpdirectory.com/directory/twelfth-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Twelfth MCP server | Agent MCP Directory > Twelfth: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: CRM. Source: https://agentmcpdirectory.com/directory/twelfth-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Twelfth: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Twelfth at api.twelfth.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Twelfth | | --- | --- | | Domain | twelfth.ai | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 50, grade C; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for twelfth.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.twelfth.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 970 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:03Z https://api.twelfth.ai/mcp sent initialize result auth-required (HTTP 401) 1137 ms - 20:04:58Z https://api.twelfth.ai/mcp sent initialize result auth-required (HTTP 401) 970 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.twelfth.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | api.twelfth.ai | | Authorization server metadata | api.twelfth.ai | | Registration endpoint | https://api.twelfth.ai/api/auth/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.twelfth.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.twelfth.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.twelfth.ai/api/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Twelfth. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: twelfth.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.twelfth/workspace | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/twelfth-ai/index.md) ## Sources - [Ora score page for twelfth.ai](https://ora.ai/score/twelfth.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=twelfth), read 4 November 2026 - [Twelfth website](https://twelfth.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Twelve Data MCP server | Agent MCP Directory" description: "Twelve Data: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech." canonical: https://agentmcpdirectory.com/directory/twelvedata-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Twelve Data MCP server | Agent MCP Directory > Twelve Data: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Payments & Fintech. Source: https://agentmcpdirectory.com/directory/twelvedata-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Twelve Data: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Twelve Data at mcp.twelvedata.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Twelve Data | | --- | --- | | Domain | twelvedata.com | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for twelvedata.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.twelvedata.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 882 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:06Z https://mcp.twelvedata.com/mcp sent initialize result auth-required (HTTP 401) 3966 ms - 20:04:58Z https://mcp.twelvedata.com/mcp sent initialize result auth-required (HTTP 401) 882 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.twelvedata.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.twelvedata.com | | Authorization server metadata | auth.twelvedata.com | | Registration endpoint | https://auth.twelvedata.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.twelvedata.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.twelvedata.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.twelvedata.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Twelve Data. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.twelvedata/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/twelvedata-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=twelvedata), read 4 November 2026 - [Twelve Data website](https://twelvedata.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Twilio MCP server | Agent MCP Directory" description: "Twilio has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/twilio-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Twilio MCP server | Agent MCP Directory > Twilio has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/twilio-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Twilio: MCP server, CLI and agent surfaces Yes: Twilio runs a public MCP server at www.twilio.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: list\_products, get\_product, get\_customer\_stories. It speaks streamable-http, protocol 2025-11-25. A CLI is on record: twilio-cli on npm. ## Fact sheet | Company | Twilio | | --- | --- | | Domain | twilio.com | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 1,118 on the list of 4 November 2026 | | Ora score | 85, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for twilio.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.twilio.com/.well-known/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | twilio-com-public-web-mcp 0.1.0 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,121 ms over 1 attempt | | Documentation | www.twilio.com | ### Tools listed 5 tools - list\_products - get\_product - get\_customer\_stories - get\_customer\_story - list\_use\_cases ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://www.twilio.com/.well-known/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1116 ms - 20:01:32Z https://www.twilio.com/.well-known/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1121 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://www.twilio.com/.well-known/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | twilio-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 7.2.0 | | Last publish | 13 October 2026 | | Command names | twilio | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: twilio.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/twilio-com/index.md) ## Sources - [Ora score page for twilio.com](https://ora.ai/score/twilio.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Twilio website](https://twilio.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "txscribe MCP server | Agent MCP Directory" description: "txscribe: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/txscribe-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # txscribe MCP server | Agent MCP Directory > txscribe: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/txscribe-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # txscribe: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for txscribe at txscribe.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | txscribe | | --- | --- | | Domain | txscribe.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for txscribe.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://txscribe.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 789 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:03Z https://txscribe.ai/mcp sent initialize result auth-required (HTTP 401) 932 ms - 20:04:58Z https://txscribe.ai/mcp sent initialize result auth-required (HTTP 401) 789 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://txscribe.ai/.well-known/oauth-protected-resource/mcp", scope="transcriptions" | | Protected resource metadata | txscribe.ai | | Authorization server metadata | txscribe.ai | | Registration endpoint | https://txscribe.ai/api/oauth/register | ### The sign-in route, step by step 1. Request `https://txscribe.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://txscribe.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://txscribe.ai/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for txscribe. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.txscribe/txscribe | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/txscribe-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=txscribe), read 4 November 2026 - [txscribe website](https://txscribe.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Typeform MCP server | Agent MCP Directory" description: "Typeform: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/typeform-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Typeform MCP server | Agent MCP Directory > Typeform: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/typeform-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Typeform: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Typeform at api.typeform.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Typeform | | --- | --- | | Domain | typeform.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 1,130 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for typeform.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.typeform.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,335 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:57Z https://api.typeform.com/mcp sent initialize result auth-required (HTTP 401) 1317 ms - 20:01:33Z https://api.typeform.com/mcp sent initialize result auth-required (HTTP 401) 1335 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.typeform.com/.well-known/oauth-protected-resource", scope="accounts:read automations:read automations:write contacts:read contacts:write forms:read forms:write pages:read pages:write responses:read responses:write insights:read packages:read subscriptions:read webhooks:read webhooks:write workspaces:read workspaces:write" | | Protected resource metadata | api.typeform.com | | Authorization server metadata | api.typeform.com | | Registration endpoint | https://api.typeform.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.typeform.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.typeform.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.typeform.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Typeform. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.typeform/typeform | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/typeform-com/index.md) ## Sources - [Ora score page for typeform.com](https://ora.ai/score/typeform.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/score) - [Where Typeform was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.typeform%2Ftypeform), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=typeform), read 4 November 2026 - [Typeform website](https://typeform.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Typewise MCP server | Agent MCP Directory" description: "Does Typewise have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/typewise-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Typewise MCP server | Agent MCP Directory > Does Typewise have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/typewise-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Typewise: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Typewise (typewise.app), so the connector had nothing to connect to. Ora's cached score for typewise.app is 75, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Typewise (registry title: typewise.app) | | --- | --- | | Domain | typewise.app | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 75, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for typewise.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Typewise. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for typewise.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Typewise. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/typewise-app/index.md) ## Sources - [Ora score page for typewise.app](https://ora.ai/score/typewise.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/leaderboard) - [Where Typewise was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Typewise website](https://typewise.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ubicloud MCP server | Agent MCP Directory" description: "Does Ubicloud have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/ubicloud-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ubicloud MCP server | Agent MCP Directory > Does Ubicloud have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/ubicloud-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ubicloud: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ubicloud (ubicloud.com), so the connector had nothing to connect to. Ora's cached score for ubicloud.com is 49, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ubicloud (registry title: ubicloud.com) | | --- | --- | | Domain | ubicloud.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 49, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for ubicloud.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ubicloud. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for ubicloud.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ubicloud. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ubicloud-com/index.md) ## Sources - [Ora score page for ubicloud.com](https://ora.ai/score/ubicloud.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Ubicloud was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ubicloud website](https://ubicloud.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "UiPath MCP server | Agent MCP Directory" description: "Does UiPath have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/uipath-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # UiPath MCP server | Agent MCP Directory > Does UiPath have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/uipath-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # UiPath: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for UiPath (uipath.com), so the connector had nothing to connect to. Ora's cached score for uipath.com is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | UiPath (registry title: uipath.com) | | --- | --- | | Domain | uipath.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for uipath.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for UiPath. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for uipath.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for UiPath. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/uipath-com/index.md) ## Sources - [Ora score page for uipath.com](https://ora.ai/score/uipath.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where UiPath was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [UiPath website](https://uipath.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Uizze MCP server | Agent MCP Directory" description: "Uizze: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/uizze-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Uizze MCP server | Agent MCP Directory > Uizze: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/uizze-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Uizze: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Uizze at uizze.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Uizze | | --- | --- | | Domain | uizze.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for uizze.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://uizze.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 175 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:05Z https://uizze.com/mcp sent initialize result auth-required (HTTP 401) 1265 ms - 20:04:58Z https://uizze.com/mcp sent initialize result auth-required (HTTP 401) 175 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="uizze-mcp", resource_metadata="https://uizze.com/.well-known/oauth-protected-resource/mcp", scope="uizze:mcp" | | Protected resource metadata | uizze.com | | Authorization server metadata | uizze.com | | Registration endpoint | https://uizze.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://uizze.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://uizze.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://uizze.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Uizze. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/uizze-com/index.md) ## Sources - [Where Uizze was found](https://github.com/mcp/uizze/uizze), read 4 November 2026 - [Uizze website](https://uizze.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ulapcybo MCP server | Agent MCP Directory" description: "Ulapcybo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/ulapcybo-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ulapcybo MCP server | Agent MCP Directory > Ulapcybo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/ulapcybo-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ulapcybo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Ulapcybo at attest.ulapcybo.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Ulapcybo (registry title: CYBO Attest) | | --- | --- | | Domain | ulapcybo.app | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for ulapcybo.app when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://attest.ulapcybo.app/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 3,003 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:07Z https://attest.ulapcybo.app/mcp sent initialize result auth-required (HTTP 401) 3168 ms - 20:05:01Z https://attest.ulapcybo.app/mcp sent initialize result auth-required (HTTP 401) 3003 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://attest.ulapcybo.app/.well-known/oauth-protected-resource/mcp", scope="applications:read applications:write scans:write scans:read justifications:write evidence:read" | | Protected resource metadata | attest.ulapcybo.app | | Authorization server metadata | auth.ulapcybo.app | | Registration endpoint | https://auth.ulapcybo.app/auth/realms/alex/clients-registrations/openid-connect | ### The sign-in route, step by step 1. Request `https://attest.ulapcybo.app/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://attest.ulapcybo.app/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.ulapcybo.app/auth/realms/alex/clients-registrations/openid-connect` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ulapcybo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: app.ulapcybo/attest | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ulapcybo-app/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=ulapcybo), read 4 November 2026 - [Ulapcybo website](https://ulapcybo.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ultralayer MCP server | Agent MCP Directory" description: "Ultralayer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/ultralayer-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ultralayer MCP server | Agent MCP Directory > Ultralayer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/ultralayer-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ultralayer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Ultralayer at api.ultralayer.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Ultralayer | | --- | --- | | Domain | ultralayer.ai | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for ultralayer.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.ultralayer.ai/v0/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 728 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:05Z https://api.ultralayer.ai/v0/mcp sent initialize result auth-required (HTTP 401) 1058 ms - 20:04:59Z https://api.ultralayer.ai/v0/mcp sent initialize result auth-required (HTTP 401) 728 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.ultralayer.ai/.well-known/oauth-protected-resource/v0/mcp" | | Protected resource metadata | api.ultralayer.ai | | Authorization server metadata | api.ultralayer.ai | | Registration endpoint | https://api.ultralayer.ai/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.ultralayer.ai/v0/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.ultralayer.ai/.well-known/oauth-protected-resource/v0/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.ultralayer.ai/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ultralayer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/ultralayer-ai/index.md) ## Sources - [Ultralayer website](https://ultralayer.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "unify MCP server | Agent MCP Directory" description: "Does unify have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/unify-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # unify MCP server | Agent MCP Directory > Does unify have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/unify-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # unify: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for unify (unify.ai), so the connector had nothing to connect to. Ora's cached score for unify.ai is 42, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | unify (registry title: unify.ai) | | --- | --- | | Domain | unify.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 42, grade D; Ora scanned the domain on 16 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for unify.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for unify. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for unify.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for unify. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/unify-ai/index.md) ## Sources - [Ora score page for unify.ai](https://ora.ai/score/unify.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 16 October 2026, read from GET /api/leaderboard) - [Where unify was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [unify website](https://unify.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Unlayer MCP server | Agent MCP Directory" description: "Unlayer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/unlayer-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Unlayer MCP server | Agent MCP Directory > Unlayer: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/unlayer-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Unlayer: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Unlayer at api.unlayer.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Unlayer (registry title: Unlayer: Email, Page & Document Templates for Developers) | | --- | --- | | Domain | unlayer.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 40, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for unlayer.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.unlayer.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,335 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:06Z https://api.unlayer.com/mcp sent initialize result auth-required (HTTP 401) 2681 ms - 20:05:00Z https://api.unlayer.com/mcp sent initialize result auth-required (HTTP 401) 1335 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="unlayer-mcp", resource_metadata="https://api.unlayer.com/.well-known/oauth-protected-resource" | | Protected resource metadata | api.unlayer.com | | Authorization server metadata | accounts.unlayer.com | | Registration endpoint | https://accounts.unlayer.com/oauth/register | ### The sign-in route, step by step 1. Request `https://api.unlayer.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.unlayer.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://accounts.unlayer.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Unlayer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.unlayer/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/unlayer-com/index.md) ## Sources - [Ora score page for unlayer.com](https://ora.ai/score/unlayer.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Unlayer was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.unlayer%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=unlayer), read 4 November 2026 - [Unlayer website](https://unlayer.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Unlimitless MCP server | Agent MCP Directory" description: "Unlimitless: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/unlimitless-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Unlimitless MCP server | Agent MCP Directory > Unlimitless: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/unlimitless-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Unlimitless: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Unlimitless at api.unlimitless.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Unlimitless (registry title: Unl) | | --- | --- | | Domain | unlimitless.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for unlimitless.ai when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.unlimitless.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 921 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:06Z https://api.unlimitless.ai/mcp sent initialize result auth-required (HTTP 401) 1377 ms - 20:04:59Z https://api.unlimitless.ai/mcp sent initialize result auth-required (HTTP 401) 921 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.unlimitless.ai/.well-known/oauth-protected-resource/mcp", scope="email profile" | | Protected resource metadata | api.unlimitless.ai | | Authorization server metadata | clerk.unlimitless.ai | | Registration endpoint | https://clerk.unlimitless.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://api.unlimitless.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.unlimitless.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.unlimitless.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Unlimitless. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.unlimitless/unl | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/unlimitless-ai/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=unlimitless), read 4 November 2026 - [Unlimitless website](https://unlimitless.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Unsiloed AI MCP server | Agent MCP Directory" description: "Unsiloed AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/unsiloed-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Unsiloed AI MCP server | Agent MCP Directory > Unsiloed AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/unsiloed-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Unsiloed AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Unsiloed AI; the connector's guess at mcp.unsiloed.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Unsiloed AI | | --- | --- | | Domain | unsiloed.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 60, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for unsiloed.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.unsiloed.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,931 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:07Z https://mcp.unsiloed.ai/mcp sent initialize result auth-required (HTTP 401) 1900 ms - 20:05:00Z https://mcp.unsiloed.ai/mcp sent initialize result auth-required (HTTP 401) 1931 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="unsiloed-mcp", resource_metadata="https://mcp.unsiloed.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.unsiloed.ai | | Authorization server metadata | hydra.unsiloed.ai | | Registration endpoint | https://hydra.unsiloed.ai/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.unsiloed.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.unsiloed.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://hydra.unsiloed.ai/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Unsiloed AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/unsiloed-ai/index.md) ## Sources - [Ora score page for unsiloed.ai](https://ora.ai/score/unsiloed.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/leaderboard) - [Where Unsiloed AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Unsiloed AI website](https://unsiloed.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Unsloth MCP server | Agent MCP Directory" description: "Does Unsloth have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/unsloth-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Unsloth MCP server | Agent MCP Directory > Does Unsloth have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/unsloth-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Unsloth: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Unsloth (unsloth.ai), so the connector had nothing to connect to. Ora's cached score for unsloth.ai is 43, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Unsloth (registry title: unsloth.ai) | | --- | --- | | Domain | unsloth.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 43, grade D; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for unsloth.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Unsloth. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for unsloth.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Unsloth. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/unsloth-ai/index.md) ## Sources - [Ora score page for unsloth.ai](https://ora.ai/score/unsloth.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Unsloth was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Unsloth website](https://unsloth.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Unstructured MCP server | Agent MCP Directory" description: "Unstructured: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/unstructured-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Unstructured MCP server | Agent MCP Directory > Unstructured: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/unstructured-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Unstructured: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Unstructured at mcp.transform.unstructured.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Unstructured (registry title: Unstructured Transform) | | --- | --- | | Domain | unstructured.io | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 73, grade B; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for unstructured.io, a vendor-published score) | | Company found through | the GitHub MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.transform.unstructured.io | | --- | --- | | How it was found | listed in the GitHub MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,655 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:07Z https://mcp.transform.unstructured.io sent initialize result auth-required (HTTP 401) 1673 ms - 20:05:00Z https://mcp.transform.unstructured.io sent initialize result auth-required (HTTP 401) 1655 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://mcp.transform.unstructured.io/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.transform.unstructured.io | | Authorization server metadata | mcp.transform.unstructured.io | | Registration endpoint | https://mcp.transform.unstructured.io/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.transform.unstructured.io` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.transform.unstructured.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.transform.unstructured.io/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Unstructured. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/unstructured-io/index.md) ## Sources - [Ora score page for unstructured.io](https://ora.ai/score/unstructured.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 October 2026, read from GET /api/leaderboard) - [Unstructured website](https://unstructured.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "updown.io MCP server | Agent MCP Directory" description: "Does updown.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/updown-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # updown.io MCP server | Agent MCP Directory > Does updown.io have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/updown-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # updown.io: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for updown.io, so the connector had nothing to connect to. Ora's cached score for updown.io is 33, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | updown.io | | --- | --- | | Domain | updown.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 33, grade D; Ora scanned the domain on 3 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for updown.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for updown.io. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for updown.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for updown.io. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/updown-io/index.md) ## Sources - [Ora score page for updown.io](https://ora.ai/score/updown.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 September 2026, read from GET /api/leaderboard) - [Where updown.io was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [updown.io website](https://updown.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Upload-Post MCP server | Agent MCP Directory" description: "Upload-Post: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media." canonical: https://agentmcpdirectory.com/directory/upload-post-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Upload-Post MCP server | Agent MCP Directory > Upload-Post: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Gaming & Media. Source: https://agentmcpdirectory.com/directory/upload-post-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Upload-Post: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Upload-Post at mcp.upload-post.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Upload-Post | | --- | --- | | Domain | upload-post.com | | Category | Gaming & Media (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for upload-post.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.upload-post.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 468 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:06Z https://mcp.upload-post.com/mcp sent initialize result auth-required (HTTP 401) 642 ms - 20:05:00Z https://mcp.upload-post.com/mcp sent initialize result auth-required (HTTP 401) 468 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="upload-post", resource_metadata="https://mcp.upload-post.com/.well-known/oauth-protected-resource", ApiKey realm="upload-post" | | Protected resource metadata | mcp.upload-post.com | | Authorization server metadata | mcp.upload-post.com | | Registration endpoint | https://mcp.upload-post.com/register | ### The sign-in route, step by step 1. Request `https://mcp.upload-post.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.upload-post.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.upload-post.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Upload-Post. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.upload-post/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/upload-post-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=upload-post), read 4 November 2026 - [Upload-Post website](https://upload-post.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Upscrape MCP server | Agent MCP Directory" description: "Upscrape: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/upscrape-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Upscrape MCP server | Agent MCP Directory > Upscrape: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/upscrape-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Upscrape: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Upscrape at data.upscrape.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Upscrape | | --- | --- | | Domain | upscrape.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for upscrape.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://data.upscrape.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 663 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:07Z https://data.upscrape.com/mcp sent initialize result auth-required (HTTP 401) 769 ms - 20:05:00Z https://data.upscrape.com/mcp sent initialize result auth-required (HTTP 401) 663 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://data.upscrape.com/.well-known/oauth-protected-resource", scope="mcp" | | Protected resource metadata | data.upscrape.com | | Authorization server metadata | app.upscrape.com | | Registration endpoint | https://app.upscrape.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://data.upscrape.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://data.upscrape.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://app.upscrape.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Upscrape. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.upscrape/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/upscrape-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=upscrape), read 4 November 2026 - [Upscrape website](https://upscrape.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Upsolve AI MCP server | Agent MCP Directory" description: "Upsolve AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/upsolve-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Upsolve AI MCP server | Agent MCP Directory > Upsolve AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/upsolve-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Upsolve AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Upsolve AI; the connector's guess at mcp.upsolve.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Upsolve AI | | --- | --- | | Domain | upsolve.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 62, grade C; Ora scanned the domain on 11 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for upsolve.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.upsolve.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,267 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:08Z https://mcp.upsolve.ai/mcp sent initialize result auth-required (HTTP 401) 1428 ms - 20:05:01Z https://mcp.upsolve.ai/mcp sent initialize result auth-required (HTTP 401) 1267 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.upsolve.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.upsolve.ai | | Authorization server metadata | grxskwgcqtwqhgdailuc.supabase.co | | Registration endpoint | https://grxskwgcqtwqhgdailuc.supabase.co/auth/v1/oauth/clients/register | ### The sign-in route, step by step 1. Request `https://mcp.upsolve.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.upsolve.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://grxskwgcqtwqhgdailuc.supabase.co/auth/v1/oauth/clients/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Upsolve AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/upsolve-ai/index.md) ## Sources - [Ora score page for upsolve.ai](https://ora.ai/score/upsolve.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 11 September 2026, read from GET /api/leaderboard) - [Where Upsolve AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Upsolve AI website](https://upsolve.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Upstash MCP server | Agent MCP Directory" description: "Upstash has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/upstash-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Upstash MCP server | Agent MCP Directory > Upstash has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/upstash-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Upstash: MCP server, CLI and agent surfaces Yes: Upstash runs a public MCP server at mcp.context7.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: resolve-library-id, query-docs. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for upstash.com is 91, grade A, read on 5 November 2026. ## Fact sheet | Company | Upstash | | --- | --- | | Domain | upstash.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 91, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for upstash.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.context7.com/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Context7 4.5.0 | | Capabilities | tools, prompts, resources | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,360 ms over 1 attempt | | Documentation | github.com | ### Tools listed 2 tools - resolve-library-id - query-docs ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:08Z https://mcp.context7.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1350 ms - 20:05:01Z https://mcp.context7.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1360 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.context7.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Upstash. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/upstash-com/index.md) ## Sources - [Upstash MCP documentation](https://github.com/upstash/context7), read 4 November 2026 - [Ora score page for upstash.com](https://ora.ai/score/upstash.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Upstash website](https://upstash.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Uptime.com :) MCP server | Agent MCP Directory" description: "Uptime.com :): sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/uptime-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Uptime.com :) MCP server | Agent MCP Directory > Uptime.com :): sign-in required (OAuth), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/uptime-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Uptime.com :): MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Uptime.com :); the connector's guess at mcp.uptime.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Uptime.com :) | | --- | --- | | Domain | uptime.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Ora score | 59, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for uptime.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.uptime.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,839 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:09Z https://mcp.uptime.com/mcp sent initialize result auth-required (HTTP 401) 2032 ms - 20:05:02Z https://mcp.uptime.com/mcp sent initialize result auth-required (HTTP 401) 1839 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer | | Protected resource metadata | mcp.uptime.com | | Authorization server metadata | uptime.com | ### The sign-in route, step by step 1. Request `https://mcp.uptime.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://uptime.com/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Uptime.com :). The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: uptime.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/uptime-com/index.md) ## Sources - [Ora score page for uptime.com](https://ora.ai/score/uptime.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/leaderboard) - [Where Uptime.com :) was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Uptime.com :) website](https://uptime.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "UptimeRobot MCP server | Agent MCP Directory" description: "UptimeRobot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/uptimerobot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # UptimeRobot MCP server | Agent MCP Directory > UptimeRobot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/uptimerobot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # UptimeRobot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for UptimeRobot at mcp.uptimerobot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | UptimeRobot | | --- | --- | | Domain | uptimerobot.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 8,241 on the list of 4 November 2026 | | Ora score | 83, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for uptimerobot.com, a vendor-published score) | | Company found through | Ora's public leaderboard; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.uptimerobot.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 301 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:14Z https://mcp.uptimerobot.com/mcp sent initialize result auth-required (HTTP 401) 392 ms - 20:01:53Z https://mcp.uptimerobot.com/mcp sent initialize result auth-required (HTTP 401) 301 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.uptimerobot.com/mcp/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.uptimerobot.com | | Authorization server metadata | mcp.uptimerobot.com | | Registration endpoint | https://mcp.uptimerobot.com/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.uptimerobot.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.uptimerobot.com/mcp/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.uptimerobot.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for UptimeRobot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: uptimerobot.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.uptimerobot/uptimerobot | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/uptimerobot-com/index.md) ## Sources - [Ora score page for uptimerobot.com](https://ora.ai/score/uptimerobot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Where UptimeRobot was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.uptimerobot%2Fuptimerobot), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=uptimerobot), read 4 November 2026 - [UptimeRobot website](https://uptimerobot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Upwork MCP server | Agent MCP Directory" description: "Upwork: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/upwork-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Upwork MCP server | Agent MCP Directory > Upwork: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/upwork-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Upwork: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Upwork at mcp.upwork.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Upwork (registry title: Upwork MCP) | | --- | --- | | Domain | upwork.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,544 on the list of 4 November 2026 | | Ora score | 48, grade C; Ora scanned the domain on 23 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for upwork.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.upwork.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 773 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:59Z https://mcp.upwork.com/mcp sent initialize result auth-required (HTTP 401) 701 ms - 20:01:35Z https://mcp.upwork.com/mcp sent initialize result auth-required (HTTP 401) 773 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="The access token is missing or invalid", resource_metadata="https://mcp.upwork.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.upwork.com | | Authorization server metadata | mcp.upwork.com | | Registration endpoint | https://www.upwork.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.upwork.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.upwork.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://www.upwork.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Upwork. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.upwork.mcp/upwork-mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/upwork-com/index.md) ## Sources - [Ora score page for upwork.com](https://ora.ai/score/upwork.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 October 2026, read from GET /api/score) - [Where Upwork was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.upwork.mcp%2Fupwork-mcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=upwork), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Chamber MCP server | Agent MCP Directory" description: "Does Chamber have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/usechamber-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chamber MCP server | Agent MCP Directory > Does Chamber have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/usechamber-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chamber: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Chamber (usechamber.io), so the connector had nothing to connect to. Ora's cached score for usechamber.io is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Chamber (registry title: usechamber.io) | | --- | --- | | Domain | usechamber.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 68, grade C; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for usechamber.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Chamber. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for usechamber.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Chamber. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/usechamber-io/index.md) ## Sources - [Ora score page for usechamber.io](https://ora.ai/score/usechamber.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/leaderboard) - [Where Chamber was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Chamber website](https://usechamber.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Lemma MCP server | Agent MCP Directory" description: "Does Lemma have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/uselemma-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Lemma MCP server | Agent MCP Directory > Does Lemma have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/uselemma-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lemma: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Lemma (uselemma.ai), so the connector had nothing to connect to. Ora's cached score for uselemma.ai is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Lemma (registry title: uselemma.ai) | | --- | --- | | Domain | uselemma.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for uselemma.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Lemma. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for uselemma.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Lemma. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/uselemma-ai/index.md) ## Sources - [Ora score page for uselemma.ai](https://ora.ai/score/uselemma.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Lemma was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Lemma website](https://uselemma.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Naive MCP server | Agent MCP Directory" description: "Does Naive have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/usenaive-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Naive MCP server | Agent MCP Directory > Does Naive have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/usenaive-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Naive: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Naive (usenaive.ai), so the connector had nothing to connect to. Ora's cached score for usenaive.ai is 48, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Naive (registry title: usenaive.ai) | | --- | --- | | Domain | usenaive.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 48, grade C; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for usenaive.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Naive. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for usenaive.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Naive. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/usenaive-ai/index.md) ## Sources - [Ora score page for usenaive.ai](https://ora.ai/score/usenaive.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/leaderboard) - [Where Naive was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Naive website](https://usenaive.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ocular MCP server | Agent MCP Directory" description: "Does Ocular have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/useocular-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ocular MCP server | Agent MCP Directory > Does Ocular have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/useocular-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ocular: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Ocular (useocular.com), so the connector had nothing to connect to. Ora's cached score for useocular.com is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Ocular (registry title: useocular.com) | | --- | --- | | Domain | useocular.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 17 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for useocular.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Ocular. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for useocular.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Ocular. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/useocular-com/index.md) ## Sources - [Ora score page for useocular.com](https://ora.ai/score/useocular.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 17 October 2026, read from GET /api/leaderboard) - [Where Ocular was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Ocular website](https://useocular.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Paragon MCP server | Agent MCP Directory" description: "Does Paragon have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/useparagon-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Paragon MCP server | Agent MCP Directory > Does Paragon have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/useparagon-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Paragon: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Paragon (useparagon.com), so the connector had nothing to connect to. Ora's cached score for useparagon.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Paragon (registry title: useparagon.com) | | --- | --- | | Domain | useparagon.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 4 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for useparagon.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Paragon. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for useparagon.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Paragon. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/useparagon-com/index.md) ## Sources - [Ora score page for useparagon.com](https://ora.ai/score/useparagon.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 October 2026, read from GET /api/leaderboard) - [Where Paragon was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Paragon website](https://useparagon.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Usercentrics MCP server | Agent MCP Directory" description: "Usercentrics has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/usercentrics-eu site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Usercentrics MCP server | Agent MCP Directory > Usercentrics has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/usercentrics-eu Site: Agent MCP Directory Last reviewed: 2026-11-05 # Usercentrics: MCP server, CLI and agent surfaces Yes: Usercentrics runs a public MCP server at usercentrics.com that listed 7 tools to a client with no credentials on 4 November 2026. Examples: start\_compliance\_scan, get\_compliance\_scan\_status, read\_page. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Usercentrics (registry title: usercentrics.eu) | | --- | --- | | Domain | usercentrics.eu | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Tranco rank | 1,099 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for usercentrics.eu when asked on 5 November 2026 | | Company found through | the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://usercentrics.com/mcp | | --- | --- | | How it was found | listed in the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Usercentrics CMP 1.0.0 | | Capabilities | logging, completions, prompts, resources, tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 2,488 ms over 1 attempt | ### Tools listed 7 tools - start\_compliance\_scan - get\_compliance\_scan\_status - read\_page - list\_pages - start\_booking\_call - continue\_booking\_call - confirm\_booking ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:58Z https://usercentrics.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2317 ms - 20:01:34Z https://usercentrics.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 2488 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://usercentrics.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Usercentrics. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: usercentrics.eu/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/usercentrics-eu/index.md) ## Sources - [Where Usercentrics was found](https://usercentrics.eu/.well-known/mcp.json), read 4 November 2026 - [Usercentrics website](https://usercentrics.eu), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Synth AI MCP server | Agent MCP Directory" description: "Synth AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/usesynth-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Synth AI MCP server | Agent MCP Directory > Synth AI: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/usesynth-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Synth AI: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Synth AI; the connector's guess at mcp.usesynth.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Synth AI (registry title: usesynth.ai) | | --- | --- | | Domain | usesynth.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 61, grade C; Ora scanned the domain on 9 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for usesynth.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.usesynth.ai/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,116 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:09Z https://mcp.usesynth.ai/mcp sent initialize result auth-required (HTTP 401) 1187 ms - 20:05:03Z https://mcp.usesynth.ai/mcp sent initialize result auth-required (HTTP 401) 1116 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://api.usesynth.ai/.well-known/oauth-protected-resource/mcp", scope="user:org:read synth:read" | | Protected resource metadata | api.usesynth.ai | | Authorization server metadata | api.usesynth.ai | | Registration endpoint | https://api.usesynth.ai/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.usesynth.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.usesynth.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.usesynth.ai/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Synth AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: usesynth.ai/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/usesynth-ai/index.md) ## Sources - [Ora score page for usesynth.ai](https://ora.ai/score/usesynth.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 9 September 2026, read from GET /api/leaderboard) - [Where Synth AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Synth AI website](https://usesynth.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Tusk MCP server | Agent MCP Directory" description: "Does Tusk have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/usetusk-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tusk MCP server | Agent MCP Directory > Does Tusk have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/usetusk-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tusk: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Tusk (usetusk.ai), so the connector had nothing to connect to. Ora's cached score for usetusk.ai is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Tusk (registry title: usetusk.ai) | | --- | --- | | Domain | usetusk.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for usetusk.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Tusk. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for usetusk.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Tusk. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/usetusk-ai/index.md) ## Sources - [Ora score page for usetusk.ai](https://ora.ai/score/usetusk.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/leaderboard) - [Where Tusk was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Tusk website](https://usetusk.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "UXKIN MCP server | Agent MCP Directory" description: "UXKIN: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/uxkin-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # UXKIN MCP server | Agent MCP Directory > UXKIN: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/uxkin-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # UXKIN: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for UXKIN at uxkin.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | UXKIN | | --- | --- | | Domain | uxkin.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for uxkin.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://uxkin.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 759 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:09Z https://uxkin.com/mcp sent initialize result auth-required (HTTP 401) 903 ms - 20:05:03Z https://uxkin.com/mcp sent initialize result auth-required (HTTP 401) 759 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://uxkin.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | uxkin.com | | Authorization server metadata | uxkin.com | | Registration endpoint | https://uxkin.com/api/oauth/register | ### The sign-in route, step by step 1. Request `https://uxkin.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://uxkin.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://uxkin.com/api/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for UXKIN. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/uxkin-com/index.md) ## Sources - [UXKIN website](https://uxkin.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "UX Pilot MCP server | Agent MCP Directory" description: "UX Pilot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/uxpilot-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # UX Pilot MCP server | Agent MCP Directory > UX Pilot: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/uxpilot-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # UX Pilot: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for UX Pilot at mcp.uxpilot.net answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | UX Pilot | | --- | --- | | Domain | uxpilot.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 50, grade C; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for uxpilot.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.uxpilot.net/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 850 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:10Z https://mcp.uxpilot.net/mcp sent initialize result auth-required (HTTP 401) 1609 ms - 20:05:03Z https://mcp.uxpilot.net/mcp sent initialize result auth-required (HTTP 401) 850 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.uxpilot.net/.well-known/oauth-protected-resource", resource="https://mcp.uxpilot.net/mcp" | | Protected resource metadata | mcp.uxpilot.net | | Authorization server metadata | mcp.uxpilot.net | | Registration endpoint | https://mcp.uxpilot.net/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.uxpilot.net/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.uxpilot.net/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.uxpilot.net/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for UX Pilot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.uxpilot/uxpilot | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/uxpilot-ai/index.md) ## Sources - [Ora score page for uxpilot.ai](https://ora.ai/score/uxpilot.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=uxpilot), read 4 November 2026 - [UX Pilot website](https://uxpilot.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "v0 MCP server | Agent MCP Directory" description: "Does v0 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/v0-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # v0 MCP server | Agent MCP Directory > Does v0 have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/v0-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # v0: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for v0 (v0.dev), so the connector had nothing to connect to. Ora's cached score for v0.dev is 66, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | v0 | | --- | --- | | Domain | v0.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 66, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for v0.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for v0. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for v0.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for v0. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: v0.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/v0-dev/index.md) ## Sources - [Ora score page for v0.dev](https://ora.ai/score/v0.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/leaderboard) - [Where v0 was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [v0 website](https://v0.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "V7labs MCP server | Agent MCP Directory" description: "Does V7labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/v7labs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # V7labs MCP server | Agent MCP Directory > Does V7labs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/v7labs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # V7labs: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for V7labs (v7labs.com), so the connector had nothing to connect to. Ora's cached score for v7labs.com is 72, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | V7labs (registry title: v7labs.com) | | --- | --- | | Domain | v7labs.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 72, grade B; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for v7labs.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for V7labs. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for v7labs.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for V7labs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/v7labs-com/index.md) ## Sources - [Ora score page for v7labs.com](https://ora.ai/score/v7labs.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 October 2026, read from GET /api/leaderboard) - [Where V7labs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [V7labs website](https://v7labs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vaaya MCP server | Agent MCP Directory" description: "Vaaya has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vaaya-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vaaya MCP server | Agent MCP Directory > Vaaya has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vaaya-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vaaya: MCP server, CLI and agent surfaces Yes: Vaaya runs a public MCP server at vaaya.ai that listed 14 tools to a client with no credentials on 4 November 2026. Examples: stocks, jobs, vaaya\_test\_connection. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for vaaya.ai is 90, grade A, read on 5 November 2026. ## Fact sheet | Company | Vaaya | | --- | --- | | Domain | vaaya.ai | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 90, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for vaaya.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://vaaya.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | vaaya 1.0.0 | | Capabilities | tools | | Tools | 14 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 976 ms over 1 attempt | ### Tools listed 14 tools - stocks - jobs - vaaya\_test\_connection - vaaya\_onboard - vaaya\_account - vaaya\_logout - docs - consult - use - result - buy - session - close - llm ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:10Z https://vaaya.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1090 ms - 20:05:03Z https://vaaya.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 976 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://vaaya.ai/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Vaaya. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: vaaya.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.vaaya/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vaaya-ai/index.md) ## Sources - [Ora score page for vaaya.ai](https://ora.ai/score/vaaya.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=vaaya), read 4 November 2026 - [Vaaya website](https://vaaya.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Valkyrlabs MCP server | Agent MCP Directory" description: "Valkyrlabs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/valkyrlabs-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Valkyrlabs MCP server | Agent MCP Directory > Valkyrlabs: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/valkyrlabs-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Valkyrlabs: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Valkyrlabs at api-0.valkyrlabs.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Valkyrlabs (registry title: GrayMatter) | | --- | --- | | Domain | valkyrlabs.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for valkyrlabs.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api-0.valkyrlabs.com/graymatter/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,579 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:11Z https://api-0.valkyrlabs.com/graymatter/mcp sent initialize result auth-required (HTTP 401) 1790 ms - 20:05:04Z https://api-0.valkyrlabs.com/graymatter/mcp sent initialize result auth-required (HTTP 401) 1579 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api-0.valkyrlabs.com/.well-known/oauth-protected-resource/graymatter/mcp", scope="memory:read memory:write context:read", error="invalid_token", error_description="OAuth authorization is required." | | Protected resource metadata | api-0.valkyrlabs.com | | Authorization server metadata | api-0.valkyrlabs.com | | Registration endpoint | https://api-0.valkyrlabs.com/oauth2/register | ### The sign-in route, step by step 1. Request `https://api-0.valkyrlabs.com/graymatter/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api-0.valkyrlabs.com/.well-known/oauth-protected-resource/graymatter/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api-0.valkyrlabs.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Valkyrlabs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/valkyrlabs-com/index.md) ## Sources - [Where Valkyrlabs was found](https://github.com/mcp/ValkyrLabs/GrayMatter), read 4 November 2026 - [Valkyrlabs website](https://valkyrlabs.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vanta MCP server | Agent MCP Directory" description: "Vanta: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vanta-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vanta MCP server | Agent MCP Directory > Vanta: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vanta-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vanta: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Vanta; the connector's guess at mcp.vanta.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Vanta | | --- | --- | | Domain | vanta.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 27 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for vanta.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.vanta.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,219 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:11Z https://mcp.vanta.com/mcp sent initialize result auth-required (HTTP 401) 1392 ms - 20:05:04Z https://mcp.vanta.com/mcp sent initialize result auth-required (HTTP 401) 1219 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", scope="mcp-api.all:write", resource_metadata="https://mcp.vanta.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.vanta.com | | Authorization server metadata | api.vanta.com | | Registration endpoint | https://api.vanta.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.vanta.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.vanta.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.vanta.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Vanta. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vanta-com/index.md) ## Sources - [Ora score page for vanta.com](https://ora.ai/score/vanta.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 October 2026, read from GET /api/leaderboard) - [Where Vanta was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Vanta website](https://vanta.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "VectorShift MCP server | Agent MCP Directory" description: "Does VectorShift have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vectorshift-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # VectorShift MCP server | Agent MCP Directory > Does VectorShift have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/vectorshift-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # VectorShift: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for VectorShift (vectorshift.ai), so the connector had nothing to connect to. Ora's cached score for vectorshift.ai is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | VectorShift (registry title: vectorshift.ai) | | --- | --- | | Domain | vectorshift.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 4 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for vectorshift.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for VectorShift. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for vectorshift.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for VectorShift. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vectorshift-ai/index.md) ## Sources - [Ora score page for vectorshift.ai](https://ora.ai/score/vectorshift.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 September 2026, read from GET /api/leaderboard) - [Where VectorShift was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [VectorShift website](https://vectorshift.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vercel MCP server | Agent MCP Directory" description: "Vercel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vercel-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vercel MCP server | Agent MCP Directory > Vercel: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vercel-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vercel: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Vercel at mcp.vercel.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Vercel | | --- | --- | | Domain | vercel.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,040 on the list of 4 November 2026 | | Ora score | 91, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for vercel.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.vercel.com | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 964 ms over 1 attempt | | Documentation | vercel.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:01Z https://mcp.vercel.com sent initialize result auth-required (HTTP 401) 912 ms - 20:01:37Z https://mcp.vercel.com sent initialize result auth-required (HTTP 401) 964 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.vercel.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.vercel.com | | Authorization server metadata | vercel.com | | Registration endpoint | https://api.vercel.com/login/oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.vercel.com` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.vercel.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.vercel.com/login/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | vercel on npm (page) | | --- | --- | | Exists | yes | | Latest version | 65.11.0 | | Last publish | 3 November 2026 | | Command names | vc, vercel | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: vercel.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: vercel.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.vercel/vercel-mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vercel-com/index.md) ## Sources - [Vercel MCP documentation](https://vercel.com/docs/mcp/vercel-mcp), read 4 November 2026 - [Ora score page for vercel.com](https://ora.ai/score/vercel.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=vercel), read 4 November 2026 - [Vercel website](https://vercel.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Veridu MCP server | Agent MCP Directory" description: "Veridu: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/veridu-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Veridu MCP server | Agent MCP Directory > Veridu: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/veridu-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Veridu: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Veridu at api.veridu.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Veridu | | --- | --- | | Domain | veridu.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for veridu.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.veridu.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,407 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:11Z https://api.veridu.io/mcp sent initialize result auth-required (HTTP 401) 1519 ms - 20:05:05Z https://api.veridu.io/mcp sent initialize result auth-required (HTTP 401) 1407 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.veridu.io/.well-known/oauth-protected-resource/mcp", scope="mcp", error="invalid_token", error_description="authorization required" | | Protected resource metadata | api.veridu.io | | Authorization server metadata | api.veridu.io | | Registration endpoint | https://api.veridu.io/oauth/register | ### The sign-in route, step by step 1. Request `https://api.veridu.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.veridu.io/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.veridu.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Veridu. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/veridu-io/index.md) ## Sources - [Veridu website](https://veridu.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "VeriTeknik MCP server | Agent MCP Directory" description: "VeriTeknik: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/veriteknik-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # VeriTeknik MCP server | Agent MCP Directory > VeriTeknik: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/veriteknik-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # VeriTeknik: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for VeriTeknik at veriteknik.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | VeriTeknik | | --- | --- | | Domain | veriteknik.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for veriteknik.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://veriteknik.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 900 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:12Z https://veriteknik.com/api/mcp sent initialize result auth-required (HTTP 401) 1405 ms - 20:05:04Z https://veriteknik.com/api/mcp sent initialize result auth-required (HTTP 401) 900 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://veriteknik.com/.well-known/oauth-protected-resource" | | Protected resource metadata | veriteknik.com | | Authorization server metadata | veriteknik.com | | Registration endpoint | https://veriteknik.com/api/mcp/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://veriteknik.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://veriteknik.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://veriteknik.com/api/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for VeriTeknik. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.veriteknik/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/veriteknik-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=veriteknik), read 4 November 2026 - [VeriTeknik website](https://veriteknik.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Veryfi MCP server | Agent MCP Directory" description: "Does Veryfi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/veryfi-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Veryfi MCP server | Agent MCP Directory > Does Veryfi have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/veryfi-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Veryfi: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Veryfi (veryfi.com), so the connector had nothing to connect to. Ora's cached score for veryfi.com is 69, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Veryfi (registry title: veryfi.com) | | --- | --- | | Domain | veryfi.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 69, grade C; Ora scanned the domain on 24 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for veryfi.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Veryfi. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for veryfi.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Veryfi. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/veryfi-com/index.md) ## Sources - [Ora score page for veryfi.com](https://ora.ai/score/veryfi.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 October 2026, read from GET /api/leaderboard) - [Where Veryfi was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Veryfi website](https://veryfi.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "vibe MCP server | Agent MCP Directory" description: "Does vibe have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/vibe-codes site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # vibe MCP server | Agent MCP Directory > Does vibe have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/vibe-codes Site: Agent MCP Directory Last reviewed: 2026-11-05 # vibe: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for vibe (vibe.codes), so the connector had nothing to connect to. Ora's cached score for vibe.codes is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | vibe (registry title: vibe.codes) | | --- | --- | | Domain | vibe.codes | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for vibe.codes, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for vibe. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for vibe.codes, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for vibe. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vibe-codes/index.md) ## Sources - [Ora score page for vibe.codes](https://ora.ai/score/vibe.codes?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where vibe was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [vibe website](https://vibe.codes), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "VibeFlow MCP server | Agent MCP Directory" description: "Does VibeFlow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vibeflow-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # VibeFlow MCP server | Agent MCP Directory > Does VibeFlow have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/vibeflow-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # VibeFlow: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for VibeFlow (vibeflow.ai), so the connector had nothing to connect to. Ora's cached score for vibeflow.ai is 73, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | VibeFlow (registry title: vibeflow.ai) | | --- | --- | | Domain | vibeflow.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for vibeflow.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for VibeFlow. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for vibeflow.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for VibeFlow. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vibeflow-ai/index.md) ## Sources - [Ora score page for vibeflow.ai](https://ora.ai/score/vibeflow.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where VibeFlow was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [VibeFlow website](https://vibeflow.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "VibeMarketing MCP server | Agent MCP Directory" description: "VibeMarketing has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vibemarketing-ninja site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # VibeMarketing MCP server | Agent MCP Directory > VibeMarketing has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vibemarketing-ninja Site: Agent MCP Directory Last reviewed: 2026-11-05 # VibeMarketing: MCP server, CLI and agent surfaces Yes: VibeMarketing runs a public MCP server at vibemarketing.ninja that listed 7 tools to a client with no credentials on 4 November 2026. Examples: get\_accounts, get\_all\_posts, schedule\_post. It speaks streamable-http, protocol 2024-11-05. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | VibeMarketing | | --- | --- | | Domain | vibemarketing.ninja | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for vibemarketing.ninja when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://vibemarketing.ninja/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | vibemarketing-mcp 1.0.0 | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 450 ms over 1 attempt | ### Tools listed 7 tools - get\_accounts - get\_all\_posts - schedule\_post - bulk\_schedule\_posts - get\_subscription\_status - delete\_post - update\_post ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:12Z https://vibemarketing.ninja/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1106 ms - 20:05:04Z https://vibemarketing.ninja/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 450 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://vibemarketing.ninja/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for VibeMarketing. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vibemarketing-ninja/index.md) ## Sources - [Where VibeMarketing was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [VibeMarketing website](https://vibemarketing.ninja), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "VibeSEO MCP server | Agent MCP Directory" description: "VibeSEO: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support." canonical: https://agentmcpdirectory.com/directory/vibeseo-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # VibeSEO MCP server | Agent MCP Directory > VibeSEO: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Communication & Support. Source: https://agentmcpdirectory.com/directory/vibeseo-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # VibeSEO: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for VibeSEO at mcp.vibeseo.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | VibeSEO | | --- | --- | | Domain | vibeseo.dev | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for vibeseo.dev when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.vibeseo.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,364 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:13Z https://mcp.vibeseo.dev/mcp sent initialize result auth-required (HTTP 401) 1546 ms - 20:05:05Z https://mcp.vibeseo.dev/mcp sent initialize result auth-required (HTTP 401) 1364 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.vibeseo.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.vibeseo.dev | | Authorization server metadata | api.vibeseo.dev | | Registration endpoint | https://api.vibeseo.dev/connect/register | ### The sign-in route, step by step 1. Request `https://mcp.vibeseo.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.vibeseo.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.vibeseo.dev/connect/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for VibeSEO. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: dev.vibeseo/geo, dev.vibeseo/vibeseo | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vibeseo-dev/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=vibeseo), read 4 November 2026 - [VibeSEO website](https://vibeseo.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vidova MCP server | Agent MCP Directory" description: "Vidova: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vidova-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vidova MCP server | Agent MCP Directory > Vidova: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vidova-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vidova: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Vidova at mcp.vidova.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Vidova | | --- | --- | | Domain | vidova.ai | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 35, grade D; Ora scanned the domain on 21 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for vidova.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.vidova.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 213 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:12Z https://mcp.vidova.ai/mcp sent initialize result auth-required (HTTP 401) 428 ms - 20:05:05Z https://mcp.vidova.ai/mcp sent initialize result auth-required (HTTP 401) 213 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", resource_metadata="https://mcp.vidova.ai/.well-known/oauth-protected-resource", scope="mcp:tools" | | Protected resource metadata | mcp.vidova.ai | | Authorization server metadata | auth.vidova.ai | | Registration endpoint | https://auth.vidova.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.vidova.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.vidova.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.vidova.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Vidova. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.vidova/vidova | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vidova-ai/index.md) ## Sources - [Ora score page for vidova.ai](https://ora.ai/score/vidova.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 21 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=vidova), read 4 November 2026 - [Vidova website](https://vidova.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vike MCP server | Agent MCP Directory" description: "Vike: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vike-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vike MCP server | Agent MCP Directory > Vike: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vike-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vike: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Vike at data.vike.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Vike (registry title: Vike Data API) | | --- | --- | | Domain | vike.io | | Category | Payments & Fintech (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for vike.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://data.vike.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 759 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:13Z https://data.vike.io/mcp sent initialize result auth-required (HTTP 401) 985 ms - 20:05:05Z https://data.vike.io/mcp sent initialize result auth-required (HTTP 401) 759 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://data.vike.io/.well-known/oauth-protected-resource" | | Protected resource metadata | data.vike.io | | Authorization server metadata | vike.io | | Registration endpoint | https://vike.io/oauth/register | ### The sign-in route, step by step 1. Request `https://data.vike.io/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://data.vike.io/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://vike.io/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Vike. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vike-io/index.md) ## Sources - [Vike website](https://vike.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vimmerse MCP server | Agent MCP Directory" description: "Does Vimmerse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vimmerse-net site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vimmerse MCP server | Agent MCP Directory > Does Vimmerse have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/vimmerse-net Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vimmerse: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Vimmerse (vimmerse.net), so the connector had nothing to connect to. Ora's cached score for vimmerse.net is 52, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Vimmerse (registry title: vimmerse.net) | | --- | --- | | Domain | vimmerse.net | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 52, grade C; Ora scanned the domain on 20 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for vimmerse.net, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Vimmerse. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for vimmerse.net, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Vimmerse. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vimmerse-net/index.md) ## Sources - [Ora score page for vimmerse.net](https://ora.ai/score/vimmerse.net?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 20 September 2026, read from GET /api/leaderboard) - [Where Vimmerse was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Vimmerse website](https://vimmerse.net), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Viridisconservation MCP server | Agent MCP Directory" description: "Viridisconservation has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/viridisconservation-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Viridisconservation MCP server | Agent MCP Directory > Viridisconservation has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/viridisconservation-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Viridisconservation: MCP server, CLI and agent surfaces Yes: Viridisconservation runs a public MCP server at mcp.viridisconservation.com that listed 9 tools to a client with no credentials on 4 November 2026. Examples: open\_escrow, fund\_escrow, release\_escrow. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Viridisconservation (registry title: Jdhart81 Agent Escrow) | | --- | --- | | Domain | viridisconservation.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for viridisconservation.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.viridisconservation.com/escrow/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | agent-escrow-agent 1.28.1 | | Capabilities | experimental, prompts, resources, tools | | Tools | 9 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,323 ms over 1 attempt | ### Tools listed 9 tools - open\_escrow - fund\_escrow - release\_escrow - refund\_escrow - dispute\_escrow - escrow\_status - list\_escrows - verify\_audit - describe\_agent ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:14Z https://mcp.viridisconservation.com/escrow/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1504 ms - 20:05:06Z https://mcp.viridisconservation.com/escrow/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1323 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.viridisconservation.com/escrow/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Viridisconservation. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/viridisconservation-com/index.md) ## Sources - [Viridisconservation website](https://viridisconservation.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Virtualmin MCP server | Agent MCP Directory" description: "Does Virtualmin have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/virtualmin-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Virtualmin MCP server | Agent MCP Directory > Does Virtualmin have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/virtualmin-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Virtualmin: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Virtualmin (virtualmin.com), so the connector had nothing to connect to. Ora's cached score for virtualmin.com is 40, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Virtualmin (registry title: virtualmin.com) | | --- | --- | | Domain | virtualmin.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 4,295 on the list of 4 November 2026 | | Ora score | 40, grade D; Ora scanned the domain on 30 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for virtualmin.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Virtualmin. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for virtualmin.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Virtualmin. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/virtualmin-com/index.md) ## Sources - [Ora score page for virtualmin.com](https://ora.ai/score/virtualmin.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 October 2026, read from GET /api/score) - [Where Virtualmin was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Virtualmin website](https://virtualmin.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Visa MCP server | Agent MCP Directory" description: "Visa: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/visa-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Visa MCP server | Agent MCP Directory > Visa: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/visa-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Visa: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Visa at developer.visa.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Visa (registry title: Visa Developer Center MCP Server) | | --- | --- | | Domain | visa.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,770 on the list of 4 November 2026 | | Ora score | 56, grade C; Ora scanned the domain on 29 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for visa.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://developer.visa.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,244 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:01Z https://developer.visa.com/mcp sent initialize result auth-required (HTTP 401) 1529 ms - 20:01:36Z https://developer.visa.com/mcp sent initialize result auth-required (HTTP 401) 1244 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://developer.visa.com/oauth-protected-resource", scope="mcp:tools" | | Protected resource metadata | developer.visa.com | | Authorization server metadata | vammcp.visa.com | | Registration endpoint | https://vammcp.visa.com/openam/oauth2/realms/root/realms/vol/register | ### The sign-in route, step by step 1. Request `https://developer.visa.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://developer.visa.com/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://vammcp.visa.com/openam/oauth2/realms/root/realms/vol/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Visa. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.visa.developer/vdp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/visa-com/index.md) ## Sources - [Ora score page for visa.com](https://ora.ai/score/visa.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 October 2026, read from GET /api/score) - [Where Visa was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.visa.developer%2Fvdp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=visa), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "VISEON MCP server | Agent MCP Directory" description: "VISEON has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/viseon-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # VISEON MCP server | Agent MCP Directory > VISEON has an open MCP server with 7 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/viseon-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # VISEON: MCP server, CLI and agent surfaces Yes: VISEON runs a public MCP server at viseon.io that listed 7 tools to a client with no credentials on 4 November 2026. Examples: get\_entity, query\_relationships, find\_by\_type. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | VISEON (registry title: VISEON Ask) | | --- | --- | | Domain | viseon.io | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for viseon.io when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://viseon.io/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | VISEON for Web 4.0.0-dev | | Capabilities | tools | | Tools | 7 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 289 ms over 1 attempt | ### Tools listed 7 tools - get\_entity - query\_relationships - find\_by\_type - search\_content - fuzzy\_find\_and\_traverse - traverse\_path - get\_citable\_passages ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:13Z https://viseon.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 702 ms - 20:05:05Z https://viseon.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 289 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://viseon.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for VISEON. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/viseon-io/index.md) ## Sources - [VISEON website](https://viseon.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "vocode MCP server | Agent MCP Directory" description: "Does vocode have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vocode-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # vocode MCP server | Agent MCP Directory > Does vocode have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/vocode-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # vocode: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for vocode (vocode.dev), so the connector had nothing to connect to. Ora's cached score for vocode.dev is 60, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | vocode (registry title: vocode.dev) | | --- | --- | | Domain | vocode.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 60, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for vocode.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for vocode. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for vocode.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for vocode. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vocode-dev/index.md) ## Sources - [Ora score page for vocode.dev](https://ora.ai/score/vocode.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where vocode was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [vocode website](https://vocode.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Voker MCP server | Agent MCP Directory" description: "Does Voker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/voker-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Voker MCP server | Agent MCP Directory > Does Voker have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/voker-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Voker: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Voker (voker.ai), so the connector had nothing to connect to. Ora's cached score for voker.ai is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Voker (registry title: voker.ai) | | --- | --- | | Domain | voker.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 7 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for voker.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Voker. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for voker.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Voker. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/voker-ai/index.md) ## Sources - [Ora score page for voker.ai](https://ora.ai/score/voker.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 7 October 2026, read from GET /api/leaderboard) - [Where Voker was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Voker website](https://voker.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vooban MCP server | Agent MCP Directory" description: "Vooban: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vooban-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vooban MCP server | Agent MCP Directory > Vooban: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vooban-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vooban: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Vooban at morphe.vooban.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Vooban (registry title: Morphe) | | --- | --- | | Domain | vooban.com | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for vooban.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://morphe.vooban.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 665 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:14Z https://morphe.vooban.com/api/mcp sent initialize result auth-required (HTTP 401) 866 ms - 20:05:06Z https://morphe.vooban.com/api/mcp sent initialize result auth-required (HTTP 401) 665 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer scope="read", resource_metadata="https://morphe.vooban.com/.well-known/oauth-protected-resource/api/mcp" | | Protected resource metadata | morphe.vooban.com | | Authorization server metadata | morphe.vooban.com | | Registration endpoint | https://morphe.vooban.com/api/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://morphe.vooban.com/api/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://morphe.vooban.com/.well-known/oauth-protected-resource/api/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://morphe.vooban.com/api/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Vooban. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.vooban.morphe/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vooban-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=vooban), read 4 November 2026 - [Vooban website](https://vooban.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vultr MCP server | Agent MCP Directory" description: "Vultr: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vultr-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vultr MCP server | Agent MCP Directory > Vultr: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vultr-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vultr: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for Vultr; the connector's guess at mcp.vultr.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Vultr | | --- | --- | | Domain | vultr.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 5,754 on the list of 4 November 2026 | | Ora score | 62, grade C; Ora scanned the domain on 22 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for vultr.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.vultr.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,273 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:10Z https://mcp.vultr.com/mcp sent initialize result auth-required (HTTP 401) 1118 ms - 20:01:47Z https://mcp.vultr.com/mcp sent initialize result auth-required (HTTP 401) 1273 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.vultr.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.vultr.com | | Authorization server metadata | mcp.vultr.com | | Registration endpoint | https://mcp.vultr.com/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.vultr.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.vultr.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.vultr.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Vultr. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vultr-com/index.md) ## Sources - [Ora score page for vultr.com](https://ora.ai/score/vultr.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 22 October 2026, read from GET /api/score) - [Where Vultr was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Vybenetwork MCP server | Agent MCP Directory" description: "Vybenetwork has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/vybenetwork-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Vybenetwork MCP server | Agent MCP Directory > Vybenetwork has an open MCP server with 5 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/vybenetwork-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vybenetwork: MCP server, CLI and agent surfaces Yes: Vybenetwork runs a public MCP server at docs.vybenetwork.com that listed 5 tools to a client with no credentials on 4 November 2026. Examples: list-endpoints, get-endpoint, search-endpoints. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Vybenetwork (registry title: Solana MCP by Vybe) | | --- | --- | | Domain | vybenetwork.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for vybenetwork.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://docs.vybenetwork.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Solana API & WebSocket Docs 4.0.11 | | Capabilities | tools | | Tools | 5 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,260 ms over 1 attempt | ### Tools listed 5 tools - list-endpoints - get-endpoint - search-endpoints - execute-request - pay-with-x402 ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:14Z https://docs.vybenetwork.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1027 ms - 20:05:07Z https://docs.vybenetwork.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1260 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://docs.vybenetwork.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Vybenetwork. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/vybenetwork-com/index.md) ## Sources - [Vybenetwork website](https://vybenetwork.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Waldium MCP server | Agent MCP Directory" description: "Waldium has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/waldium-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Waldium MCP server | Agent MCP Directory > Waldium has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/waldium-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Waldium: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Waldium; the connector tried mcp.waldium.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | Waldium (registry title: waldium.com) | | --- | --- | | Domain | waldium.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 37, grade D; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for waldium.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.waldium.com/mcp | | --- | --- | | How it was found | mcp.waldium.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,379 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:15Z https://mcp.waldium.com/mcp sent initialize result no-answer (HTTP 404) 1409 ms - 20:05:07Z https://mcp.waldium.com/mcp sent initialize result no-answer (HTTP 404) 1379 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.waldium.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Waldium. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/waldium-com/index.md) ## Sources - [Ora score page for waldium.com](https://ora.ai/score/waldium.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Waldium was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Waldium website](https://waldium.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wall Marketing MCP server | Agent MCP Directory" description: "Wall Marketing: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/wall-marketing site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wall Marketing MCP server | Agent MCP Directory > Wall Marketing: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/wall-marketing Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wall Marketing: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Wall Marketing at www.wall.marketing answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Wall Marketing | | --- | --- | | Domain | wall.marketing | | Category | Marketing (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for wall.marketing when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.wall.marketing/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 216 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:15Z https://www.wall.marketing/mcp sent initialize result auth-required (HTTP 401) 960 ms - 20:05:06Z https://www.wall.marketing/mcp sent initialize result auth-required (HTTP 401) 216 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://www.wall.marketing/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | www.wall.marketing | | Authorization server metadata | www.wall.marketing | | Registration endpoint | https://www.wall.marketing/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://www.wall.marketing/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.wall.marketing/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://www.wall.marketing/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Wall Marketing. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wall-marketing/index.md) ## Sources - [Wall Marketing website](https://wall.marketing), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Warp MCP server | Agent MCP Directory" description: "Does Warp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/warp-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Warp MCP server | Agent MCP Directory > Does Warp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/warp-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Warp: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Warp (warp.dev), so the connector had nothing to connect to. Ora's cached score for warp.dev is 80, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Warp | | --- | --- | | Domain | warp.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 80, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for warp.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Warp. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for warp.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Warp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: warp.dev/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/warp-dev/index.md) ## Sources - [Ora score page for warp.dev](https://ora.ai/score/warp.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/leaderboard) - [Where Warp was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Warp website](https://warp.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WarpBuild MCP server | Agent MCP Directory" description: "WarpBuild: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/warpbuild-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WarpBuild MCP server | Agent MCP Directory > WarpBuild: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/warpbuild-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WarpBuild: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. No source names an endpoint for WarpBuild; the connector's guess at mcp.warpbuild.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | WarpBuild (registry title: warpbuild.com) | | --- | --- | | Domain | warpbuild.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 61, grade C; Ora scanned the domain on 29 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for warpbuild.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.warpbuild.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 709 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:15Z https://mcp.warpbuild.com/mcp sent initialize result auth-required (HTTP 401) 1303 ms - 20:05:07Z https://mcp.warpbuild.com/mcp sent initialize result auth-required (HTTP 401) 709 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.warpbuild.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.warpbuild.com | | Authorization server metadata | auth.warpbuild.com | | Registration endpoint | https://auth.warpbuild.com/api/v1/auth/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.warpbuild.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.warpbuild.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.warpbuild.com/api/v1/auth/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WarpBuild. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/warpbuild-com/index.md) ## Sources - [Ora score page for warpbuild.com](https://ora.ai/score/warpbuild.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 29 August 2026, read from GET /api/leaderboard) - [Where WarpBuild was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [WarpBuild website](https://warpbuild.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wasmer MCP server | Agent MCP Directory" description: "Does Wasmer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wasmer-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wasmer MCP server | Agent MCP Directory > Does Wasmer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/wasmer-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wasmer: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Wasmer (wasmer.io), so the connector had nothing to connect to. Ora's cached score for wasmer.io is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Wasmer (registry title: wasmer.io) | | --- | --- | | Domain | wasmer.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for wasmer.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Wasmer. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for wasmer.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Wasmer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wasmer-io/index.md) ## Sources - [Ora score page for wasmer.io](https://ora.ai/score/wasmer.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Wasmer was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Wasmer website](https://wasmer.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Watchgoose MCP server | Agent MCP Directory" description: "Watchgoose: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/watchgoose-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Watchgoose MCP server | Agent MCP Directory > Watchgoose: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/watchgoose-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Watchgoose: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Watchgoose at mcp.watchgoose.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Watchgoose | | --- | --- | | Domain | watchgoose.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 60, grade C; Ora scanned the domain on 28 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for watchgoose.com, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.watchgoose.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 352 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:15Z https://mcp.watchgoose.com/mcp sent initialize result auth-required (HTTP 401) 593 ms - 20:05:07Z https://mcp.watchgoose.com/mcp sent initialize result auth-required (HTTP 401) 352 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", resource_metadata="https://mcp.watchgoose.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.watchgoose.com | | Authorization server metadata | mcp.watchgoose.com | | Registration endpoint | https://mcp.watchgoose.com/register | ### The sign-in route, step by step 1. Request `https://mcp.watchgoose.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.watchgoose.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.watchgoose.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Watchgoose. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: watchgoose.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/watchgoose-com/index.md) ## Sources - [Ora score page for watchgoose.com](https://ora.ai/score/watchgoose.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 August 2026, read from GET /api/score) - [Where Watchgoose was found](https://github.com/mcp/bartekrutkowski/watchgoose-mcp), read 4 November 2026 - [Watchgoose website](https://watchgoose.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Waydev MCP server | Agent MCP Directory" description: "Does Waydev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/waydev-co site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Waydev MCP server | Agent MCP Directory > Does Waydev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/waydev-co Site: Agent MCP Directory Last reviewed: 2026-11-05 # Waydev: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Waydev (waydev.co), so the connector had nothing to connect to. Ora's cached score for waydev.co is 64, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Waydev (registry title: waydev.co) | | --- | --- | | Domain | waydev.co | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 64, grade C; Ora scanned the domain on 8 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for waydev.co, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Waydev. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for waydev.co, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Waydev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: waydev.co/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/waydev-co/index.md) ## Sources - [Ora score page for waydev.co](https://ora.ai/score/waydev.co?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 8 September 2026, read from GET /api/leaderboard) - [Where Waydev was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Waydev website](https://waydev.co), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WayStation MCP server | Agent MCP Directory" description: "WayStation has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/waystation-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WayStation MCP server | Agent MCP Directory > WayStation has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/waystation-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # WayStation: MCP server, CLI and agent surfaces Not verified. A source lists an MCP endpoint for WayStation (waystation.ai), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 402, GET HTTP 402 text/plain; charset=utf-8). ## Fact sheet | Company | WayStation | | --- | --- | | Domain | waystation.ai | | Category | Productivity (Ora leaderboard category) | | MCP server | No answer | | Ora score | none: Ora returned no cached score for waystation.ai when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://waystation.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | HTTP status | 402 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 436 ms over 2 attempts | | Result | no MCP answer (POST HTTP 402, GET HTTP 402 text/plain; charset=utf-8) | ### Connector log 4 connections on 4 November 2026, read-only methods only - 20:00:15Z https://waystation.ai/mcp sent initialize result no-answer (HTTP 402) 605 ms - 20:00:16Z https://waystation.ai/jira/mcp sent initialize result no-answer (HTTP 402) 264 ms - 20:05:07Z https://waystation.ai/mcp sent initialize result no-answer (HTTP 402) 436 ms - 20:05:07Z https://waystation.ai/jira/mcp sent initialize result no-answer (HTTP 402) 270 ms ## Authentication | Auth type | Auth not determined | | --- | --- | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://waystation.ai/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 402, GET HTTP 402 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WayStation. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.waystation/airtable, ai.waystation/gmail, ai.waystation/jira and 2 more | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/waystation-ai/index.md) ## Sources - [Where WayStation was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=waystation), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Web3Juice MCP server | Agent MCP Directory" description: "Web3Juice has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/web3juice-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Web3Juice MCP server | Agent MCP Directory > Web3Juice has an open MCP server with 14 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/web3juice-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Web3Juice: MCP server, CLI and agent surfaces Yes: Web3Juice runs a public MCP server at web3juice.com that listed 14 tools to a client with no credentials on 4 November 2026. Examples: list\_investments, list\_wallets, get\_wallet\_positions. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Web3Juice | | --- | --- | | Domain | web3juice.com | | Category | Data & Analytics (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for web3juice.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://web3juice.com/api/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | web3juice 1.0.0 | | Capabilities | tools, prompts, resources | | Tools | 14 | | Resources | 3 | | Prompts | 4 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 764 ms over 1 attempt | ### Tools listed 14 tools - list\_investments - list\_wallets - get\_wallet\_positions - list\_alerts - get\_alert - list\_notebook\_entries - get\_notebook\_entry - summarize\_yields - search\_pools - get\_pool - get\_pool\_history - compare\_pools - get\_data\_sources - get\_methodology ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:17Z https://web3juice.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1938 ms - 20:05:07Z https://web3juice.com/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 764 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://web3juice.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Web3Juice. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.web3juice/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/web3juice-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=web3juice), read 4 November 2026 - [Web3Juice website](https://web3juice.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Webflow MCP server | Agent MCP Directory" description: "Webflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Commerce Tools." canonical: https://agentmcpdirectory.com/directory/webflow-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Webflow MCP server | Agent MCP Directory > Webflow: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Commerce Tools. Source: https://agentmcpdirectory.com/directory/webflow-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Webflow: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Webflow at mcp.webflow.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Webflow | | --- | --- | | Domain | webflow.com | | Category | Commerce Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 2,772 on the list of 4 November 2026 | | Ora score | 78, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for webflow.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.webflow.com/sse | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 93 ms over 1 attempt | | Documentation | developers.webflow.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:00Z https://mcp.webflow.com/sse sent initialize result auth-required (HTTP 401) 103 ms - 20:01:35Z https://mcp.webflow.com/sse sent initialize result auth-required (HTTP 401) 93 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.webflow.com/.well-known/oauth-protected-resource/sse", error="invalid_token", error_description="Missing or invalid access token" | | Protected resource metadata | mcp.webflow.com | | Authorization server metadata | mcp.webflow.com | | Registration endpoint | https://mcp.webflow.com/oauth/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.webflow.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.webflow.com/.well-known/oauth-protected-resource/sse` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.webflow.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @webflow/webflow-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 2.15.0 | | Last publish | 27 October 2026 | | Command names | webflow | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.webflow/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/webflow-com/index.md) ## Sources - [Webflow MCP documentation](https://developers.webflow.com/mcp/reference/overview), read 4 November 2026 - [Ora score page for webflow.com](https://ora.ai/score/webflow.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 3 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=webflow), read 4 November 2026 - [Webflow website](https://webflow.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Webhound MCP server | Agent MCP Directory" description: "Webhound: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML." canonical: https://agentmcpdirectory.com/directory/webhound-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Webhound MCP server | Agent MCP Directory > Webhound: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: AI & ML. Source: https://agentmcpdirectory.com/directory/webhound-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Webhound: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Webhound at api.webhound.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Webhound | | --- | --- | | Domain | webhound.ai | | Category | AI & ML (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 38, grade D; Ora scanned the domain on 25 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for webhound.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.webhound.ai/api/v2/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,170 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:17Z https://api.webhound.ai/api/v2/mcp sent initialize result auth-required (HTTP 401) 1693 ms - 20:05:08Z https://api.webhound.ai/api/v2/mcp sent initialize result auth-required (HTTP 401) 1170 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.webhound.ai/.well-known/oauth-protected-resource/api/v2/mcp" | | Protected resource metadata | api.webhound.ai | | Authorization server metadata | api.webhound.ai | | Registration endpoint | https://api.webhound.ai/api/v2/oauth/register | ### The sign-in route, step by step 1. Request `https://api.webhound.ai/api/v2/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.webhound.ai/.well-known/oauth-protected-resource/api/v2/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.webhound.ai/api/v2/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Webhound. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.webhound/webhound | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/webhound-ai/index.md) ## Sources - [Ora score page for webhound.ai](https://ora.ai/score/webhound.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 August 2026, read from GET /api/leaderboard) - [Where Webhound was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.webhound%2Fwebhound), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=webhound), read 4 November 2026 - [Webhound website](https://webhound.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WebinarIgnition MCP server | Agent MCP Directory" description: "WebinarIgnition has an open MCP server with 93 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/webinarignition-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WebinarIgnition MCP server | Agent MCP Directory > WebinarIgnition has an open MCP server with 93 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/webinarignition-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WebinarIgnition: MCP server, CLI and agent surfaces Yes: WebinarIgnition runs a public MCP server at mcp.webinarignition.com that listed 93 tools to a client with no credentials on 4 November 2026. Examples: wi\_get\_session\_facts, wi\_list\_site\_abilities, wi\_get\_connector\_status. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | WebinarIgnition | | --- | --- | | Domain | webinarignition.com | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for webinarignition.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.webinarignition.com/?src=registry | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | WebinarIgnition 1.14.4 | | Capabilities | tools, prompts, resources | | Tools | 93 | | Resources | 3 | | Prompts | 4 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 788 ms over 1 attempt | ### Tools listed 93 tools; the first 40 names are recorded - wi\_get\_session\_facts - wi\_list\_site\_abilities - wi\_get\_connector\_status - wi\_answer\_product\_question - wi\_get\_setup\_plan - wi\_start\_webinar - wi\_continue\_webinar - wi\_write\_webinar\_invitation\_emails - wi\_check\_wordpress - wi\_connect\_wordpress\_woocommerce\_site - wi\_disconnect\_wordpress - wi\_create\_webinar\_registration\_page - wi\_get\_build\_status - wi\_create\_handoff\_link - wi\_delete\_webinar - wi\_list\_webinar\_leads\_registrants - wi\_get\_webinar\_attendance\_stats - wi\_get\_webinar\_funnel\_conversion\_stats - wi\_get\_webinar\_revenue\_woocommerce - wi\_list\_webinars - wi\_get\_webinar - wi\_get\_webinar\_emails - wi\_get\_registration\_fields - wi\_get\_webinar\_settings - wi\_get\_webinar\_colors - wi\_list\_webinar\_products - wi\_get\_streaming\_status - wi\_get\_webinar\_questions - wi\_get\_webinar\_prompter - wi\_get\_renotification\_status - wi\_check\_mail\_delivery - wi\_check\_embedding - wi\_list\_webinar\_links - wi\_list\_webhooks - wi\_read\_webhook\_deliveries - wi\_get\_webhook\_test\_address - wi\_find\_wordpress\_user - wi\_find\_media - wi\_get\_webinar\_page\_blocks - wi\_get\_explainer\_video ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:17Z https://mcp.webinarignition.com/?src=registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1264 ms - 20:05:08Z https://mcp.webinarignition.com/?src=registry sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 788 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.webinarignition.com/?src=registry` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WebinarIgnition. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.webinarignition/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/webinarignition-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=webinarignition), read 4 November 2026 - [WebinarIgnition website](https://webinarignition.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Webiny MCP server | Agent MCP Directory" description: "Does Webiny have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/webiny-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Webiny MCP server | Agent MCP Directory > Does Webiny have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/webiny-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Webiny: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Webiny (webiny.com), so the connector had nothing to connect to. Ora's cached score for webiny.com is 67, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Webiny (registry title: webiny.com) | | --- | --- | | Domain | webiny.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 67, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for webiny.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Webiny. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for webiny.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Webiny. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/webiny-com/index.md) ## Sources - [Ora score page for webiny.com](https://ora.ai/score/webiny.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where Webiny was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Webiny website](https://webiny.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WebZum MCP server | Agent MCP Directory" description: "WebZum has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/webzum-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WebZum MCP server | Agent MCP Directory > WebZum has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/webzum-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WebZum: MCP server, CLI and agent surfaces Yes: WebZum runs a public MCP server at webzum.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: build\_website, get\_site\_status, host\_site. It speaks streamable-http, protocol 2024-11-05. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | WebZum | | --- | --- | | Domain | webzum.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for webzum.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://webzum.com/api/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | webzum 1.0.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 2,797 ms over 1 attempt | ### Tools listed 6 tools - build\_website - get\_site\_status - host\_site - host\_file - get\_hosted\_files - host\_zip ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:19Z https://webzum.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2760 ms - 20:05:10Z https://webzum.com/api/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2797 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://webzum.com/api/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WebZum. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/webzum-com/index.md) ## Sources - [Where WebZum was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [WebZum website](https://webzum.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WeTransfer MCP server | Agent MCP Directory" description: "Does WeTransfer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wetransfer-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WeTransfer MCP server | Agent MCP Directory > Does WeTransfer have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/wetransfer-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WeTransfer: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for WeTransfer (wetransfer.com), so the connector had nothing to connect to. Ora's cached score for wetransfer.com is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | WeTransfer (registry title: wetransfer.com) | | --- | --- | | Domain | wetransfer.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,554 on the list of 4 November 2026 | | Ora score | 39, grade D; Ora scanned the domain on 26 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for wetransfer.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for WeTransfer. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for wetransfer.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for WeTransfer. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wetransfer-com/index.md) ## Sources - [Ora score page for wetransfer.com](https://ora.ai/score/wetransfer.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 August 2026, read from GET /api/score) - [Where WeTransfer was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [WeTransfer website](https://wetransfer.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WeWeb MCP server | Agent MCP Directory" description: "Does WeWeb have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/weweb-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WeWeb MCP server | Agent MCP Directory > Does WeWeb have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/weweb-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # WeWeb: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for WeWeb (weweb.io), so the connector had nothing to connect to. Ora's cached score for weweb.io is 62, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | WeWeb (registry title: weweb.io) | | --- | --- | | Domain | weweb.io | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 62, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for weweb.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for WeWeb. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for weweb.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for WeWeb. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/weweb-io/index.md) ## Sources - [Ora score page for weweb.io](https://ora.ai/score/weweb.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where WeWeb was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [WeWeb website](https://weweb.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Whalesync MCP server | Agent MCP Directory" description: "Whalesync: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics." canonical: https://agentmcpdirectory.com/directory/whalesync-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Whalesync MCP server | Agent MCP Directory > Whalesync: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Data & Analytics. Source: https://agentmcpdirectory.com/directory/whalesync-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Whalesync: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Whalesync at api.whalesync.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Whalesync | | --- | --- | | Domain | whalesync.com | | Category | Data & Analytics (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 45, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for whalesync.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.whalesync.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 295 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:17Z https://api.whalesync.com/mcp sent initialize result auth-required (HTTP 401) 824 ms - 20:05:08Z https://api.whalesync.com/mcp sent initialize result auth-required (HTTP 401) 295 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://api.whalesync.com/.well-known/oauth-protected-resource/mcp", scope="read operate readwrite" | | Protected resource metadata | api.whalesync.com | | Authorization server metadata | api.whalesync.com | | Registration endpoint | https://api.whalesync.com/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://api.whalesync.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://api.whalesync.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://api.whalesync.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Whalesync. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.whalesync/whalesync | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/whalesync-com/index.md) ## Sources - [Ora score page for whalesync.com](https://ora.ai/score/whalesync.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where Whalesync was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.whalesync%2Fwhalesync), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=whalesync), read 4 November 2026 - [Whalesync website](https://whalesync.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Whimsical MCP server | Agent MCP Directory" description: "Whimsical: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/whimsical-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Whimsical MCP server | Agent MCP Directory > Whimsical: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/whimsical-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Whimsical: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Whimsical at mcp.whimsical.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Whimsical | | --- | --- | | Domain | whimsical.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 58, grade C; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for whimsical.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.whimsical.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 462 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:17Z https://mcp.whimsical.com/mcp sent initialize result auth-required (HTTP 401) 655 ms - 20:05:08Z https://mcp.whimsical.com/mcp sent initialize result auth-required (HTTP 401) 462 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_request", error_description="Missing Bearer token", resource_metadata="https://mcp.whimsical.com/.well-known/oauth-protected-resource", scope="profile mcp:read mcp:write" | | Protected resource metadata | mcp.whimsical.com | | Authorization server metadata | mcp.whimsical.com | | Registration endpoint | https://api.whimsical.com/v1/oauth.register-mcp-client | ### The sign-in route, step by step 1. Request `https://mcp.whimsical.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.whimsical.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://api.whimsical.com/v1/oauth.register-mcp-client` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Whimsical. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.whimsical/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/whimsical-com/index.md) ## Sources - [Ora score page for whimsical.com](https://ora.ai/score/whimsical.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/leaderboard) - [Where Whimsical was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.whimsical%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=whimsical), read 4 November 2026 - [Whimsical website](https://whimsical.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WhitePact MCP server | Agent MCP Directory" description: "WhitePact: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised." canonical: https://agentmcpdirectory.com/directory/whitepact-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WhitePact MCP server | Agent MCP Directory > WhitePact: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Uncategorised. Source: https://agentmcpdirectory.com/directory/whitepact-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WhitePact: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for WhitePact at whitepact-mcp-http.onrender.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | WhitePact | | --- | --- | | Domain | whitepact.com | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for whitepact.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://whitepact-mcp-http.onrender.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 855 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:18Z https://whitepact-mcp-http.onrender.com/mcp sent initialize result auth-required (HTTP 401) 1236 ms - 20:05:09Z https://whitepact-mcp-http.onrender.com/mcp sent initialize result auth-required (HTTP 401) 855 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://whitepact-mcp-http.onrender.com/.well-known/oauth-protected-resource", scope="whitepact:review" | | Protected resource metadata | whitepact-mcp-http.onrender.com | | Authorization server metadata | whitepact-mcp-http.onrender.com | | Registration endpoint | https://whitepact-mcp-http.onrender.com/oauth/register | ### The sign-in route, step by step 1. Request `https://whitepact-mcp-http.onrender.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://whitepact-mcp-http.onrender.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://whitepact-mcp-http.onrender.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WhitePact. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/whitepact-com/index.md) ## Sources - [Where WhitePact was found](https://github.com/mcp/Guruprasath-Annadurai/Whitepact), read 4 November 2026 - [WhitePact website](https://whitepact.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WhyLabs MCP server | Agent MCP Directory" description: "Does WhyLabs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/whylabs-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WhyLabs MCP server | Agent MCP Directory > Does WhyLabs have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/whylabs-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # WhyLabs: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for WhyLabs (whylabs.ai), so the connector had nothing to connect to. Ora's cached score for whylabs.ai is 47, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | WhyLabs (registry title: whylabs.ai) | | --- | --- | | Domain | whylabs.ai | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 47, grade D; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for whylabs.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for WhyLabs. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for whylabs.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for WhyLabs. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/whylabs-ai/index.md) ## Sources - [Ora score page for whylabs.ai](https://ora.ai/score/whylabs.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where WhyLabs was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [WhyLabs website](https://whylabs.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wild Moose AI MCP server | Agent MCP Directory" description: "Does Wild Moose AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wildmoose-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wild Moose AI MCP server | Agent MCP Directory > Does Wild Moose AI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/wildmoose-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wild Moose AI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Wild Moose AI (wildmoose.ai), so the connector had nothing to connect to. Ora's cached score for wildmoose.ai is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Wild Moose AI | | --- | --- | | Domain | wildmoose.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 28 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for wildmoose.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Wild Moose AI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for wildmoose.ai, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Wild Moose AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wildmoose-ai/index.md) ## Sources - [Ora score page for wildmoose.ai](https://ora.ai/score/wildmoose.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 August 2026, read from GET /api/leaderboard) - [Where Wild Moose AI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Wild Moose AI website](https://wildmoose.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Windmill MCP server | Agent MCP Directory" description: "Does Windmill have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/windmill-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Windmill MCP server | Agent MCP Directory > Does Windmill have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/windmill-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Windmill: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Windmill (windmill.dev), so the connector had nothing to connect to. Ora's cached score for windmill.dev is 56, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Windmill (registry title: windmill.dev) | | --- | --- | | Domain | windmill.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 56, grade C; Ora scanned the domain on 18 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for windmill.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Windmill. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for windmill.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Windmill. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/windmill-dev/index.md) ## Sources - [Ora score page for windmill.dev](https://ora.ai/score/windmill.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 18 September 2026, read from GET /api/leaderboard) - [Where Windmill was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Windmill website](https://windmill.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Windsurf MCP server | Agent MCP Directory" description: "Does Windsurf have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/windsurf-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Windsurf MCP server | Agent MCP Directory > Does Windsurf have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/windsurf-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Windsurf: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Windsurf (windsurf.com), so the connector had nothing to connect to. Ora's cached score for windsurf.com is 57, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Windsurf | | --- | --- | | Domain | windsurf.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 57, grade C; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for windsurf.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Windsurf. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for windsurf.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Windsurf. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/windsurf-com/index.md) ## Sources - [Ora score page for windsurf.com](https://ora.ai/score/windsurf.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where Windsurf was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Windsurf website](https://windsurf.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WITAN Markets MCP server | Agent MCP Directory" description: "WITAN Markets has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/witan-markets site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WITAN Markets MCP server | Agent MCP Directory > WITAN Markets has an open MCP server with 8 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/witan-markets Site: Agent MCP Directory Last reviewed: 2026-11-05 # WITAN Markets: MCP server, CLI and agent surfaces Yes: WITAN Markets runs a public MCP server at witan.markets that listed 8 tools to a client with no credentials on 4 November 2026. Examples: search\_knowledge, search\_by\_error, get\_knowledge\_full. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | WITAN Markets | | --- | --- | | Domain | witan.markets | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for witan.markets when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://witan.markets/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | witan 0.15.0 | | Capabilities | tools | | Tools | 8 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,720 ms over 1 attempt | ### Tools listed 8 tools - search\_knowledge - search\_by\_error - get\_knowledge\_full - list\_datasets - dataset\_info - read\_dataset - get\_reviews - list\_requests ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:20Z https://witan.markets/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 2603 ms - 20:05:10Z https://witan.markets/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1720 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://witan.markets/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WITAN Markets. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: witan.markets (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/witan-markets/index.md) ## Sources - [WITAN Markets website](https://witan.markets), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wix MCP server | Agent MCP Directory" description: "Wix: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wix-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wix MCP server | Agent MCP Directory > Wix: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/wix-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wix: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Wix at mcp.wix.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Wix | | --- | --- | | Domain | wix.com | | Category | Commerce Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 610 on the list of 4 November 2026 | | Ora score | 64, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for wix.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.wix.com/sse | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 92 ms over 1 attempt | | Documentation | dev.wix.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:55Z https://mcp.wix.com/sse sent initialize result auth-required (HTTP 401) 91 ms - 20:01:30Z https://mcp.wix.com/sse sent initialize result auth-required (HTTP 401) 92 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token", resource_metadata="https://mcp.wix.com/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.wix.com | | Authorization server metadata | mcp.wix.com | | Registration endpoint | https://mcp.wix.com/register | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.wix.com/sse` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.wix.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.wix.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @wix/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 1.2.8 | | Last publish | 1 November 2026 | | Command names | wix | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.wix/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wix-com/index.md) ## Sources - [Wix MCP documentation](https://dev.wix.com/docs/sdk/articles/use-the-wix-mcp/about-the-wix-mcp), read 4 November 2026 - [Ora score page for wix.com](https://ora.ai/score/wix.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=wix), read 4 November 2026 - [Wix website](https://wix.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wiz MCP server | Agent MCP Directory" description: "Does Wiz have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/wiz-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wiz MCP server | Agent MCP Directory > Does Wiz have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/wiz-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wiz: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Wiz (wiz.io), so the connector had nothing to connect to. Ora's cached score for wiz.io is 58, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Wiz | | --- | --- | | Domain | wiz.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 58, grade C; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for wiz.io, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Wiz. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for wiz.io, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Wiz. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wiz-io/index.md) ## Sources - [Ora score page for wiz.io](https://ora.ai/score/wiz.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 October 2026, read from GET /api/leaderboard) - [Where Wiz was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Wiz website](https://wiz.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wolfram MCP server | Agent MCP Directory" description: "Wolfram has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wolfram-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wolfram MCP server | Agent MCP Directory > Wolfram has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/wolfram-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wolfram: MCP server, CLI and agent surfaces Yes: Wolfram runs a public MCP server at agenttools.wolfram.com that listed 3 tools to a client with no credentials on 4 November 2026. Examples: WolframContext, WolframLanguageEvaluator, WolframAlpha. It speaks streamable-http, protocol 2025-03-26. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Wolfram (registry title: Wolfram Research) | | --- | --- | | Domain | wolfram.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Tranco rank | 4,877 on the list of 4 November 2026 | | Ora score | none: Ora returned no cached score for wolfram.com when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agenttools.wolfram.com/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-03-26 | | Server | Wolfram 2026.09.15 | | Capabilities | tools | | Tools | 3 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,746 ms over 1 attempt | ### Tools listed 3 tools - WolframContext - WolframLanguageEvaluator - WolframAlpha ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:07Z https://agenttools.wolfram.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1812 ms - 20:01:44Z https://agenttools.wolfram.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1746 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://agenttools.wolfram.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Wolfram. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.wolfram/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wolfram-com/index.md) ## Sources - [Where Wolfram was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=wolfram), read 4 November 2026 - [Wolfram website](https://wolfram.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Woodpecker CI MCP server | Agent MCP Directory" description: "Does Woodpecker CI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/woodpecker-ci-org site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Woodpecker CI MCP server | Agent MCP Directory > Does Woodpecker CI have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/woodpecker-ci-org Site: Agent MCP Directory Last reviewed: 2026-11-05 # Woodpecker CI: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Woodpecker CI (woodpecker-ci.org), so the connector had nothing to connect to. Ora's cached score for woodpecker-ci.org is 39, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Woodpecker CI (registry title: woodpecker-ci.org) | | --- | --- | | Domain | woodpecker-ci.org | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 39, grade D; Ora scanned the domain on 6 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for woodpecker-ci.org, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Woodpecker CI. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for woodpecker-ci.org, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Woodpecker CI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/woodpecker-ci-org/index.md) ## Sources - [Ora score page for woodpecker-ci.org](https://ora.ai/score/woodpecker-ci.org?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 6 August 2026, read from GET /api/leaderboard) - [Where Woodpecker CI was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Woodpecker CI website](https://woodpecker-ci.org), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Workamajig MCP server | Agent MCP Directory" description: "Workamajig has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/workamajig-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Workamajig MCP server | Agent MCP Directory > Workamajig has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/workamajig-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Workamajig: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Workamajig; the connector tried mcp.workamajig.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=us-ascii). ## Fact sheet | Company | Workamajig (registry title: workamajig.com) | | --- | --- | | Domain | workamajig.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 62, grade C; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for workamajig.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.workamajig.com/mcp | | --- | --- | | How it was found | mcp.workamajig.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,579 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=us-ascii) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:20Z https://mcp.workamajig.com/mcp sent initialize result no-answer (HTTP 404) 1688 ms - 20:05:11Z https://mcp.workamajig.com/mcp sent initialize result no-answer (HTTP 404) 1579 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.workamajig.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/html; charset=us-ascii). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Workamajig. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/workamajig-com/index.md) ## Sources - [Ora score page for workamajig.com](https://ora.ai/score/workamajig.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 27 August 2026, read from GET /api/leaderboard) - [Where Workamajig was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Workamajig website](https://workamajig.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Workato MCP server | Agent MCP Directory" description: "Workato has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/workato-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Workato MCP server | Agent MCP Directory > Workato has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/workato-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Workato: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Workato; the connector tried mcp.workato.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 400, GET HTTP 400 text/plain; charset=utf-8). ## Fact sheet | Company | Workato (registry title: workato.com) | | --- | --- | | Domain | workato.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Ora score | 64, grade C; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for workato.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.workato.com/mcp | | --- | --- | | How it was found | mcp.workato.com was tried as a guess and did not answer | | HTTP status | 400 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 943 ms over 2 attempts | | Result | no MCP answer (POST HTTP 400, GET HTTP 400 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:19Z https://mcp.workato.com/mcp sent initialize result no-answer (HTTP 400) 901 ms - 20:05:10Z https://mcp.workato.com/mcp sent initialize result no-answer (HTTP 400) 943 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.workato.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 400, GET HTTP 400 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Workato. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/workato-com/index.md) ## Sources - [Ora score page for workato.com](https://ora.ai/score/workato.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 2 November 2026, read from GET /api/leaderboard) - [Where Workato was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Workato website](https://workato.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Workflowy MCP server | Agent MCP Directory" description: "Does Workflowy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/workflowy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Workflowy MCP server | Agent MCP Directory > Does Workflowy have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/workflowy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Workflowy: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Workflowy (workflowy.com), so the connector had nothing to connect to. Ora's cached score for workflowy.com is 59, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Workflowy (registry title: workflowy.com) | | --- | --- | | Domain | workflowy.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 59, grade C; Ora scanned the domain on 30 August 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for workflowy.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Workflowy. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for workflowy.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Workflowy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/workflowy-com/index.md) ## Sources - [Ora score page for workflowy.com](https://ora.ai/score/workflowy.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 30 August 2026, read from GET /api/leaderboard) - [Where Workflowy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Workflowy website](https://workflowy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WorkOS MCP server | Agent MCP Directory" description: "WorkOS: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/workos-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WorkOS MCP server | Agent MCP Directory > WorkOS: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/workos-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WorkOS: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for WorkOS at mcp.workos.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | WorkOS | | --- | --- | | Domain | workos.com | | Category | Identity & Auth (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 86, grade A; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for workos.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.workos.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 549 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:19Z https://mcp.workos.com/mcp sent initialize result auth-required (HTTP 401) 501 ms - 20:05:10Z https://mcp.workos.com/mcp sent initialize result auth-required (HTTP 401) 549 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="unauthorized", error_description="Authorization needed", resource_metadata="https://mcp.workos.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.workos.com | | Authorization server metadata | signin.workos.com | | Registration endpoint | https://signin.workos.com/oauth2/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://mcp.workos.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.workos.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://signin.workos.com/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WorkOS. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: workos.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: workos.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: workos.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.workos/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/workos-com/index.md) ## Sources - [Ora score page for workos.com](https://ora.ai/score/workos.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/leaderboard) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=workos), read 4 November 2026 - [WorkOS website](https://workos.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wp MCP server | Agent MCP Directory" description: "Does Wp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/wp-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wp MCP server | Agent MCP Directory > Does Wp have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/wp-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wp: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Wp (wp.com), so the connector had nothing to connect to. Ora's cached score for wp.com is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Wp (registry title: wp.com) | | --- | --- | | Domain | wp.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 487 on the list of 4 November 2026 | | Ora score | 46, grade D; Ora scanned the domain on 26 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for wp.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Wp. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for wp.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Wp. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wp-com/index.md) ## Sources - [Ora score page for wp.com](https://ora.ai/score/wp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 September 2026, read from GET /api/score) - [Where Wp was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Wp website](https://wp.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WP Engine MCP server | Agent MCP Directory" description: "Does WP Engine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wpengine-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WP Engine MCP server | Agent MCP Directory > Does WP Engine have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/wpengine-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WP Engine: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for WP Engine (wpengine.com), so the connector had nothing to connect to. Ora's cached score for wpengine.com is 68, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | WP Engine | | --- | --- | | Domain | wpengine.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Tranco rank | 2,347 on the list of 4 November 2026 | | Ora score | 68, grade C; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for wpengine.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for WP Engine. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for wpengine.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for WP Engine. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wpengine-com/index.md) ## Sources - [Ora score page for wpengine.com](https://ora.ai/score/wpengine.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 5 November 2026, read from GET /api/score) - [Where WP Engine was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [WP Engine website](https://wpengine.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WPWriter MCP server | Agent MCP Directory" description: "WPWriter: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/wpwriter-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WPWriter MCP server | Agent MCP Directory > WPWriter: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/wpwriter-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WPWriter: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for WPWriter at mcp.wpwriter.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | WPWriter (registry title: WPWriter: WordPress AI Content & SEO) | | --- | --- | | Domain | wpwriter.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for wpwriter.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.wpwriter.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 553 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:20Z https://mcp.wpwriter.com/mcp sent initialize result auth-required (HTTP 401) 1367 ms - 20:05:10Z https://mcp.wpwriter.com/mcp sent initialize result auth-required (HTTP 401) 553 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.wpwriter.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.wpwriter.com | | Authorization server metadata | mcp.wpwriter.com | | Registration endpoint | https://mcp.wpwriter.com/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.wpwriter.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.wpwriter.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.wpwriter.com/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WPWriter. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.wpwriter/wordpress | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wpwriter-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=wpwriter), read 4 November 2026 - [WPWriter website](https://wpwriter.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WRDO MCP server | Agent MCP Directory" description: "WRDO has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wrdo-co-za site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WRDO MCP server | Agent MCP Directory > WRDO has an open MCP server with 6 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/wrdo-co-za Site: Agent MCP Directory Last reviewed: 2026-11-05 # WRDO: MCP server, CLI and agent surfaces Yes: WRDO runs a public MCP server at api.wrdo.co.za that listed 6 tools to a client with no credentials on 4 November 2026. Examples: search\_local\_businesses, list\_categories, list\_areas. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for wrdo.co.za is 48, grade C, read on 5 November 2026. ## Fact sheet | Company | WRDO | | --- | --- | | Domain | wrdo.co.za | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 48, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for wrdo.co.za, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.wrdo.co.za/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | WRDO 1.1.0 | | Capabilities | tools | | Tools | 6 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 822 ms over 1 attempt | ### Tools listed 6 tools - search\_local\_businesses - list\_categories - list\_areas - get\_business - start\_request - get\_price\_list ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:20Z https://api.wrdo.co.za/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 876 ms - 20:05:11Z https://api.wrdo.co.za/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 822 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.wrdo.co.za/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for WRDO. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wrdo-co-za/index.md) ## Sources - [Ora score page for wrdo.co.za](https://ora.ai/score/wrdo.co.za?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/score) - [WRDO website](https://wrdo.co.za), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Wrike MCP server | Agent MCP Directory" description: "Wrike has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/wrike-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Wrike MCP server | Agent MCP Directory > Wrike has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/wrike-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Wrike: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for Wrike; the connector tried mcp.wrike.com as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain;charset=utf-8). ## Fact sheet | Company | Wrike (registry title: wrike.com) | | --- | --- | | Domain | wrike.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | No answer | | Ora score | 66, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for wrike.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.wrike.com/mcp | | --- | --- | | How it was found | mcp.wrike.com was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 132 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain;charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:19Z https://mcp.wrike.com/mcp sent initialize result no-answer (HTTP 404) 191 ms - 20:05:10Z https://mcp.wrike.com/mcp sent initialize result no-answer (HTTP 404) 132 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.wrike.com/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain;charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Wrike. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wrike-com/index.md) ## Sources - [Ora score page for wrike.com](https://ora.ai/score/wrike.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 26 October 2026, read from GET /api/leaderboard) - [Where Wrike was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Wrike website](https://wrike.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "WunderGraph MCP server | Agent MCP Directory" description: "Does WunderGraph have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/wundergraph-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # WunderGraph MCP server | Agent MCP Directory > Does WunderGraph have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/wundergraph-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # WunderGraph: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for WunderGraph (wundergraph.com), so the connector had nothing to connect to. Ora's cached score for wundergraph.com is 70, grade B, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | WunderGraph (registry title: wundergraph.com) | | --- | --- | | Domain | wundergraph.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 70, grade B; Ora scanned the domain on 28 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for wundergraph.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for WunderGraph. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for wundergraph.com, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for WunderGraph. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/wundergraph-com/index.md) ## Sources - [Ora score page for wundergraph.com](https://ora.ai/score/wundergraph.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 28 September 2026, read from GET /api/leaderboard) - [Where WunderGraph was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [WunderGraph website](https://wundergraph.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Xenition MCP server | Agent MCP Directory" description: "Xenition has an open MCP server with 68 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/xenition-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Xenition MCP server | Agent MCP Directory > Xenition has an open MCP server with 68 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/xenition-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Xenition: MCP server, CLI and agent surfaces Yes: Xenition runs a public MCP server at api.xenition.com that listed 68 tools to a client with no credentials on 4 November 2026. Examples: add\_event, add\_ledger\_entry, add\_note. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Xenition | | --- | --- | | Domain | xenition.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for xenition.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://api.xenition.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | xenition 0.1.0 | | Capabilities | logging, resources, tools | | Tools | 68 | | Resources | 30 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,159 ms over 1 attempt | ### Tools listed 68 tools; the first 40 names are recorded - add\_event - add\_ledger\_entry - add\_note - add\_rows - add\_task - add\_to\_knowledge - app\_status - approve\_action - ask\_workspace - build\_app - build\_app\_from\_template - check\_3d\_model - check\_agent\_run - complete\_task - create\_3d\_model - create\_automation - create\_board - create\_diagram - create\_document - create\_image - create\_shared\_form - create\_slides - create\_speech - create\_spreadsheet - create\_video - deny\_action - deploy\_app - discover\_search - discover\_sources - edit\_app - edit\_artifact - edit\_image - edit\_video - export\_pdf - extract\_from\_artifact - find\_app\_templates - find\_forms - form\_responses - get\_artifact - get\_mission ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:21Z https://api.xenition.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1283 ms - 20:05:12Z https://api.xenition.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 1159 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://api.xenition.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Xenition. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.xenition.api/xenition | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/xenition-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=xenition), read 4 November 2026 - [Xenition website](https://xenition.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "XMemo MCP server | Agent MCP Directory" description: "XMemo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/xmemo-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # XMemo MCP server | Agent MCP Directory > XMemo: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/xmemo-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # XMemo: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for XMemo at xmemo.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | XMemo | | --- | --- | | Domain | xmemo.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 81, grade B; Ora scanned the domain on 14 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for xmemo.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://xmemo.dev/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,490 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:22Z https://xmemo.dev/mcp sent initialize result auth-required (HTTP 401) 1723 ms - 20:05:12Z https://xmemo.dev/mcp sent initialize result auth-required (HTTP 401) 1490 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://xmemo.dev/.well-known/oauth-protected-resource", scope="memory:read memory:write knowledge:read" | | Protected resource metadata | xmemo.dev | | Authorization server metadata | xmemo.dev | | Registration endpoint | https://xmemo.dev/oauth/register | ### The sign-in route, step by step 1. Request `https://xmemo.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://xmemo.dev/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://xmemo.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for XMemo. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/xmemo-dev/index.md) ## Sources - [Ora score page for xmemo.dev](https://ora.ai/score/xmemo.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 14 October 2026, read from GET /api/score) - [XMemo website](https://xmemo.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Xquik MCP server | Agent MCP Directory" description: "Xquik has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/xquik-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Xquik MCP server | Agent MCP Directory > Xquik has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/xquik-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Xquik: MCP server, CLI and agent surfaces Yes: Xquik runs a public MCP server at xquik.com that listed 4 tools to a client with no credentials on 4 November 2026. Examples: docs, search, execute. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for xquik.com is 92, grade A, read on 5 November 2026. ## Fact sheet | Company | Xquik (registry title: Xquik MCP Server) | | --- | --- | | Domain | xquik.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 92, grade A; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for xquik.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://xquik.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | xquik 2.6.64 | | Capabilities | resources, tools, extensions | | Tools | 4 | | Resources | 1 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 485 ms over 1 attempt | ### Tools listed 4 tools - docs - search - execute - whoami ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:21Z https://xquik.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 646 ms - 20:05:11Z https://xquik.com/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 485 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://xquik.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Xquik. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: xquik.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.xquik/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/xquik-com/index.md) ## Sources - [Ora score page for xquik.com](https://ora.ai/score/xquik.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=xquik), read 4 November 2026 - [Xquik website](https://xquik.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "YouSpot MCP server | Agent MCP Directory" description: "YouSpot has an open MCP server with 171 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/youspot-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # YouSpot MCP server | Agent MCP Directory > YouSpot has an open MCP server with 171 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/youspot-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # YouSpot: MCP server, CLI and agent surfaces Yes: YouSpot runs a public MCP server at youspot.com that listed 171 tools to a client with no credentials on 4 November 2026. Examples: read\_web\_page, web\_search, check\_page\_changes. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for youspot.com is 98, grade A+, read on 5 November 2026. ## Fact sheet | Company | YouSpot | | --- | --- | | Domain | youspot.com | | Category | CRM (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 98, grade A+; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for youspot.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://youspot.com/mcp/v1 | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-06-18 | | Server | connect 1.0.0 | | Capabilities | prompts, resources, tools | | Tools | 171 | | Resources | 4 | | Prompts | 1 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,774 ms over 1 attempt | ### Tools listed 171 tools; the first 40 names are recorded - read\_web\_page - web\_search - check\_page\_changes - extract\_web\_page - what\_needs\_attention - slack\_waiting\_on\_me - mail\_waiting\_on\_me - get\_my\_plan - draft\_cloud\_agent - message\_agent - agent\_reply - research\_company - my\_topics - match\_my\_network - get\_domain\_info - get\_domain\_value - send\_email - read\_file - save\_file\_from\_url - save\_text\_file - import\_contacts\_from\_file - search\_gmail\_messages - get\_gmail\_message - list\_gmail\_labels - create\_gmail\_draft - archive\_gmail\_message - get\_granola\_notes - get\_granola\_note - search\_granola\_transcripts - get\_granola\_status - sync\_granola\_notes - get\_calendar\_events - list\_google\_calendars - create\_calendar\_event - update\_calendar\_event - list\_graph\_objects - get\_graph\_object - set\_graph\_object\_fields - enrich\_graph\_object - search\_graph\_objects ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:22Z https://youspot.com/mcp/v1 sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1857 ms - 20:05:13Z https://youspot.com/mcp/v1 sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1774 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://youspot.com/mcp/v1` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for YouSpot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: youspot.com (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: youspot.com/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: youspot.com/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Found: youspot.com/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: youspot.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.youspot/youspot | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/youspot-com/index.md) ## Sources - [Ora score page for youspot.com](https://ora.ai/score/youspot.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where YouSpot was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.youspot%2Fyouspot), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=youspot), read 4 November 2026 - [YouSpot website](https://youspot.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zapier MCP server | Agent MCP Directory" description: "Zapier: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zapier-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zapier MCP server | Agent MCP Directory > Zapier: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zapier-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zapier: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Zapier at mcp.zapier.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Zapier | | --- | --- | | Domain | zapier.com | | Category | Productivity (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 3,001 on the list of 4 November 2026 | | Ora score | 84, grade B; Ora scanned the domain on 4 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for zapier.com, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zapier.com/api/mcp/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 669 ms over 1 attempt | | Documentation | zapier.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:01Z https://mcp.zapier.com/api/mcp/mcp sent initialize result auth-required (HTTP 401) 661 ms - 20:01:37Z https://mcp.zapier.com/api/mcp/mcp sent initialize result auth-required (HTTP 401) 669 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Zapier MCP", error="invalid_token" | | Protected resource metadata | mcp.zapier.com | | Authorization server metadata | mcp.zapier.com | | Registration endpoint | https://mcp.zapier.com/api/v1/oauth/register | | Auth as listed by a registry | API Key (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.zapier.com/api/mcp/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.zapier.com/.well-known/oauth-protected-resource/api/mcp/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.zapier.com/api/v1/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | zapier-platform-cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 19.3.0 | | Last publish | 30 October 2026 | | Command names | zapier-platform | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.zapier/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zapier-com/index.md) ## Sources - [Zapier MCP documentation](https://zapier.com/mcp), read 4 November 2026 - [Ora score page for zapier.com](https://ora.ai/score/zapier.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 4 November 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=zapier), read 4 November 2026 - [Zapier website](https://zapier.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zed MCP server | Agent MCP Directory" description: "Does Zed have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/zed-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zed MCP server | Agent MCP Directory > Does Zed have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/zed-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zed: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for Zed (zed.dev), so the connector had nothing to connect to. Ora's cached score for zed.dev is 57, grade C, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | Zed | | --- | --- | | Domain | zed.dev | | Category | Developer Tools (Ora leaderboard category) | | MCP server | None found | | Ora score | 57, grade C; Ora scanned the domain on 13 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for zed.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for Zed. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for zed.dev, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for Zed. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zed-dev/index.md) ## Sources - [Ora score page for zed.dev](https://ora.ai/score/zed.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 13 October 2026, read from GET /api/leaderboard) - [Where Zed was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [Zed website](https://zed.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zenable MCP server | Agent MCP Directory" description: "Zenable: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security." canonical: https://agentmcpdirectory.com/directory/zenable-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zenable MCP server | Agent MCP Directory > Zenable: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Security. Source: https://agentmcpdirectory.com/directory/zenable-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zenable: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Zenable at mcp.zenable.app answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Zenable | | --- | --- | | Domain | zenable.io | | Category | Security (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for zenable.io when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zenable.app/ | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,611 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:23Z https://mcp.zenable.app/ sent initialize result auth-required (HTTP 401) 1358 ms - 20:05:13Z https://mcp.zenable.app/ sent initialize result auth-required (HTTP 401) 1611 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.zenable.app/.well-known/oauth-protected-resource" | | Protected resource metadata | mcp.zenable.app | | Authorization server metadata | zenable.us.auth0.com | | Registration endpoint | https://zenable.us.auth0.com/oidc/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.zenable.app/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.zenable.app/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://zenable.us.auth0.com/oidc/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zenable. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zenable-io/index.md) ## Sources - [Where Zenable was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Zenable website](https://zenable.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zentrik MCP server | Agent MCP Directory" description: "Zentrik: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools." canonical: https://agentmcpdirectory.com/directory/zentrik-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zentrik MCP server | Agent MCP Directory > Zentrik: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Agent Tools. Source: https://agentmcpdirectory.com/directory/zentrik-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zentrik: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Zentrik at zentrik.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Zentrik | | --- | --- | | Domain | zentrik.ai | | Category | Agent Tools (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 66, grade C; Ora scanned the domain on 19 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for zentrik.ai, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://zentrik.ai/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 698 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:22Z https://zentrik.ai/mcp sent initialize result auth-required (HTTP 401) 790 ms - 20:05:12Z https://zentrik.ai/mcp sent initialize result auth-required (HTTP 401) 698 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://zentrik.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | zentrik.ai | | Authorization server metadata | zentrik.ai | | Registration endpoint | https://zentrik.ai/oauth/register | | Client ID metadata documents | supported | ### The sign-in route, step by step 1. Request `https://zentrik.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://zentrik.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://zentrik.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zentrik. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.zentrik/mcp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zentrik-ai/index.md) ## Sources - [Ora score page for zentrik.ai](https://ora.ai/score/zentrik.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 September 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=zentrik), read 4 November 2026 - [Zentrik website](https://zentrik.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ZeroDev MCP server | Agent MCP Directory" description: "Does ZeroDev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zerodev-app site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ZeroDev MCP server | Agent MCP Directory > Does ZeroDev have an MCP server? None found, and nothing was connected: no endpoint is on record. Checked 4 November 2026. Source: https://agentmcpdirectory.com/directory/zerodev-app Site: Agent MCP Directory Last reviewed: 2026-11-05 # ZeroDev: MCP server, CLI and agent surfaces Not connected. No source read for this edition names an MCP endpoint for ZeroDev (zerodev.app), so the connector had nothing to connect to. Ora's cached score for zerodev.app is 46, grade D, read on 5 November 2026. The company was added from Ora's public leaderboard. ## Fact sheet | Company | ZeroDev (registry title: zerodev.app) | | --- | --- | | Domain | zerodev.app | | Category | Infrastructure (Ora leaderboard category) | | MCP server | None found | | Ora score | 46, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for zerodev.app, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server No MCP endpoint is on record for ZeroDev. The sources read for this edition are the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard. None names an endpoint for zerodev.app, so the connector had nothing to call and nothing was connected. The connector guesses mcp. only for Developer Tools and Infrastructure rows whose subdomain resolves in DNS; this row has no such endpoint. That is a statement about these sources on 4 November 2026, not proof that no server exists. | Source | Result | | --- | --- | | Official MCP Registry | No entry for this domain | | GitHub MCP Registry | No entry for this domain | | awesome-remote-mcp-servers | Not listed | ## CLI No CLI is on record for ZeroDev. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zerodev-app/index.md) ## Sources - [Ora score page for zerodev.app](https://ora.ai/score/zerodev.app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where ZeroDev was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ZeroDev website](https://zerodev.app), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ZeroEntropy MCP server | Agent MCP Directory" description: "ZeroEntropy has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources." canonical: https://agentmcpdirectory.com/directory/zeroentropy-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ZeroEntropy MCP server | Agent MCP Directory > ZeroEntropy has an MCP endpoint on record that did not answer a handshake, so it is not counted. Directory entry with sources. Source: https://agentmcpdirectory.com/directory/zeroentropy-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # ZeroEntropy: MCP server, CLI and agent surfaces Not verified. No source names an endpoint for ZeroEntropy; the connector tried mcp.zeroentropy.dev as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). ## Fact sheet | Company | ZeroEntropy (registry title: zeroentropy.dev) | | --- | --- | | Domain | zeroentropy.dev | | Category | Infrastructure (Ora leaderboard category) | | MCP server | No answer | | Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for zeroentropy.dev, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zeroentropy.dev/mcp | | --- | --- | | How it was found | mcp.zeroentropy.dev was tried as a guess and did not answer | | HTTP status | 404 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,300 ms over 2 attempts | | Result | no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8) | ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:23Z https://mcp.zeroentropy.dev/mcp sent initialize result no-answer (HTTP 404) 1267 ms - 20:05:13Z https://mcp.zeroentropy.dev/mcp sent initialize result no-answer (HTTP 404) 1300 ms ## Authentication | Auth type | Auth not determined | | --- | --- | ### The sign-in route, step by step 1. Request `https://mcp.zeroentropy.dev/mcp`. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8). 2. Check the vendor's docs for the sign-in route before wiring a client. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ZeroEntropy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The path answered with a web page, not an OpenAPI file. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | The path answered with a web page, not the file. Not counted. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zeroentropy-dev/index.md) ## Sources - [Ora score page for zeroentropy.dev](https://ora.ai/score/zeroentropy.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where ZeroEntropy was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ZeroEntropy website](https://zeroentropy.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "ZeroEval MCP server | Agent MCP Directory" description: "ZeroEval has an open MCP server with 29 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zeroeval-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # ZeroEval MCP server | Agent MCP Directory > ZeroEval has an open MCP server with 29 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zeroeval-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # ZeroEval: MCP server, CLI and agent surfaces Yes: ZeroEval runs a public MCP server at mcp.zeroeval.com, found by guessing the subdomain, and it listed 29 tools to a client with no credentials on 4 November 2026. Examples: list-traces, get-trace, list-judges. It speaks streamable-http, protocol 2025-11-25. Endpoint found by subdomain guess, verified by connecting. ## Fact sheet | Company | ZeroEval (registry title: zeroeval.com) | | --- | --- | | Domain | zeroeval.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 65, grade C; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for zeroeval.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zeroeval.com/mcp | | --- | --- | | How it was found | endpoint found by subdomain guess, verified by connecting | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | zeroeval-mcp 1.0.0 | | Capabilities | logging, completions, tools, prompts, resources | | Tools | 29 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,601 ms over 1 attempt | ### Tools listed 29 tools - list-traces - get-trace - list-judges - get-judge - list-judge-evaluations - get-judge-criteria - create-judge - link-judge-to-prompt - unlink-judge-from-prompt - create-judge-feedback - list-prompts - get-prompt - list-prompt-versions - create-prompt-feedback - list-optimization-runs - get-optimization-run - get-project-summary - start-prompt-optimization - start-judge-optimization - cancel-optimization-run - preview-optimization-deploy - deploy-optimization-run - investigate-prompt-issues - investigate-judge-issues - prepare-prompt-optimization - prepare-judge-optimization - list-issues - get-issue - investigate-issue ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:23Z https://mcp.zeroeval.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1683 ms - 20:05:13Z https://mcp.zeroeval.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1601 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.zeroeval.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for ZeroEval. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zeroeval-com/index.md) ## Sources - [Ora score page for zeroeval.com](https://ora.ai/score/zeroeval.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 October 2026, read from GET /api/score) - [Where ZeroEval was found](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 4 November 2026 - [ZeroEval website](https://zeroeval.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "zeroheight MCP server | Agent MCP Directory" description: "zeroheight: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools." canonical: https://agentmcpdirectory.com/directory/zeroheight-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # zeroheight MCP server | Agent MCP Directory > zeroheight: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Developer Tools. Source: https://agentmcpdirectory.com/directory/zeroheight-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # zeroheight: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for zeroheight at mcp.zeroheight.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | zeroheight (registry title: zeroheight.com) | | --- | --- | | Domain | zeroheight.com | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 37, grade D; Ora scanned the domain on 19 April 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for zeroheight.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zeroheight.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 901 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:23Z https://mcp.zeroheight.com/mcp sent initialize result auth-required (HTTP 401) 844 ms - 20:05:13Z https://mcp.zeroheight.com/mcp sent initialize result auth-required (HTTP 401) 901 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.zeroheight.com/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.zeroheight.com | | Authorization server metadata | auth.zeroheight.com | | Registration endpoint | https://auth.zeroheight.com/oauth/client/register | ### The sign-in route, step by step 1. Request `https://mcp.zeroheight.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.zeroheight.com/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://auth.zeroheight.com/oauth/client/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for zeroheight. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.zeroheight/zeroheight | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zeroheight-com/index.md) ## Sources - [Ora score page for zeroheight.com](https://ora.ai/score/zeroheight.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 19 April 2026, read from GET /api/leaderboard) - [Where zeroheight was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.zeroheight%2Fzeroheight), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=zeroheight), read 4 November 2026 - [zeroheight website](https://zeroheight.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zinc MCP server | Agent MCP Directory" description: "Zinc has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zinc-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zinc MCP server | Agent MCP Directory > Zinc has an open MCP server with 9 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zinc-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zinc: MCP server, CLI and agent surfaces Yes: Zinc runs a public MCP server at mcp.zinc.com that listed 9 tools to a client with no credentials on 4 November 2026. Examples: list-orders, get-order, get-order-tracking. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for zinc.com is 81, grade B, read on 5 November 2026. ## Fact sheet | Company | Zinc | | --- | --- | | Domain | zinc.com | | Category | E-commerce (Ora leaderboard category) | | MCP server | Verified (No authentication) | | Ora score | 81, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for zinc.com, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zinc.com/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | zinc 1.1.0 | | Capabilities | logging, tools, prompts, resources | | Tools | 9 | | Resources | 4 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,350 ms over 1 attempt | ### Tools listed 9 tools - list-orders - get-order - get-order-tracking - list-addresses - prepare-order - place-order - get-payment-status - search-products - send\_feedback ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:24Z https://mcp.zinc.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1906 ms - 20:05:13Z https://mcp.zinc.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1350 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.zinc.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zinc. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: www.zinc.com (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.zinc.www/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zinc-com/index.md) ## Sources - [Ora score page for zinc.com](https://ora.ai/score/zinc.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/score) - [Where Zinc was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.zinc.www%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=zinc), read 4 November 2026 - [Zinc website](https://zinc.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zine MCP server | Agent MCP Directory" description: "Zine: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zine-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zine MCP server | Agent MCP Directory > Zine: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zine-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zine: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Zine at www.zine.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Zine | | --- | --- | | Domain | zine.ai | | Category | AI & ML (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for zine.ai when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://www.zine.ai/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,135 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:24Z https://www.zine.ai/mcp sent initialize result auth-required (HTTP 401) 1303 ms - 20:05:13Z https://www.zine.ai/mcp sent initialize result auth-required (HTTP 401) 1135 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="Zine MCP", resource_metadata="https://www.zine.ai/.well-known/oauth-protected-resource" | | Protected resource metadata | www.zine.ai | | Authorization server metadata | www.zine.ai | | Registration endpoint | https://www.zine.ai/api/auth/mcp-oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://www.zine.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://www.zine.ai/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://www.zine.ai/api/auth/mcp-oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zine. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.zine/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zine-ai/index.md) ## Sources - [Where Zine was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=zine), read 4 November 2026 - [Zine website](https://zine.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zip-Codes.com MCP server | Agent MCP Directory" description: "Zip-Codes.com has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zip-codes-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zip-Codes.com MCP server | Agent MCP Directory > Zip-Codes.com has an open MCP server with 12 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zip-codes-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zip-Codes.com: MCP server, CLI and agent surfaces Yes: Zip-Codes.com runs a public MCP server at mcp.zip-codes.com that listed 12 tools to a client with no credentials on 4 November 2026. Examples: suggest\_places, zip\_lookup, zip\_facts. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Zip-Codes.com (registry title: Zip-Codes.com Location Intelligence: Spatial Analysis, Districts & 14+ Years of Demographics) | | --- | --- | | Domain | zip-codes.com | | Category | Developer Tools (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for zip-codes.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zip-codes.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | zip-codes 1.0.0 | | Capabilities | logging, tools | | Tools | 12 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,348 ms over 2 attempts | | Result | initialize error: Protocol version '2026-07-28' is not available through the initialize handshake. | ### Tools listed 12 tools - suggest\_places - zip\_lookup - zip\_facts - quick\_zip - city\_name\_rules - buy\_credits - radius\_search - about\_data - distance - validate\_address - county\_reference - metro\_area\_reference ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:25Z https://mcp.zip-codes.com/mcp sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 1719 ms - 20:05:14Z https://mcp.zip-codes.com/mcp sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 1348 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.zip-codes.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zip-Codes.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.zip-codes/api | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zip-codes-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=zip-codes), read 4 November 2026 - [Zip-Codes.com website](https://zip-codes.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Ziptax MCP server | Agent MCP Directory" description: "Ziptax has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zip-tax site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Ziptax MCP server | Agent MCP Directory > Ziptax has an open MCP server with 2 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zip-tax Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ziptax: MCP server, CLI and agent surfaces Yes: Ziptax runs a public MCP server at mcp.zip-tax.com that listed 2 tools to a client with no credentials on 4 November 2026. Examples: get\_account\_metrics, lookup\_tax\_rate. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Ziptax (registry title: Ziptax Sales Tax API) | | --- | --- | | Domain | zip.tax | | Category | CRM (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for zip.tax when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zip-tax.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | ZipTax Sales Tax API 1.0.5 | | Capabilities | tools | | Tools | 2 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 1,379 ms over 1 attempt | ### Tools listed 2 tools - get\_account\_metrics - lookup\_tax\_rate ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:25Z https://mcp.zip-tax.com/ sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1452 ms - 20:05:14Z https://mcp.zip-tax.com/ sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1379 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.zip-tax.com/` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Ziptax. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zip-tax/index.md) ## Sources - [Ziptax website](https://zip.tax), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zip1 MCP server | Agent MCP Directory" description: "Zip1 has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zip1-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zip1 MCP server | Agent MCP Directory > Zip1 has an open MCP server with 4 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zip1-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zip1: MCP server, CLI and agent surfaces Yes: Zip1 runs a public MCP server at zip1.io that listed 4 tools to a client with no credentials on 4 November 2026. Examples: create\_short\_url, get\_url\_stats, validate\_url. It speaks streamable-http, protocol 2024-11-05. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Zip1 (registry title: zip1.io) | | --- | --- | | Domain | zip1.io | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for zip1.io when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://zip1.io/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2024-11-05 | | Server | zip1-io-mcp 1.0.0 | | Capabilities | tools | | Tools | 4 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:05 UTC | | Handshake time | 595 ms over 1 attempt | ### Tools listed 4 tools - create\_short\_url - get\_url\_stats - validate\_url - generate\_short\_code ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:24Z https://zip1.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 683 ms - 20:05:14Z https://zip1.io/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 595 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://zip1.io/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zip1. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Not read: the site's robots.txt disallows the path for this crawler. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zip1-io/index.md) ## Sources - [Where Zip1 was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Zip1 website](https://zip1.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zomato MCP server | Agent MCP Directory" description: "Zomato: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zomato-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zomato MCP server | Agent MCP Directory > Zomato: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zomato-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zomato: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Zomato at mcp-server.zomato.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Zomato (registry title: zomato.com) | | --- | --- | | Domain | zomato.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 4,689 on the list of 4 November 2026 | | Ora score | 16, grade F; Ora scanned the domain on 23 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for zomato.com, a vendor-published score) | | Company found through | the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp-server.zomato.com/mcp | | --- | --- | | How it was found | listed in the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,212 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:06Z https://mcp-server.zomato.com/mcp sent initialize result auth-required (HTTP 401) 1301 ms - 20:01:43Z https://mcp-server.zomato.com/mcp sent initialize result auth-required (HTTP 401) 1212 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Authentication required" | | Authorization server metadata | mcp-server.zomato.com | | Registration endpoint | https://mcp-server.zomato.com/register | ### The sign-in route, step by step 1. Request `https://mcp-server.zomato.com/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata to find the authorization server. 3. Register a client at the registration endpoint `https://mcp-server.zomato.com/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zomato. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | A2A agent card (older path) | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | agents.json | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | OAuth authorization server metadata | Not read: robots.txt or the crawl budget kept the shared crawl away from this path. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.zomato/mcp | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zomato-com/index.md) ## Sources - [Ora score page for zomato.com](https://ora.ai/score/zomato.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 23 August 2026, read from GET /api/score) - [Where Zomato was found](https://registry.modelcontextprotocol.io/v0/servers?search=com.zomato%2Fmcp), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=zomato), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Zoom MCP server | Agent MCP Directory" description: "Zoom: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/zoom-us site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Zoom MCP server | Agent MCP Directory > Zoom: sign-in required (OAuth), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/zoom-us Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zoom: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Zoom at mcp.zoom.us answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Zoom | | --- | --- | | Domain | zoom.us | | Category | Communication & Support (Ora leaderboard category) | | MCP server | Sign-in required (OAuth without client registration) | | Tranco rank | 64 on the list of 4 November 2026 | | Ora score | 61, grade C; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for zoom.us, a vendor-published score) | | Company found through | the awesome-remote-mcp-servers list; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.zoom.us/mcp/zoom/streamable | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 641 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:52Z https://mcp.zoom.us/mcp/zoom/streamable sent initialize result auth-required (HTTP 401) 1035 ms - 20:01:26Z https://mcp.zoom.us/mcp/zoom/streamable sent initialize result auth-required (HTTP 401) 641 ms ## Authentication | Auth type | OAuth without client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://zoom.us/.well-known/oauth-protected-resource/mcp/zoom/streamable" | | Protected resource metadata | zoom.us | | Authorization server metadata | zoom.us | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.zoom.us/mcp/zoom/streamable` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the OAuth metadata at `https://zoom.us/.well-known/oauth-authorization-server`. It lists no registration endpoint. 3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one. 4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Zoom. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: zoom.us/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/zoom-us/index.md) ## Sources - [Ora score page for zoom.us](https://ora.ai/score/zoom.us?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 25 October 2026, read from GET /api/score) - [Where Zoom was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [Zoom website](https://zoom.us), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Editorial policy | Agent MCP Directory" description: "How Agent MCP Directory sources, dates, labels and corrects what it publishes: primary sources first, vendor claims marked, no figure without a read date." canonical: https://agentmcpdirectory.com/editorial-policy site: "Agent MCP Directory" last_updated: 2026-11-04 section: "About" --- # Editorial policy | Agent MCP Directory > How Agent MCP Directory sources, dates, labels and corrects what it publishes: primary sources first, vendor claims marked, no figure without a read date. Source: https://agentmcpdirectory.com/editorial-policy Site: Agent MCP Directory Last reviewed: 2026-11-04 # Editorial policy Every fact on this site has a source and a read date. Primary sources come first. What a company says about its own product is labelled a vendor claim, and that includes Ora's scores. A row changes only after a new connector run or a correction with a source. ## Sources and dates - Each page ends with its sources, each with the date it was read, and with the date the page was last reviewed. - Primary means the maintainer of the thing described: a specification, a changelog, a registry API. Vendor means a company describing its own product; such statements are labelled as claims. - Prices and scores carry the date read and are treated as stale after 60 days. ## Rows - A row is added when a source lists the company or when an endpoint is submitted, and it is published after the connector has tried it. - A row is counted as having an MCP server only under the rules on [the method page](https://agentmcpdirectory.com/method/#counting). - A row is removed only if the company asks, shows the endpoint is not theirs, or the domain is a platform that hosts other people's sites. ## Scores and verdicts The host rubric is published. A cell changes only with a source, and a verdict by reader type changes only when the sourced difference it rests on changes. ## Corrections Errors are fixed in place and logged on [the corrections page](https://agentmcpdirectory.com/corrections/) with the date. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/editorial-policy/index.md) ## Sources - [Model Context Protocol specification](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "FAQ: MCP servers, registries and this directory | Agent MCP Directory" description: "30 questions on MCP versions, registries, hosts, OAuth, WebMCP and A2A, answered with sources, including how this directory verifies a server." canonical: https://agentmcpdirectory.com/faq site: "Agent MCP Directory" last_updated: 2026-11-05 section: "FAQ" --- # FAQ: MCP servers, registries and this directory | Agent MCP Directory > 30 questions on MCP versions, registries, hosts, OAuth, WebMCP and A2A, answered with sources, including how this directory verifies a server. Source: https://agentmcpdirectory.com/faq Site: Agent MCP Directory Last reviewed: 2026-11-05 # Questions and answers 30 questions about the current MCP specification, the registries, Cloudflare and Vercel hosting, OAuth, WebMCP, A2A and how this directory verifies a server. Every answer cites a source and the date it was read. The directory also runs a read-only MCP server of its own, covered in the questions below. ## The specification, transports and sign-in ### What is the current MCP specification version? The current revision is 2026-07-28, released on 28 Jul 2026. It made MCP stateless (no initialize handshake, no Mcp-Session-Id), added server/discover and deprecated Dynamic Client Registration and the HTTP+SSE transport. The previous revision was 2025-11-25. ([MCP 2026-07-28 changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 5 November 2026) ### Is the SSE transport still supported in MCP? HTTP+SSE has been deprecated since 2025-03-26 and the 2026-07-28 revision reclassifies it as Deprecated under a policy with a minimum twelve-month window. Several vendors already removed it: Cloudflare product servers return 410 Gone on /sse since 22 Oct 2026 and Neon retired its /sse endpoint. ([MCP deprecated features, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/deprecated), read 5 November 2026; [MCP 2026-07-28 changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 5 November 2026; [Cloudflare changelog: Cloudflare MCP servers no longer serve /sse (22 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 5 November 2026; [Neon MCP server docs](https://neon.com/docs/ai/neon-mcp-server), read 5 November 2026) ### Does an MCP server still need an initialize handshake? Not under 2026-07-28. Each request carries its protocol version and client capabilities in \_meta, and servers must implement server/discover. Clients talking to servers on earlier revisions detect the era and fall back to the old handshake. ([MCP 2026-07-28 changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 5 November 2026) ### Should my MCP server support Dynamic Client Registration? Support Client ID Metadata Documents first; the spec says clients and authorization servers SHOULD support them. DCR is MAY and deprecated, kept for authorization servers that lack CIMD. Cloudflare's Workers OAuth Provider v1 supports both, which is a reasonable default for a while. ([MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 5 November 2026; [Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 5 November 2026) ### What does an MCP server have to publish for OAuth? OAuth 2.0 Protected Resource Metadata (RFC 9728), usually at /.well-known/oauth-protected-resource, naming the authorization server. On a request without a token, return 401 with a WWW-Authenticate header carrying resource\_metadata and, ideally, the required scope. ([MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 5 November 2026) ## Registries and directories ### How many servers are in the official MCP Registry? A full pull of GET /v0/servers with version=latest on 4 Nov 2026 returned 56,677 entries: 55,806 active and 871 deprecated. 37,977 declared at least one remote endpoint. The registry is still a preview and does not check that endpoints work. ([Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), counted on 4 November 2026) ### How do I publish my server to the official MCP Registry? Use the mcp-publisher CLI from your server's project after proving the namespace: GitHub OAuth or OIDC for io.github names, DNS or HTTP verification for a domain. A pull request or a server.json added to the registry repository does not list a server. ([modelcontextprotocol/registry on GitHub](https://github.com/modelcontextprotocol/registry), read 5 November 2026) ### Is the GitHub MCP Registry the same as the official registry? No. GitHub lists 773 servers on github.com/mcp and serves them at api.mcp.github.com/v0/servers with GitHub metadata such as stars and licence. The official registry holds about 56,700 entries published by anyone with a verified namespace. ([GitHub MCP Registry API, GET /v0/servers](https://api.mcp.github.com/v0/servers), counted on 4 November 2026; [Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), observed on 4 November 2026; [modelcontextprotocol/registry on GitHub](https://github.com/modelcontextprotocol/registry), read 5 November 2026) ### What happened to Smithery? Arcade announced on 5 Aug 2026 that it acquired Smithery. The smithery.ai home page now says it is part of Arcade and that the MCP Proxy and managed identity features shut down on 31 Oct 2026. ([Arcade: Smithery is now part of Arcade.dev (5 Aug 2026)](https://www.arcade.dev/blog/smithery-joins-arcade), read 5 November 2026; [smithery.ai home page](https://smithery.ai/), read 5 November 2026) ### How many MCP servers does Glama list? Glama showed 115,804 servers on 4 Nov 2026, split into 45,531 remote, 43,657 local and 21,761 hybrid, and a separate list of 40,288 remote connectors. These are Glama's own counts. Its API needs a key and its data license requires attribution. ([Glama MCP servers directory](https://glama.ai/mcp/servers), counted on 4 November 2026; [Glama MCP connectors (remote servers)](https://glama.ai/mcp/connectors), counted on 4 November 2026) ### What does it take to get into the Claude Connectors Directory? A remote HTTPS server, OAuth 2.0 if tools act on a user account, a title and readOnlyHint or destructiveHint on every tool, documentation and privacy URLs, and a test account for reviewers. Submissions go through claude.ai/directory/manage on any paid Claude plan; local MCPB bundles are no longer accepted. ([Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 5 November 2026) ## Hosting, gateways and pricing ### Should I host my MCP server on Cloudflare or Vercel? Both serve Streamable HTTP. Cloudflare gives you an OAuth authorization server library (Workers OAuth Provider v1) and portals for central control. Vercel's mcp-handler verifies tokens but needs an external authorization server, and suits teams already on Next.js. ([Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 5 November 2026; [Vercel: deploy MCP servers to Vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 5 November 2026) ### Does Vercel run an MCP server for its own platform? Yes. Vercel MCP is at https://mcp.vercel.com with OAuth, on all plans. Since 2 Nov 2026 it accepts any client that uses a Client ID Metadata Document, without prior review. ([Vercel MCP docs](https://vercel.com/docs/agent-resources/vercel-mcp), read 5 November 2026; [Vercel changelog: Vercel MCP supports Client ID Metadata Documents (2 Nov 2026)](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 5 November 2026) ### How does Zapier charge for MCP? MCP is included in every Zapier plan and each successful tool call uses two tasks from the plan quota; failed calls do not count. Clients must support Streamable HTTP. ([Zapier MCP docs](https://docs.zapier.com/mcp/home), read 5 November 2026) ### How does Composio charge for MCP tool calls? Hobby is free with 100K tool calls a month (up to 20K on Composio-managed apps). Pro is 29 USD a month with 29 USD of credits and overage of 0.0003 USD per tool call; managed-app calls cost more. Prices read on 4 Nov 2026. ([Composio pricing](https://composio.dev/pricing), read 5 November 2026) ### What is an MCP server portal? A Cloudflare product, generally available since 24 Sep 2026, that puts up to 80 remote MCP servers behind one endpoint, signs users in through Cloudflare Access and lets admins hide, allowlist or alias individual tools. ([Cloudflare changelog: MCP server portals GA (24 Sep 2026)](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/), read 5 November 2026; [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 5 November 2026) ### Do AI gateways front MCP servers? Some do. Portkey's MCP Gateway and Kong's AI MCP Server handle MCP traffic. Cloudflare AI Gateway and Vercel AI Gateway front model APIs only; Cloudflare handles MCP through portals and Vercel through mcp-handler hosting. ([Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026; [Kong AI Gateway docs](https://developer.konghq.com/ai-gateway/), read 5 November 2026; [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 5 November 2026; [Vercel AI Gateway pricing](https://vercel.com/docs/ai-gateway/pricing), read 5 November 2026; [Vercel: deploy MCP servers to Vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 5 November 2026) ## WebMCP, A2A and other agent surfaces ### What is WebMCP and can agents use it today? WebMCP is a draft browser API, document.modelContext.registerTool(), for pages to expose tools. nekuda's FAQ (October 2026) says Chrome and Edge test it in an origin trial and Brave has it behind a flag; Firefox and Safari have none, and Gemini in Chrome and Claude for Chrome do not use WebMCP tools yet. ([webmcp.com (nekuda)](https://webmcp.com/), read 5 November 2026) ### What is the difference between MCP and A2A? MCP connects an agent to tools and data on a server. A2A connects agents to other agents through an Agent Card at /.well-known/agent-card.json and task messages over JSON-RPC, gRPC or HTTP+JSON. Under the Agentic AI Foundation, A2A and MCP are sibling projects since A2A joined on 27 Aug 2026. ([A2A joins the Agentic AI Foundation (27 Aug 2026)](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 5 November 2026; [A2A specification](https://a2a-protocol.org/latest/specification/), read 5 November 2026) ### Where does an A2A agent card live? At https://{server\_domain}/.well-known/agent-card.json, registered as a well-known URI in section 14.3 of the A2A 1.0.0 specification. ([A2A specification](https://a2a-protocol.org/latest/specification/), read 5 November 2026) ### Is agents.json still maintained? The wild-card-ai/agents-json repository shows version 0.1.0 under MIT with 75 commits on master. The page shows no last-activity date, so treat it as an early specification. ([wild-card-ai/agents-json](https://github.com/wild-card-ai/agents-json), read 5 November 2026) ### How does NLWeb relate to MCP? Every NLWeb instance acts as an MCP server and supports a core ask method that takes a natural-language question and returns Schema.org JSON. NLWeb is Microsoft's open project, MIT licensed. ([nlweb-ai/NLWeb](https://github.com/nlweb-ai/NLWeb), read 5 November 2026) ### Do I need an MCP server to count as agent ready? AgentReady.org, launched by Ora on 19 Oct 2026, requires an MCP server or a CLI, at least one, for the act layer; a public API with OpenAPI and WebMCP are SHOULDs. Ora is the publisher of that standard. ([Ora: Introducing AgentReady.org (19 Oct 2026)](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=faq), read 5 November 2026) ## Specific servers and tools ### What tools does Stripe's MCP server expose? Stripe's server at https://mcp.stripe.com exposes stripe\_api\_search, stripe\_api\_details, stripe\_api\_read and stripe\_api\_write, plus account, Atlas, analytics, Treasury and docs tools. Some write actions need human confirmation in the Dashboard. ([Stripe MCP docs](https://docs.stripe.com/mcp), observed on 4 November 2026) ### Does Shopify still serve Storefront MCP at /api/mcp? The catalog and cart tools on https://{shop}/api/mcp were removed; the replacement endpoint is https://{shop}/api/ucp/mcp, and every request should carry an agent profile. ([Shopify Storefront MCP docs](https://shopify.dev/docs/apps/build/storefront-mcp), read 5 November 2026) ### How do I connect to the GitHub MCP server? Use the remote at https://api.githubcopilot.com/mcp/ with OAuth or a PAT as a bearer token, or run ghcr.io/github/github-mcp-server locally. --read-only disables write tools even if you request them by name. ([github/github-mcp-server](https://github.com/github/github-mcp-server), read 5 November 2026) ### How good are the tool descriptions in public MCP servers? Arcade's ToolBench rescan of more than 90,000 open-source servers (30 Sep 2026) found 260 servers (0.28 percent) earned an A, descriptions averaged 57 out of 100, and seven in ten servers give no useful guidance when a call fails. This is Arcade's own research. ([Arcade: ToolBench rescan, 90,000 MCP servers (30 Sep 2026)](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 5 November 2026) ### Does Ora have an MCP server? Ora publishes /.well-known/mcp.json naming https://ora.ai/api/mcp over Streamable HTTP with 18 tools, including scan\_domain, get\_score and run\_journey. ([ora.ai/.well-known/mcp.json](https://ora.ai/.well-known/mcp.json?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=faq), observed on 4 November 2026) ## This directory ### Does this directory run its own MCP server? Yes, a read-only one. The server at /mcp offers five read-only tools over the directory rows and the census, and the same data is available through a REST API and an NLWeb ask endpoint. It never calls another company's server. It is not a row in the directory, which lists companies and not this publication. ([agentmcpdirectory.com/developers](https://agentmcpdirectory.com/developers/), read 5 November 2026) ### How does this directory verify an MCP server? Each claimed endpoint is checked by a connector that only calls read-only methods (server/discover or initialize, tools/list, resources/list, prompts/list) and logs the time and tool list. Entries that cannot be verified say why and do not count as having an MCP server. In the 4 November 2026 run the connector sent initialize; server/discover joins its allowlist from the next run. ([agentmcpdirectory.com/method](https://agentmcpdirectory.com/method/), read 5 November 2026) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/faq/index.md) ## Sources - [MCP 2026-07-28 changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 5 November 2026 - [MCP deprecated features, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/deprecated), read 5 November 2026 - [Cloudflare changelog: Cloudflare MCP servers no longer serve /sse (22 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 5 November 2026 - [Neon MCP server docs](https://neon.com/docs/ai/neon-mcp-server), read 5 November 2026 - [MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 5 November 2026 - [Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026)](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 5 November 2026 - [Official MCP Registry API, GET /v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 (Count taken from the registry API at registry.modelcontextprotocol.io on 4 November 2026.) - [modelcontextprotocol/registry on GitHub](https://github.com/modelcontextprotocol/registry), read 5 November 2026 - [GitHub MCP Registry API, GET /v0/servers](https://api.mcp.github.com/v0/servers), read 4 November 2026 (Count taken from the registry API at api.mcp.github.com on 4 November 2026.) - [Arcade: Smithery is now part of Arcade.dev (5 Aug 2026)](https://www.arcade.dev/blog/smithery-joins-arcade), read 5 November 2026 - [smithery.ai home page](https://smithery.ai/), read 5 November 2026 - [Glama MCP servers directory](https://glama.ai/mcp/servers), read 4 November 2026 (Figure read on the glama.ai page on 4 November 2026.) - [Glama MCP connectors (remote servers)](https://glama.ai/mcp/connectors), read 4 November 2026 (Figure read on the glama.ai page on 4 November 2026.) - [Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 5 November 2026 - [Vercel: deploy MCP servers to Vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 5 November 2026 - [Vercel MCP docs](https://vercel.com/docs/agent-resources/vercel-mcp), read 5 November 2026 - [Vercel changelog: Vercel MCP supports Client ID Metadata Documents (2 Nov 2026)](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 5 November 2026 - [Zapier MCP docs](https://docs.zapier.com/mcp/home), read 5 November 2026 - [Composio pricing](https://composio.dev/pricing), read 5 November 2026 - [webmcp.com (nekuda)](https://webmcp.com/), read 5 November 2026 - [A2A joins the Agentic AI Foundation (27 Aug 2026)](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 5 November 2026 - [A2A specification](https://a2a-protocol.org/latest/specification/), read 5 November 2026 - [wild-card-ai/agents-json](https://github.com/wild-card-ai/agents-json), read 5 November 2026 - [nlweb-ai/NLWeb](https://github.com/nlweb-ai/NLWeb), read 5 November 2026 - [Ora: Introducing AgentReady.org (19 Oct 2026)](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=faq), read 5 November 2026 - [Stripe MCP docs](https://docs.stripe.com/mcp), read 4 November 2026 (Fact noted from the docs.stripe.com page on 4 November 2026.) - [Shopify Storefront MCP docs](https://shopify.dev/docs/apps/build/storefront-mcp), read 5 November 2026 - [github/github-mcp-server](https://github.com/github/github-mcp-server), read 5 November 2026 - [Cloudflare changelog: MCP server portals GA (24 Sep 2026)](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/), read 5 November 2026 - [Cloudflare MCP server portals docs](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 5 November 2026 - [Portkey MCP Gateway docs](https://portkey.ai/docs/product/mcp-gateway), read 5 November 2026 - [Kong AI Gateway docs](https://developer.konghq.com/ai-gateway/), read 5 November 2026 - [Vercel AI Gateway pricing](https://vercel.com/docs/ai-gateway/pricing), read 5 November 2026 - [Arcade: ToolBench rescan, 90,000 MCP servers (30 Sep 2026)](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 5 November 2026 - [ora.ai/.well-known/mcp.json](https://ora.ai/.well-known/mcp.json?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=faq), read 4 November 2026 (Fact noted from the ora.ai page on 4 November 2026.) - [agentmcpdirectory.com/developers](https://agentmcpdirectory.com/developers/), read 5 November 2026 - [agentmcpdirectory.com/method](https://agentmcpdirectory.com/method/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Glossary: MCP and act-layer terms | Agent MCP Directory" description: "41 terms for building and finding MCP servers, CLIs and agent surfaces, each defined briefly with a sourced example. From A2A to WebMCP." canonical: https://agentmcpdirectory.com/glossary site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Glossary: MCP and act-layer terms | Agent MCP Directory > 41 terms for building and finding MCP servers, CLIs and agent surfaces, each defined briefly with a sourced example. From A2A to WebMCP. Source: https://agentmcpdirectory.com/glossary Site: Agent MCP Directory Last reviewed: 2026-11-04 # Glossary 41 terms used across this directory, from the act layer and MCP host to WebMCP and server cards. Each entry gives a one-line definition and an example with a source, so a reader and an agent can check the term against the specification it came from. | Act layer | The part of agent readiness about completing tasks: MCP servers, CLIs, APIs with OpenAPI, WebMCP and agent payments. | | --- | --- | | Agent Card | The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json. | | Agent Skills | A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. | | Agent2Agent (A2A) | A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. | | Agentic AI Foundation (AAIF) | The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. | | agents.json | An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. | | AI gateway | A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. | | Client ID Metadata Document (CIMD) | A JSON file on the client's domain whose HTTPS URL is used as the OAuth client_id, the recommended MCP registration method. | | Code Mode | A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one, set by portal policy. | | Confused deputy | An attack where a proxy with its own credentials is tricked into acting for someone else; MCP security guidance addresses it for OAuth proxies. | | document.modelContext | The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. | | Dynamic Client Registration (DCR) | RFC 7591 registration where a client POSTs to /register for credentials; deprecated in MCP 2026-07-28 and kept for compatibility. | | Elicitation | A way for a server to ask the user, through the client, for more information, now handled through multi round-trip requests. | | HTTP+SSE transport | The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated in 2026-07-28. | | MCP Apps | An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. | | MCP client | The connector inside a host application that holds one connection to one MCP server. | | MCP gateway | A proxy in front of MCP servers that authenticates callers, injects upstream credentials, filters tools and logs calls. | | MCP host | The LLM application that starts client connections and asks the user for consent. | | MCP registry | A catalog of MCP server metadata that clients and directories read; the official one is registry.modelcontextprotocol.io. | | MCP server | A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. | | MCP server portal | Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. | | mcp-publisher | The CLI that publishes a server.json to the official registry after namespace verification. | | Model Context Protocol (MCP) | A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. | | Multi round-trip request (MRTR) | The 2026-07-28 pattern where a server returns input_required and the client retries the request with the answers. | | Namespace verification | Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP for domains. | | NLWeb | Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses; each instance is an MCP server. | | Prompt | A templated message or workflow an MCP server offers to users. | | Protected Resource Metadata | The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. | | Remote MCP server | An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. | | Resource | Context or data an MCP server offers for the user or model to read, addressed by URI. | | Resource indicator | The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. | | server.json | The registry metadata file for one server: name, version, remotes, packages, website and repository. | | server/discover | The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. | | Stateless MCP | The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id; each request carries version and capabilities in _meta. | | stdio transport | The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over standard streams. | | Step-up authorization | Requesting a wider scope set after a 403 insufficient_scope challenge, keeping previously granted scopes. | | Streamable HTTP | The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE stream. | | Tasks extension | An official MCP extension for long-running operations with polling and durable handles, moved out of core in 2026-07-28. | | Tool | A function an MCP server offers for the model to call, with a name, description and input schema. | | Tool annotations | Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. | | WebMCP | A draft browser API for pages to register JavaScript tools that an in-browser agent can call. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/index.md) ## Sources - [Act layer](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 4 November 2026 - [Agent Card](https://a2a-protocol.org/latest/specification/), read 4 November 2026 - [Agent Skills](https://docs.stripe.com/mcp), read 4 November 2026 - [Agent2Agent (A2A)](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 - [agents.json](https://github.com/wild-card-ai/agents-json), read 4 November 2026 - [AI gateway](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026 - [Client ID Metadata Document (CIMD)](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Code Mode](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Confused deputy](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 - [document.modelContext](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 4 November 2026 - [Dynamic Client Registration (DCR)](https://supabase.com/docs/guides/getting-started/mcp), read 4 November 2026 - [Elicitation](https://modelcontextprotocol.io/specification/2025-11-25/changelog), read 4 November 2026 - [HTTP+SSE transport](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 - [MCP Apps](https://vercel.com/changelog/monitor-vercel-deployments-in-chatgpt), read 4 November 2026 - [MCP gateway](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 - [MCP host](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 - [MCP registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [Multi round-trip request (MRTR)](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [NLWeb](https://github.com/nlweb-ai/NLWeb), read 4 November 2026 - [Protected Resource Metadata](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [Remote MCP server](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Resource](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Resource indicator](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 - [stdio transport](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Step-up authorization](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Act layer: definition and example | Agent MCP Directory" description: "Act layer: The part of agent readiness about completing tasks: MCP servers, CLIs, APIs with OpenAPI, WebMCP and agent payments." canonical: https://agentmcpdirectory.com/glossary/act-layer site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Act layer: definition and example | Agent MCP Directory > Act layer: The part of agent readiness about completing tasks: MCP servers, CLIs, APIs with OpenAPI, WebMCP and agent payments. Source: https://agentmcpdirectory.com/glossary/act-layer Site: Agent MCP Directory Last reviewed: 2026-11-04 # Act layer Act layer: The part of agent readiness about completing tasks: MCP servers, CLIs, APIs with OpenAPI, WebMCP and agent payments. Example: AgentReady.org requires an MCP server or a CLI, at least one. Next in the glossary is Agent Card: The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json. ## Definition The part of agent readiness about completing tasks: MCP servers, CLIs, APIs with OpenAPI, WebMCP and agent payments. ## Example, with source AgentReady.org requires an MCP server or a CLI, at least one. ([ora.ai](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=glossary), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [WebMCP](https://agentmcpdirectory.com/standards/webmcp/) - [OpenAPI as an agent surface](https://agentmcpdirectory.com/standards/openapi-as-agent-surface/) - [CLIs as an agent surface](https://agentmcpdirectory.com/standards/cli-as-agent-surface/) ## Neighbouring terms - [Agent Card](https://agentmcpdirectory.com/glossary/agent-card/): The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json. - [Agent Skills](https://agentmcpdirectory.com/glossary/agent-skills/): A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/act-layer/index.md) ## Sources - [Source for the Act layer example](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=glossary), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Agent Card: definition and example | Agent MCP Directory" description: "Agent Card: The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json." canonical: https://agentmcpdirectory.com/glossary/agent-card site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Agent Card: definition and example | Agent MCP Directory > Agent Card: The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json. Source: https://agentmcpdirectory.com/glossary/agent-card Site: Agent MCP Directory Last reviewed: 2026-11-04 # Agent Card Agent Card: The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json. Example: A2A registers the well-known URI in section 14.3 of its spec. Next in the glossary is Agent Skills: A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. ## Definition The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json. ## Example, with source A2A registers the well-known URI in section 14.3 of its spec. ([a2a-protocol.org](https://a2a-protocol.org/latest/specification/), read 4 November 2026) ## Where it appears on this site - [A2A](https://agentmcpdirectory.com/standards/a2a/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) ## Neighbouring terms - [Act layer](https://agentmcpdirectory.com/glossary/act-layer/): The part of agent readiness about completing tasks: MCP servers, CLIs, APIs with OpenAPI, WebMCP and agent payments. - [Agent Skills](https://agentmcpdirectory.com/glossary/agent-skills/): A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. - [Agent2Agent (A2A)](https://agentmcpdirectory.com/glossary/agent2agent/): A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/agent-card/index.md) ## Sources - [Source for the Agent Card example](https://a2a-protocol.org/latest/specification/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Agent Skills: definition and example | Agent MCP Directory" description: "Agent Skills: A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/agent-skills site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Agent Skills: definition and example | Agent MCP Directory > Agent Skills: A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/agent-skills Site: Agent MCP Directory Last reviewed: 2026-11-04 # Agent Skills Agent Skills: A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. Example: Stripe's stripe agent setup installs its skills with the MCP server. Next in the glossary is Agent2Agent (A2A): A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. ## Definition A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. ## Example, with source Stripe's stripe agent setup installs its skills with the MCP server. ([docs.stripe.com](https://docs.stripe.com/mcp), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) ## Neighbouring terms - [Agent Card](https://agentmcpdirectory.com/glossary/agent-card/): The A2A JSON document describing an agent's skills, endpoints and auth, served at /.well-known/agent-card.json. - [Agent2Agent (A2A)](https://agentmcpdirectory.com/glossary/agent2agent/): A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. - [Agentic AI Foundation (AAIF)](https://agentmcpdirectory.com/glossary/agentic-ai-foundation/): The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/agent-skills/index.md) ## Sources - [Source for the Agent Skills example](https://docs.stripe.com/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Agent2Agent (A2A): definition and example | Agent MCP Directory" description: "Agent2Agent (A2A): A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/agent2agent site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Agent2Agent (A2A): definition and example | Agent MCP Directory > Agent2Agent (A2A): A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/agent2agent Site: Agent MCP Directory Last reviewed: 2026-11-04 # Agent2Agent (A2A) Agent2Agent (A2A): A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. Example: A2A joined the Agentic AI Foundation on 27 Aug 2026. Next in the glossary is Agentic AI Foundation (AAIF): The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. ## Definition A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. ## Example, with source A2A joined the Agentic AI Foundation on 27 Aug 2026. ([a2a-protocol.org](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026) ## Where it appears on this site - [A2A](https://agentmcpdirectory.com/standards/a2a/) ## Neighbouring terms - [Agent Skills](https://agentmcpdirectory.com/glossary/agent-skills/): A folder with a SKILL.md file of instructions and optional scripts that agents load on demand. - [Agentic AI Foundation (AAIF)](https://agentmcpdirectory.com/glossary/agentic-ai-foundation/): The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. - [agents.json](https://agentmcpdirectory.com/glossary/agents-json/): An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/agent2agent/index.md) ## Sources - [Source for the Agent2Agent (A2A) example](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Agentic AI Foundation (AAIF): definition | Agent MCP Directory" description: "Agentic AI Foundation (AAIF): The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/agentic-ai-foundation site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Agentic AI Foundation (AAIF): definition | Agent MCP Directory > Agentic AI Foundation (AAIF): The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/agentic-ai-foundation Site: Agent MCP Directory Last reviewed: 2026-11-04 # Agentic AI Foundation (AAIF) Agentic AI Foundation (AAIF): The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. Example: A2A joined as a Growth Stage project on 27 Aug 2026. Next in the glossary is agents.json: An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. ## Definition The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. ## Example, with source A2A joined as a Growth Stage project on 27 Aug 2026. ([a2a-protocol.org](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [A2A](https://agentmcpdirectory.com/standards/a2a/) ## Neighbouring terms - [Agent2Agent (A2A)](https://agentmcpdirectory.com/glossary/agent2agent/): A protocol for agents to discover each other and exchange tasks, now at version 1.0.0. - [agents.json](https://agentmcpdirectory.com/glossary/agents-json/): An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. - [AI gateway](https://agentmcpdirectory.com/glossary/ai-gateway/): A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/agentic-ai-foundation/index.md) ## Sources - [Source for the Agentic AI Foundation (AAIF) example](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "agents.json: definition and example | Agent MCP Directory" description: "agents.json: An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/agents-json site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # agents.json: definition and example | Agent MCP Directory > agents.json: An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/agents-json Site: Agent MCP Directory Last reviewed: 2026-11-04 # agents.json agents.json: An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. Example: The current version is 0.1.0 under MIT. Next in the glossary is AI gateway: A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. ## Definition An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. ## Example, with source The current version is 0.1.0 under MIT. ([github.com](https://github.com/wild-card-ai/agents-json), read 4 November 2026) ## Where it appears on this site - [agents.json](https://agentmcpdirectory.com/standards/agents-json/) - [OpenAPI as an agent surface](https://agentmcpdirectory.com/standards/openapi-as-agent-surface/) ## Neighbouring terms - [Agentic AI Foundation (AAIF)](https://agentmcpdirectory.com/glossary/agentic-ai-foundation/): The Linux Foundation-directed foundation that hosts MCP, A2A, goose and AGENTS.md. - [AI gateway](https://agentmcpdirectory.com/glossary/ai-gateway/): A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. - [Client ID Metadata Document (CIMD)](https://agentmcpdirectory.com/glossary/client-id-metadata-document/): A JSON file on the client's domain whose HTTPS URL is used as the OAuth client\_id, the recommended MCP registration method. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/agents-json/index.md) ## Sources - [Source for the agents.json example](https://github.com/wild-card-ai/agents-json), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "AI gateway: definition and example | Agent MCP Directory" description: "AI gateway: A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/ai-gateway site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # AI gateway: definition and example | Agent MCP Directory > AI gateway: A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/ai-gateway Site: Agent MCP Directory Last reviewed: 2026-11-04 # AI gateway AI gateway: A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. Example: Cloudflare AI Gateway gives caching and rate limiting free on all plans. Also in the glossary is agents.json: An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. ## Definition A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. ## Example, with source Cloudflare AI Gateway gives caching and rate limiting free on all plans. ([developers.cloudflare.com](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026) ## Where it appears on this site - [Hosts and gateways compared](https://agentmcpdirectory.com/hosts/) ## Neighbouring terms - [agents.json](https://agentmcpdirectory.com/glossary/agents-json/): An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. - [Client ID Metadata Document (CIMD)](https://agentmcpdirectory.com/glossary/client-id-metadata-document/): A JSON file on the client's domain whose HTTPS URL is used as the OAuth client\_id, the recommended MCP registration method. - [Code Mode](https://agentmcpdirectory.com/glossary/code-mode/): A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one, set by portal policy. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/ai-gateway/index.md) ## Sources - [Source for the AI gateway example](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Client ID Metadata Document (CIMD): definition | Agent MCP Directory" description: "Client ID Metadata Document (CIMD): A JSON file on the client's domain whose HTTPS URL is used as the OAuth client_id. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/client-id-metadata-document site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Client ID Metadata Document (CIMD): definition | Agent MCP Directory > Client ID Metadata Document (CIMD): A JSON file on the client's domain whose HTTPS URL is used as the OAuth client_id. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/client-id-metadata-document Site: Agent MCP Directory Last reviewed: 2026-11-04 # Client ID Metadata Document (CIMD) Client ID Metadata Document (CIMD): A JSON file on the client's domain whose HTTPS URL is used as the OAuth client\_id, the recommended MCP registration method. Example: Vercel MCP accepts CIMD clients without review since 2 Nov 2026. Also in the glossary is agents.json: An OpenAPI-based file at /.well-known/agents.json describing flows of API calls for agents. ## Definition A JSON file on the client's domain whose HTTPS URL is used as the OAuth client\_id, the recommended MCP registration method. ## Example, with source Vercel MCP accepts CIMD clients without review since 2 Nov 2026. ([vercel.com](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [OAuth for MCP](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) ## Neighbouring terms - [AI gateway](https://agentmcpdirectory.com/glossary/ai-gateway/): A proxy in front of model APIs that adds caching, rate limits, logs and billing across providers. - [Code Mode](https://agentmcpdirectory.com/glossary/code-mode/): A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one, set by portal policy. - [Confused deputy](https://agentmcpdirectory.com/glossary/confused-deputy/): An attack where a proxy with its own credentials is tricked into acting for someone else; MCP security guidance addresses it for OAuth proxies. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/client-id-metadata-document/index.md) ## Sources - [Source for the Client ID Metadata Document (CIMD) example](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Code Mode: definition and example | Agent MCP Directory" description: "Code Mode: A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one." canonical: https://agentmcpdirectory.com/glossary/code-mode site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Code Mode: definition and example | Agent MCP Directory > Code Mode: A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one. Source: https://agentmcpdirectory.com/glossary/code-mode Site: Agent MCP Directory Last reviewed: 2026-11-04 # Code Mode Code Mode: A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one, set by portal policy. Example: Portal Code Mode policy can be off, opt\_in, default\_on or enforced. Also in the glossary is document.modelContext: The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. ## Definition A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one, set by portal policy. ## Example, with source Portal Code Mode policy can be off, opt\_in, default\_on or enforced. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) ## Where it appears on this site - [Hosts and gateways compared](https://agentmcpdirectory.com/hosts/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [Client ID Metadata Document (CIMD)](https://agentmcpdirectory.com/glossary/client-id-metadata-document/): A JSON file on the client's domain whose HTTPS URL is used as the OAuth client\_id, the recommended MCP registration method. - [Confused deputy](https://agentmcpdirectory.com/glossary/confused-deputy/): An attack where a proxy with its own credentials is tricked into acting for someone else; MCP security guidance addresses it for OAuth proxies. - [document.modelContext](https://agentmcpdirectory.com/glossary/document-modelcontext/): The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/code-mode/index.md) ## Sources - [Source for the Code Mode example](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Confused deputy: definition and example | Agent MCP Directory" description: "Confused deputy: An attack where a proxy with its own credentials is tricked into acting for someone else. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/confused-deputy site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Confused deputy: definition and example | Agent MCP Directory > Confused deputy: An attack where a proxy with its own credentials is tricked into acting for someone else. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/confused-deputy Site: Agent MCP Directory Last reviewed: 2026-11-04 # Confused deputy Confused deputy: An attack where a proxy with its own credentials is tricked into acting for someone else; MCP security guidance addresses it for OAuth proxies. Example: Vercel MCP requires explicit consent for each client connection to prevent it. Next in the glossary is document.modelContext: The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. ## Definition An attack where a proxy with its own credentials is tricked into acting for someone else; MCP security guidance addresses it for OAuth proxies. ## Example, with source Vercel MCP requires explicit consent for each client connection to prevent it. ([vercel.com](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [OAuth for MCP](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) - [Building a remote MCP server](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) ## Neighbouring terms - [Code Mode](https://agentmcpdirectory.com/glossary/code-mode/): A Cloudflare approach where the agent writes code against a typed API instead of calling many tools one by one, set by portal policy. - [document.modelContext](https://agentmcpdirectory.com/glossary/document-modelcontext/): The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. - [Dynamic Client Registration (DCR)](https://agentmcpdirectory.com/glossary/dynamic-client-registration/): RFC 7591 registration where a client POSTs to /register for credentials; deprecated in MCP 2026-07-28 and kept for compatibility. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/confused-deputy/index.md) ## Sources - [Source for the Confused deputy example](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "document.modelContext: definition and example | Agent MCP Directory" description: "document.modelContext: The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/document-modelcontext site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # document.modelContext: definition and example | Agent MCP Directory > document.modelContext: The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/document-modelcontext Site: Agent MCP Directory Last reviewed: 2026-11-04 # document.modelContext document.modelContext: The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. Example: Cloudflare Browser Run moved to document.modelContext on 28 Sep 2026. Next in the glossary is Dynamic Client Registration (DCR): RFC 7591 registration where a client POSTs to /register for credentials; deprecated in MCP 2026-07-28 and kept for compatibility. ## Definition The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. ## Example, with source Cloudflare Browser Run moved to document.modelContext on 28 Sep 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 4 November 2026) ## Where it appears on this site - [WebMCP](https://agentmcpdirectory.com/standards/webmcp/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [Confused deputy](https://agentmcpdirectory.com/glossary/confused-deputy/): An attack where a proxy with its own credentials is tricked into acting for someone else; MCP security guidance addresses it for OAuth proxies. - [Dynamic Client Registration (DCR)](https://agentmcpdirectory.com/glossary/dynamic-client-registration/): RFC 7591 registration where a client POSTs to /register for credentials; deprecated in MCP 2026-07-28 and kept for compatibility. - [Elicitation](https://agentmcpdirectory.com/glossary/elicitation/): A way for a server to ask the user, through the client, for more information, now handled through multi round-trip requests. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/document-modelcontext/index.md) ## Sources - [Source for the document.modelContext example](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Dynamic Client Registration (DCR): definition | Agent MCP Directory" description: "Dynamic Client Registration (DCR): RFC 7591 registration where a client POSTs to /register for credentials. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/dynamic-client-registration site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Dynamic Client Registration (DCR): definition | Agent MCP Directory > Dynamic Client Registration (DCR): RFC 7591 registration where a client POSTs to /register for credentials. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/dynamic-client-registration Site: Agent MCP Directory Last reviewed: 2026-11-04 # Dynamic Client Registration (DCR) Dynamic Client Registration (DCR): RFC 7591 registration where a client POSTs to /register for credentials; deprecated in MCP 2026-07-28 and kept for compatibility. Example: Supabase's hosted server uses DCR so users sign in through the browser. Also in the glossary is document.modelContext: The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. ## Definition RFC 7591 registration where a client POSTs to /register for credentials; deprecated in MCP 2026-07-28 and kept for compatibility. ## Example, with source Supabase's hosted server uses DCR so users sign in through the browser. ([supabase.com](https://supabase.com/docs/guides/getting-started/mcp), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [OAuth for MCP](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) ## Neighbouring terms - [document.modelContext](https://agentmcpdirectory.com/glossary/document-modelcontext/): The WebMCP entry point on the document object that holds registerTool, getTools and executeTool. - [Elicitation](https://agentmcpdirectory.com/glossary/elicitation/): A way for a server to ask the user, through the client, for more information, now handled through multi round-trip requests. - [HTTP+SSE transport](https://agentmcpdirectory.com/glossary/http-sse-transport/): The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated in 2026-07-28. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/dynamic-client-registration/index.md) ## Sources - [Source for the Dynamic Client Registration (DCR) example](https://supabase.com/docs/guides/getting-started/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Elicitation: definition and example | Agent MCP Directory" description: "Elicitation: A way for a server to ask the user, through the client, for more information. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/elicitation site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Elicitation: definition and example | Agent MCP Directory > Elicitation: A way for a server to ask the user, through the client, for more information. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/elicitation Site: Agent MCP Directory Last reviewed: 2026-11-04 # Elicitation Elicitation: A way for a server to ask the user, through the client, for more information, now handled through multi round-trip requests. Example: 2025-11-25 added URL mode elicitation. Next in the glossary is HTTP+SSE transport: The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated in 2026-07-28. ## Definition A way for a server to ask the user, through the client, for more information, now handled through multi round-trip requests. ## Example, with source 2025-11-25 added URL mode elicitation. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2025-11-25/changelog), read 4 November 2026) ## Neighbouring terms - [Dynamic Client Registration (DCR)](https://agentmcpdirectory.com/glossary/dynamic-client-registration/): RFC 7591 registration where a client POSTs to /register for credentials; deprecated in MCP 2026-07-28 and kept for compatibility. - [HTTP+SSE transport](https://agentmcpdirectory.com/glossary/http-sse-transport/): The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated in 2026-07-28. - [MCP Apps](https://agentmcpdirectory.com/glossary/mcp-apps/): An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/elicitation/index.md) ## Sources - [Source for the Elicitation example](https://modelcontextprotocol.io/specification/2025-11-25/changelog), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "HTTP+SSE transport: definition and example | Agent MCP Directory" description: "HTTP+SSE transport: The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated." canonical: https://agentmcpdirectory.com/glossary/http-sse-transport site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # HTTP+SSE transport: definition and example | Agent MCP Directory > HTTP+SSE transport: The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated. Source: https://agentmcpdirectory.com/glossary/http-sse-transport Site: Agent MCP Directory Last reviewed: 2026-11-04 # HTTP+SSE transport HTTP+SSE transport: The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated in 2026-07-28. Example: Cloudflare MCP servers return 410 Gone on /sse since 22 Oct 2026. Next in the glossary is MCP Apps: An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. ## Definition The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated in 2026-07-28. ## Example, with source Cloudflare MCP servers return 410 Gone on /sse since 22 Oct 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Building a remote MCP server](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) ## Neighbouring terms - [Elicitation](https://agentmcpdirectory.com/glossary/elicitation/): A way for a server to ask the user, through the client, for more information, now handled through multi round-trip requests. - [MCP Apps](https://agentmcpdirectory.com/glossary/mcp-apps/): An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. - [MCP client](https://agentmcpdirectory.com/glossary/mcp-client/): The connector inside a host application that holds one connection to one MCP server. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/http-sse-transport/index.md) ## Sources - [Source for the HTTP+SSE transport example](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP Apps: definition and example | Agent MCP Directory" description: "MCP Apps: An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-apps site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # MCP Apps: definition and example | Agent MCP Directory > MCP Apps: An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-apps Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP Apps MCP Apps: An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. Example: Vercel MCP renders deployments as an MCP Apps card in ChatGPT. Next in the glossary is MCP client: The connector inside a host application that holds one connection to one MCP server. ## Definition An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. ## Example, with source Vercel MCP renders deployments as an MCP Apps card in ChatGPT. ([vercel.com](https://vercel.com/changelog/monitor-vercel-deployments-in-chatgpt), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [HTTP+SSE transport](https://agentmcpdirectory.com/glossary/http-sse-transport/): The older MCP HTTP transport with a separate SSE endpoint, deprecated since 2025-03-26 and reclassified Deprecated in 2026-07-28. - [MCP client](https://agentmcpdirectory.com/glossary/mcp-client/): The connector inside a host application that holds one connection to one MCP server. - [MCP gateway](https://agentmcpdirectory.com/glossary/mcp-gateway/): A proxy in front of MCP servers that authenticates callers, injects upstream credentials, filters tools and logs calls. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-apps/index.md) ## Sources - [Source for the MCP Apps example](https://vercel.com/changelog/monitor-vercel-deployments-in-chatgpt), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP client: definition and example | Agent MCP Directory" description: "MCP client: The connector inside a host application that holds one connection to one MCP server. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-client site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # MCP client: definition and example | Agent MCP Directory > MCP client: The connector inside a host application that holds one connection to one MCP server. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-client Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP client MCP client: The connector inside a host application that holds one connection to one MCP server. Example: Vercel lists Claude Code, Cursor and Codex CLI among clients that connect to Vercel MCP. Next in the glossary is MCP gateway: A proxy in front of MCP servers that authenticates callers, injects upstream credentials, filters tools and logs calls. ## Definition The connector inside a host application that holds one connection to one MCP server. ## Example, with source Vercel lists Claude Code, Cursor and Codex CLI among clients that connect to Vercel MCP. ([vercel.com](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [CLIs as an agent surface](https://agentmcpdirectory.com/standards/cli-as-agent-surface/) ## Neighbouring terms - [MCP Apps](https://agentmcpdirectory.com/glossary/mcp-apps/): An MCP extension in which a tool points to a ui:// resource the host renders as a sandboxed View. - [MCP gateway](https://agentmcpdirectory.com/glossary/mcp-gateway/): A proxy in front of MCP servers that authenticates callers, injects upstream credentials, filters tools and logs calls. - [MCP host](https://agentmcpdirectory.com/glossary/mcp-host/): The LLM application that starts client connections and asks the user for consent. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-client/index.md) ## Sources - [Source for the MCP client example](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP gateway: definition and example | Agent MCP Directory" description: "MCP gateway: A proxy in front of MCP servers that authenticates callers, injects upstream credentials. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-gateway site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # MCP gateway: definition and example | Agent MCP Directory > MCP gateway: A proxy in front of MCP servers that authenticates callers, injects upstream credentials. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-gateway Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP gateway MCP gateway: A proxy in front of MCP servers that authenticates callers, injects upstream credentials, filters tools and logs calls. Example: Portkey's MCP Gateway logs every tool call with user, parameters and response. Next in the glossary is MCP host: The LLM application that starts client connections and asks the user for consent. ## Definition A proxy in front of MCP servers that authenticates callers, injects upstream credentials, filters tools and logs calls. ## Example, with source Portkey's MCP Gateway logs every tool call with user, parameters and response. ([portkey.ai](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Hosts and gateways compared](https://agentmcpdirectory.com/hosts/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [MCP client](https://agentmcpdirectory.com/glossary/mcp-client/): The connector inside a host application that holds one connection to one MCP server. - [MCP host](https://agentmcpdirectory.com/glossary/mcp-host/): The LLM application that starts client connections and asks the user for consent. - [MCP registry](https://agentmcpdirectory.com/glossary/mcp-registry/): A catalog of MCP server metadata that clients and directories read; the official one is registry.modelcontextprotocol.io. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-gateway/index.md) ## Sources - [Source for the MCP gateway example](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP host: definition and example | Agent MCP Directory" description: "MCP host: The LLM application that starts client connections and asks the user for consent. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-host site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # MCP host: definition and example | Agent MCP Directory > MCP host: The LLM application that starts client connections and asks the user for consent. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-host Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP host MCP host: The LLM application that starts client connections and asks the user for consent. Example: The spec names hosts, clients and servers as the three roles. Next in the glossary is MCP registry: A catalog of MCP server metadata that clients and directories read; the official one is registry.modelcontextprotocol.io. ## Definition The LLM application that starts client connections and asks the user for consent. ## Example, with source The spec names hosts, clients and servers as the three roles. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/latest), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) ## Neighbouring terms - [MCP gateway](https://agentmcpdirectory.com/glossary/mcp-gateway/): A proxy in front of MCP servers that authenticates callers, injects upstream credentials, filters tools and logs calls. - [MCP registry](https://agentmcpdirectory.com/glossary/mcp-registry/): A catalog of MCP server metadata that clients and directories read; the official one is registry.modelcontextprotocol.io. - [MCP server](https://agentmcpdirectory.com/glossary/mcp-server/): A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-host/index.md) ## Sources - [Source for the MCP host example](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Prompt: definition and example | Agent MCP Directory" description: "Prompt: A templated message or workflow an MCP server offers to users. Defined with a sourced example. Read 4 November 2026." canonical: https://agentmcpdirectory.com/glossary/mcp-prompt site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Prompt: definition and example | Agent MCP Directory > Prompt: A templated message or workflow an MCP server offers to users. Defined with a sourced example. Read 4 November 2026. Source: https://agentmcpdirectory.com/glossary/mcp-prompt Site: Agent MCP Directory Last reviewed: 2026-11-04 # Prompt Prompt: A templated message or workflow an MCP server offers to users. Example: Cloudflare portals can hide or alias individual prompts. Next in the glossary is Protected Resource Metadata: The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. ## Definition A templated message or workflow an MCP server offers to users. ## Example, with source Cloudflare portals can hide or alias individual prompts. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Hosts and gateways compared](https://agentmcpdirectory.com/hosts/) ## Neighbouring terms - [NLWeb](https://agentmcpdirectory.com/glossary/nlweb/): Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses; each instance is an MCP server. - [Protected Resource Metadata](https://agentmcpdirectory.com/glossary/protected-resource-metadata/): The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. - [Remote MCP server](https://agentmcpdirectory.com/glossary/remote-mcp-server/): An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-prompt/index.md) ## Sources - [Source for the Prompt example](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "mcp-publisher: definition and example | Agent MCP Directory" description: "mcp-publisher: The CLI that publishes a server.json to the official registry after namespace verification. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-publisher site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # mcp-publisher: definition and example | Agent MCP Directory > mcp-publisher: The CLI that publishes a server.json to the official registry after namespace verification. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-publisher Site: Agent MCP Directory Last reviewed: 2026-11-04 # mcp-publisher mcp-publisher: The CLI that publishes a server.json to the official registry after namespace verification. Example: The registry README says a pull request does not list a server. Next in the glossary is Model Context Protocol (MCP): A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. ## Definition The CLI that publishes a server.json to the official registry after namespace verification. ## Example, with source The registry README says a pull request does not list a server. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [CLIs as an agent surface](https://agentmcpdirectory.com/standards/cli-as-agent-surface/) - [Getting listed in registries](https://agentmcpdirectory.com/guides/get-listed-in-registries/) ## Neighbouring terms - [MCP server portal](https://agentmcpdirectory.com/glossary/mcp-server-portal/): Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. - [Model Context Protocol (MCP)](https://agentmcpdirectory.com/glossary/model-context-protocol/): A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. - [Multi round-trip request (MRTR)](https://agentmcpdirectory.com/glossary/multi-round-trip-request/): The 2026-07-28 pattern where a server returns input\_required and the client retries the request with the answers. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-publisher/index.md) ## Sources - [Source for the mcp-publisher example](https://github.com/modelcontextprotocol/registry), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP registry: definition and example | Agent MCP Directory" description: "MCP registry: A catalog of MCP server metadata that clients and directories read. Defined with a sourced example. Read 4 November 2026." canonical: https://agentmcpdirectory.com/glossary/mcp-registry site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # MCP registry: definition and example | Agent MCP Directory > MCP registry: A catalog of MCP server metadata that clients and directories read. Defined with a sourced example. Read 4 November 2026. Source: https://agentmcpdirectory.com/glossary/mcp-registry Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP registry MCP registry: A catalog of MCP server metadata that clients and directories read; the official one is registry.modelcontextprotocol.io. Example: The official registry has been in preview since 8 Sep 2025. Next in the glossary is MCP server: A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. ## Definition A catalog of MCP server metadata that clients and directories read; the official one is registry.modelcontextprotocol.io. ## Example, with source The official registry has been in preview since 8 Sep 2025. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Getting listed in registries](https://agentmcpdirectory.com/guides/get-listed-in-registries/) ## Neighbouring terms - [MCP host](https://agentmcpdirectory.com/glossary/mcp-host/): The LLM application that starts client connections and asks the user for consent. - [MCP server](https://agentmcpdirectory.com/glossary/mcp-server/): A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. - [MCP server portal](https://agentmcpdirectory.com/glossary/mcp-server-portal/): Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-registry/index.md) ## Sources - [Source for the MCP registry example](https://github.com/modelcontextprotocol/registry), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Resource: definition and example | Agent MCP Directory" description: "Resource: Context or data an MCP server offers for the user or model to read, addressed by URI. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-resource site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Resource: definition and example | Agent MCP Directory > Resource: Context or data an MCP server offers for the user or model to read, addressed by URI. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-resource Site: Agent MCP Directory Last reviewed: 2026-11-04 # Resource Resource: Context or data an MCP server offers for the user or model to read, addressed by URI. Example: Mintlify exposes skill.md files as MCP resources. Next in the glossary is Resource indicator: The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. ## Definition Context or data an MCP server offers for the user or model to read, addressed by URI. ## Example, with source Mintlify exposes skill.md files as MCP resources. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) - [Building a remote MCP server](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) ## Neighbouring terms - [Remote MCP server](https://agentmcpdirectory.com/glossary/remote-mcp-server/): An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. - [Resource indicator](https://agentmcpdirectory.com/glossary/resource-indicator/): The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. - [server.json](https://agentmcpdirectory.com/glossary/server-json/): The registry metadata file for one server: name, version, remotes, packages, website and repository. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-resource/index.md) ## Sources - [Source for the Resource example](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP server: definition and example | Agent MCP Directory" description: "MCP server: A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-server site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # MCP server: definition and example | Agent MCP Directory > MCP server: A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-server Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP server MCP server: A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. Example: Stripe runs its MCP server at https://mcp.stripe.com. Next in the glossary is MCP server portal: Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. ## Definition A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. ## Example, with source Stripe runs its MCP server at https://mcp.stripe.com. ([docs.stripe.com](https://docs.stripe.com/mcp), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) - [Building a remote MCP server](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) ## Neighbouring terms - [MCP registry](https://agentmcpdirectory.com/glossary/mcp-registry/): A catalog of MCP server metadata that clients and directories read; the official one is registry.modelcontextprotocol.io. - [MCP server portal](https://agentmcpdirectory.com/glossary/mcp-server-portal/): Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. - [mcp-publisher](https://agentmcpdirectory.com/glossary/mcp-publisher/): The CLI that publishes a server.json to the official registry after namespace verification. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-server/index.md) ## Sources - [Source for the MCP server example](https://docs.stripe.com/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP server portal: definition and example | Agent MCP Directory" description: "MCP server portal: Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls." canonical: https://agentmcpdirectory.com/glossary/mcp-server-portal site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # MCP server portal: definition and example | Agent MCP Directory > MCP server portal: Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. Source: https://agentmcpdirectory.com/glossary/mcp-server-portal Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP server portal MCP server portal: Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. Example: A portal supports up to 80 servers. Next in the glossary is mcp-publisher: The CLI that publishes a server.json to the official registry after namespace verification. ## Definition Cloudflare's product that puts many MCP servers behind one authenticated endpoint with per-tool controls. ## Example, with source A portal supports up to 80 servers. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Hosts and gateways compared](https://agentmcpdirectory.com/hosts/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [MCP server](https://agentmcpdirectory.com/glossary/mcp-server/): A program that exposes tools, resources or prompts to MCP clients over stdio or Streamable HTTP. - [mcp-publisher](https://agentmcpdirectory.com/glossary/mcp-publisher/): The CLI that publishes a server.json to the official registry after namespace verification. - [Model Context Protocol (MCP)](https://agentmcpdirectory.com/glossary/model-context-protocol/): A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-server-portal/index.md) ## Sources - [Source for the MCP server portal example](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Tool: definition and example | Agent MCP Directory" description: "Tool: A function an MCP server offers for the model to call, with a name, description and input schema. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/mcp-tool site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Tool: definition and example | Agent MCP Directory > Tool: A function an MCP server offers for the model to call, with a name, description and input schema. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/mcp-tool Site: Agent MCP Directory Last reviewed: 2026-11-04 # Tool Tool: A function an MCP server offers for the model to call, with a name, description and input schema. Example: Browserbase's tools are navigate, act, observe, extract, start and end. Next in the glossary is Tool annotations: Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. ## Definition A function an MCP server offers for the model to call, with a name, description and input schema. ## Example, with source Browserbase's tools are navigate, act, observe, extract, start and end. ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [Tasks extension](https://agentmcpdirectory.com/glossary/tasks-extension/): An official MCP extension for long-running operations with polling and durable handles, moved out of core in 2026-07-28. - [Tool annotations](https://agentmcpdirectory.com/glossary/tool-annotations/): Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. - [WebMCP](https://agentmcpdirectory.com/glossary/webmcp/): A draft browser API for pages to register JavaScript tools that an in-browser agent can call. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/mcp-tool/index.md) ## Sources - [Source for the Tool example](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Model Context Protocol (MCP): definition | Agent MCP Directory" description: "Model Context Protocol (MCP): A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts." canonical: https://agentmcpdirectory.com/glossary/model-context-protocol site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Model Context Protocol (MCP): definition | Agent MCP Directory > Model Context Protocol (MCP): A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. Source: https://agentmcpdirectory.com/glossary/model-context-protocol Site: Agent MCP Directory Last reviewed: 2026-11-04 # Model Context Protocol (MCP) Model Context Protocol (MCP): A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. Example: The current revision is dated 2026-07-28 and its schema lives at schema/2026-07-28/schema.ts. Also in the glossary is mcp-publisher: The CLI that publishes a server.json to the official registry after namespace verification. ## Definition A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. ## Example, with source The current revision is dated 2026-07-28 and its schema lives at schema/2026-07-28/schema.ts. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/latest), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [mcp-publisher](https://agentmcpdirectory.com/glossary/mcp-publisher/): The CLI that publishes a server.json to the official registry after namespace verification. - [Multi round-trip request (MRTR)](https://agentmcpdirectory.com/glossary/multi-round-trip-request/): The 2026-07-28 pattern where a server returns input\_required and the client retries the request with the answers. - [Namespace verification](https://agentmcpdirectory.com/glossary/namespace-verification/): Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP for domains. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/model-context-protocol/index.md) ## Sources - [Source for the Model Context Protocol (MCP) example](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Multi round-trip request (MRTR): definition | Agent MCP Directory" description: "Multi round-trip request (MRTR): The 2026-07-28 pattern where a server returns input_required and the client retries the request with the answers." canonical: https://agentmcpdirectory.com/glossary/multi-round-trip-request site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Multi round-trip request (MRTR): definition | Agent MCP Directory > Multi round-trip request (MRTR): The 2026-07-28 pattern where a server returns input_required and the client retries the request with the answers. Source: https://agentmcpdirectory.com/glossary/multi-round-trip-request Site: Agent MCP Directory Last reviewed: 2026-11-04 # Multi round-trip request (MRTR) Multi round-trip request (MRTR): The 2026-07-28 pattern where a server returns input\_required and the client retries the request with the answers. Example: It replaces server-initiated requests such as elicitation/create. Next in the glossary is Namespace verification: Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP for domains. ## Definition The 2026-07-28 pattern where a server returns input\_required and the client retries the request with the answers. ## Example, with source It replaces server-initiated requests such as elicitation/create. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) ## Neighbouring terms - [Model Context Protocol (MCP)](https://agentmcpdirectory.com/glossary/model-context-protocol/): A JSON-RPC 2.0 protocol in which hosts run clients that connect to servers offering tools, resources and prompts. - [Namespace verification](https://agentmcpdirectory.com/glossary/namespace-verification/): Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP for domains. - [NLWeb](https://agentmcpdirectory.com/glossary/nlweb/): Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses; each instance is an MCP server. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/multi-round-trip-request/index.md) ## Sources - [Source for the Multi round-trip request (MRTR) example](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Namespace verification: definition and example | Agent MCP Directory" description: "Namespace verification: Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP." canonical: https://agentmcpdirectory.com/glossary/namespace-verification site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Namespace verification: definition and example | Agent MCP Directory > Namespace verification: Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP. Source: https://agentmcpdirectory.com/glossary/namespace-verification Site: Agent MCP Directory Last reviewed: 2026-11-04 # Namespace verification Namespace verification: Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP for domains. Example: A me./ name requires proving control of the domain. Next in the glossary is NLWeb: Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses; each instance is an MCP server. ## Definition Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP for domains. ## Example, with source A me./ name requires proving control of the domain. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) ## Where it appears on this site - [Getting listed in registries](https://agentmcpdirectory.com/guides/get-listed-in-registries/) ## Neighbouring terms - [Multi round-trip request (MRTR)](https://agentmcpdirectory.com/glossary/multi-round-trip-request/): The 2026-07-28 pattern where a server returns input\_required and the client retries the request with the answers. - [NLWeb](https://agentmcpdirectory.com/glossary/nlweb/): Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses; each instance is an MCP server. - [Prompt](https://agentmcpdirectory.com/glossary/mcp-prompt/): A templated message or workflow an MCP server offers to users. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/namespace-verification/index.md) ## Sources - [Source for the Namespace verification example](https://github.com/modelcontextprotocol/registry), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "NLWeb: definition and example | Agent MCP Directory" description: "NLWeb: Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/nlweb site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # NLWeb: definition and example | Agent MCP Directory > NLWeb: Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/nlweb Site: Agent MCP Directory Last reviewed: 2026-11-04 # NLWeb NLWeb: Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses; each instance is an MCP server. Example: The reference implementation is in Python under MIT. Next in the glossary is Prompt: A templated message or workflow an MCP server offers to users. ## Definition Microsoft's open project giving sites a natural-language ask method with Schema.org JSON responses; each instance is an MCP server. ## Example, with source The reference implementation is in Python under MIT. ([github.com](https://github.com/nlweb-ai/NLWeb), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [NLWeb](https://agentmcpdirectory.com/standards/nlweb/) ## Neighbouring terms - [Namespace verification](https://agentmcpdirectory.com/glossary/namespace-verification/): Proof that a publisher controls a registry name, by GitHub login or OIDC for io.github names and DNS or HTTP for domains. - [Prompt](https://agentmcpdirectory.com/glossary/mcp-prompt/): A templated message or workflow an MCP server offers to users. - [Protected Resource Metadata](https://agentmcpdirectory.com/glossary/protected-resource-metadata/): The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/nlweb/index.md) ## Sources - [Source for the NLWeb example](https://github.com/nlweb-ai/NLWeb), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Protected Resource Metadata: definition | Agent MCP Directory" description: "Protected Resource Metadata: The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes." canonical: https://agentmcpdirectory.com/glossary/protected-resource-metadata site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Protected Resource Metadata: definition | Agent MCP Directory > Protected Resource Metadata: The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. Source: https://agentmcpdirectory.com/glossary/protected-resource-metadata Site: Agent MCP Directory Last reviewed: 2026-11-04 # Protected Resource Metadata Protected Resource Metadata: The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. Example: mcp-handler serves it from /.well-known/oauth-protected-resource. Next in the glossary is Remote MCP server: An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. ## Definition The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. ## Example, with source mcp-handler serves it from /.well-known/oauth-protected-resource. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [OAuth for MCP](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) ## Neighbouring terms - [Prompt](https://agentmcpdirectory.com/glossary/mcp-prompt/): A templated message or workflow an MCP server offers to users. - [Remote MCP server](https://agentmcpdirectory.com/glossary/remote-mcp-server/): An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. - [Resource](https://agentmcpdirectory.com/glossary/mcp-resource/): Context or data an MCP server offers for the user or model to read, addressed by URI. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/protected-resource-metadata/index.md) ## Sources - [Source for the Protected Resource Metadata example](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Remote MCP server: definition and example | Agent MCP Directory" description: "Remote MCP server: An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/remote-mcp-server site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Remote MCP server: definition and example | Agent MCP Directory > Remote MCP server: An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/remote-mcp-server Site: Agent MCP Directory Last reviewed: 2026-11-04 # Remote MCP server Remote MCP server: An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. Example: 37,977 of 56,677 official registry entries declared a remote on 4 Nov 2026. Next in the glossary is Resource: Context or data an MCP server offers for the user or model to read, addressed by URI. ## Definition An MCP server reached over the network, today through Streamable HTTP, rather than launched locally. ## Example, with source 37,977 of 56,677 official registry entries declared a remote on 4 Nov 2026. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Getting listed in registries](https://agentmcpdirectory.com/guides/get-listed-in-registries/) - [Building a remote MCP server](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) ## Neighbouring terms - [Protected Resource Metadata](https://agentmcpdirectory.com/glossary/protected-resource-metadata/): The RFC 9728 document an MCP server MUST publish to name its authorization servers and scopes. - [Resource](https://agentmcpdirectory.com/glossary/mcp-resource/): Context or data an MCP server offers for the user or model to read, addressed by URI. - [Resource indicator](https://agentmcpdirectory.com/glossary/resource-indicator/): The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/remote-mcp-server/index.md) ## Sources - [Source for the Remote MCP server example](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Resource indicator: definition and example | Agent MCP Directory" description: "Resource indicator: The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/resource-indicator site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Resource indicator: definition and example | Agent MCP Directory > Resource indicator: The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/resource-indicator Site: Agent MCP Directory Last reviewed: 2026-11-04 # Resource indicator Resource indicator: The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. Example: The spec example is resource=https%3A%2F%2Fmcp.example.com. Next in the glossary is server.json: The registry metadata file for one server: name, version, remotes, packages, website and repository. ## Definition The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. ## Example, with source The spec example is resource=https%3A%2F%2Fmcp.example.com. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [OAuth for MCP](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) ## Neighbouring terms - [Resource](https://agentmcpdirectory.com/glossary/mcp-resource/): Context or data an MCP server offers for the user or model to read, addressed by URI. - [server.json](https://agentmcpdirectory.com/glossary/server-json/): The registry metadata file for one server: name, version, remotes, packages, website and repository. - [server/discover](https://agentmcpdirectory.com/glossary/server-discover/): The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/resource-indicator/index.md) ## Sources - [Source for the Resource indicator example](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "server/discover: definition and example | Agent MCP Directory" description: "server/discover: The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity." canonical: https://agentmcpdirectory.com/glossary/server-discover site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # server/discover: definition and example | Agent MCP Directory > server/discover: The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. Source: https://agentmcpdirectory.com/glossary/server-discover Site: Agent MCP Directory Last reviewed: 2026-11-04 # server/discover server/discover: The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. Example: Clients may call it first or use it to probe older stdio servers. Next in the glossary is Stateless MCP: The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id; each request carries version and capabilities in \_meta. ## Definition The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. ## Example, with source Clients may call it first or use it to probe older stdio servers. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) ## Neighbouring terms - [server.json](https://agentmcpdirectory.com/glossary/server-json/): The registry metadata file for one server: name, version, remotes, packages, website and repository. - [Stateless MCP](https://agentmcpdirectory.com/glossary/stateless-mcp/): The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id; each request carries version and capabilities in \_meta. - [stdio transport](https://agentmcpdirectory.com/glossary/stdio-transport/): The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over standard streams. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/server-discover/index.md) ## Sources - [Source for the server/discover example](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "server.json: definition and example | Agent MCP Directory" description: "server.json: The registry metadata file for one server: name, version, remotes, packages, website and repository. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/server-json site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # server.json: definition and example | Agent MCP Directory > server.json: The registry metadata file for one server: name, version, remotes, packages, website and repository. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/server-json Site: Agent MCP Directory Last reviewed: 2026-11-04 # server.json server.json: The registry metadata file for one server: name, version, remotes, packages, website and repository. Example: Entries on 4 Nov 2026 used the 2025-12-11 server.json schema. Next in the glossary is server/discover: The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. ## Definition The registry metadata file for one server: name, version, remotes, packages, website and repository. ## Example, with source Entries on 4 Nov 2026 used the 2025-12-11 server.json schema. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026) ## Where it appears on this site - [Getting listed in registries](https://agentmcpdirectory.com/guides/get-listed-in-registries/) ## Neighbouring terms - [Resource indicator](https://agentmcpdirectory.com/glossary/resource-indicator/): The RFC 8707 resource parameter that names the MCP server a token is for; clients MUST send it. - [server/discover](https://agentmcpdirectory.com/glossary/server-discover/): The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. - [Stateless MCP](https://agentmcpdirectory.com/glossary/stateless-mcp/): The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id; each request carries version and capabilities in \_meta. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/server-json/index.md) ## Sources - [Source for the server.json example](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Stateless MCP: definition and example | Agent MCP Directory" description: "Stateless MCP: The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id. Defined with a sourced example. Read 4 November 2026." canonical: https://agentmcpdirectory.com/glossary/stateless-mcp site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Stateless MCP: definition and example | Agent MCP Directory > Stateless MCP: The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id. Defined with a sourced example. Read 4 November 2026. Source: https://agentmcpdirectory.com/glossary/stateless-mcp Site: Agent MCP Directory Last reviewed: 2026-11-04 # Stateless MCP Stateless MCP: The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id; each request carries version and capabilities in \_meta. Example: Cloudflare portals support stateless 2026-07-28 clients. Next in the glossary is stdio transport: The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over standard streams. ## Definition The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id; each request carries version and capabilities in \_meta. ## Example, with source Cloudflare portals support stateless 2026-07-28 clients. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Hosts and gateways compared](https://agentmcpdirectory.com/hosts/) ## Neighbouring terms - [server/discover](https://agentmcpdirectory.com/glossary/server-discover/): The 2026-07-28 RPC every server MUST implement to advertise supported protocol versions, capabilities and identity. - [stdio transport](https://agentmcpdirectory.com/glossary/stdio-transport/): The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over standard streams. - [Step-up authorization](https://agentmcpdirectory.com/glossary/step-up-authorization/): Requesting a wider scope set after a 403 insufficient\_scope challenge, keeping previously granted scopes. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/stateless-mcp/index.md) ## Sources - [Source for the Stateless MCP example](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "stdio transport: definition and example | Agent MCP Directory" description: "stdio transport: The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over." canonical: https://agentmcpdirectory.com/glossary/stdio-transport site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # stdio transport: definition and example | Agent MCP Directory > stdio transport: The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over. Source: https://agentmcpdirectory.com/glossary/stdio-transport Site: Agent MCP Directory Last reviewed: 2026-11-04 # stdio transport stdio transport: The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over standard streams. Example: Apify's local server runs with npx @apify/actors-mcp-server over stdio. Next in the glossary is Step-up authorization: Requesting a wider scope set after a 403 insufficient\_scope challenge, keeping previously granted scopes. ## Definition The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over standard streams. ## Example, with source Apify's local server runs with npx @apify/actors-mcp-server over stdio. ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Building a remote MCP server](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) ## Neighbouring terms - [Stateless MCP](https://agentmcpdirectory.com/glossary/stateless-mcp/): The 2026-07-28 model with no initialize handshake and no Mcp-Session-Id; each request carries version and capabilities in \_meta. - [Step-up authorization](https://agentmcpdirectory.com/glossary/step-up-authorization/): Requesting a wider scope set after a 403 insufficient\_scope challenge, keeping previously granted scopes. - [Streamable HTTP](https://agentmcpdirectory.com/glossary/streamable-http/): The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE stream. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/stdio-transport/index.md) ## Sources - [Source for the stdio transport example](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Step-up authorization: definition and example | Agent MCP Directory" description: "Step-up authorization: Requesting a wider scope set after a 403 insufficient_scope challenge, keeping previously granted scopes." canonical: https://agentmcpdirectory.com/glossary/step-up-authorization site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Step-up authorization: definition and example | Agent MCP Directory > Step-up authorization: Requesting a wider scope set after a 403 insufficient_scope challenge, keeping previously granted scopes. Source: https://agentmcpdirectory.com/glossary/step-up-authorization Site: Agent MCP Directory Last reviewed: 2026-11-04 # Step-up authorization Step-up authorization: Requesting a wider scope set after a 403 insufficient\_scope challenge, keeping previously granted scopes. Example: The Cloudflare API MCP server added step-up authorization on 19 Oct 2026. Next in the glossary is Streamable HTTP: The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE stream. ## Definition Requesting a wider scope set after a 403 insufficient\_scope challenge, keeping previously granted scopes. ## Example, with source The Cloudflare API MCP server added step-up authorization on 19 Oct 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [OAuth for MCP](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) ## Neighbouring terms - [stdio transport](https://agentmcpdirectory.com/glossary/stdio-transport/): The MCP binding where a client launches the server as a subprocess and exchanges newline-delimited JSON-RPC over standard streams. - [Streamable HTTP](https://agentmcpdirectory.com/glossary/streamable-http/): The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE stream. - [Tasks extension](https://agentmcpdirectory.com/glossary/tasks-extension/): An official MCP extension for long-running operations with polling and durable handles, moved out of core in 2026-07-28. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/step-up-authorization/index.md) ## Sources - [Source for the Step-up authorization example](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Streamable HTTP: definition and example | Agent MCP Directory" description: "Streamable HTTP: The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE." canonical: https://agentmcpdirectory.com/glossary/streamable-http site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Streamable HTTP: definition and example | Agent MCP Directory > Streamable HTTP: The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE. Source: https://agentmcpdirectory.com/glossary/streamable-http Site: Agent MCP Directory Last reviewed: 2026-11-04 # Streamable HTTP Streamable HTTP: The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE stream. Example: Zapier MCP requires clients that support Streamable HTTP. Next in the glossary is Tasks extension: An official MCP extension for long-running operations with polling and durable handles, moved out of core in 2026-07-28. ## Definition The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE stream. ## Example, with source Zapier MCP requires clients that support Streamable HTTP. ([docs.zapier.com](https://docs.zapier.com/mcp/home), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Building a remote MCP server](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) ## Neighbouring terms - [Step-up authorization](https://agentmcpdirectory.com/glossary/step-up-authorization/): Requesting a wider scope set after a 403 insufficient\_scope challenge, keeping previously granted scopes. - [Tasks extension](https://agentmcpdirectory.com/glossary/tasks-extension/): An official MCP extension for long-running operations with polling and durable handles, moved out of core in 2026-07-28. - [Tool](https://agentmcpdirectory.com/glossary/mcp-tool/): A function an MCP server offers for the model to call, with a name, description and input schema. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/streamable-http/index.md) ## Sources - [Source for the Streamable HTTP example](https://docs.zapier.com/mcp/home), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Tasks extension: definition and example | Agent MCP Directory" description: "Tasks extension: An official MCP extension for long-running operations with polling and durable handles. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/tasks-extension site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Tasks extension: definition and example | Agent MCP Directory > Tasks extension: An official MCP extension for long-running operations with polling and durable handles. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/tasks-extension Site: Agent MCP Directory Last reviewed: 2026-11-04 # Tasks extension Tasks extension: An official MCP extension for long-running operations with polling and durable handles, moved out of core in 2026-07-28. Example: The extension id is io.modelcontextprotocol/tasks. Next in the glossary is Tool: A function an MCP server offers for the model to call, with a name, description and input schema. ## Definition An official MCP extension for long-running operations with polling and durable handles, moved out of core in 2026-07-28. ## Example, with source The extension id is io.modelcontextprotocol/tasks. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) ## Where it appears on this site - [MCP](https://agentmcpdirectory.com/standards/mcp/) ## Neighbouring terms - [Streamable HTTP](https://agentmcpdirectory.com/glossary/streamable-http/): The MCP HTTP binding where each message is a POST to one endpoint and replies come as JSON or a request-scoped SSE stream. - [Tool](https://agentmcpdirectory.com/glossary/mcp-tool/): A function an MCP server offers for the model to call, with a name, description and input schema. - [Tool annotations](https://agentmcpdirectory.com/glossary/tool-annotations/): Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/tasks-extension/index.md) ## Sources - [Source for the Tasks extension example](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Tool annotations: definition and example | Agent MCP Directory" description: "Tool annotations: Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/tool-annotations site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # Tool annotations: definition and example | Agent MCP Directory > Tool annotations: Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/tool-annotations Site: Agent MCP Directory Last reviewed: 2026-11-04 # Tool annotations Tool annotations: Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. Example: Claude's directory requires a title and readOnlyHint or destructiveHint on every tool. Next in the glossary is WebMCP: A draft browser API for pages to register JavaScript tools that an in-browser agent can call. ## Definition Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. ## Example, with source Claude's directory requires a title and readOnlyHint or destructiveHint on every tool. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) ## Where it appears on this site - [Getting listed in registries](https://agentmcpdirectory.com/guides/get-listed-in-registries/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [Tool](https://agentmcpdirectory.com/glossary/mcp-tool/): A function an MCP server offers for the model to call, with a name, description and input schema. - [WebMCP](https://agentmcpdirectory.com/glossary/webmcp/): A draft browser API for pages to register JavaScript tools that an in-browser agent can call. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/tool-annotations/index.md) ## Sources - [Source for the Tool annotations example](https://claude.com/docs/connectors/building/submission), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "WebMCP: definition and example | Agent MCP Directory" description: "WebMCP: A draft browser API for pages to register JavaScript tools that an in-browser agent can call. Defined with a sourced example." canonical: https://agentmcpdirectory.com/glossary/webmcp site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Glossary" --- # WebMCP: definition and example | Agent MCP Directory > WebMCP: A draft browser API for pages to register JavaScript tools that an in-browser agent can call. Defined with a sourced example. Source: https://agentmcpdirectory.com/glossary/webmcp Site: Agent MCP Directory Last reviewed: 2026-11-04 # WebMCP WebMCP: A draft browser API for pages to register JavaScript tools that an in-browser agent can call. Example: The draft documents document.modelContext.registerTool(). Next in the glossary is Act layer: The part of agent readiness about completing tasks: MCP servers, CLIs, APIs with OpenAPI, WebMCP and agent payments. ## Definition A draft browser API for pages to register JavaScript tools that an in-browser agent can call. ## Example, with source The draft documents document.modelContext.registerTool(). ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) ## Where it appears on this site - [WebMCP](https://agentmcpdirectory.com/standards/webmcp/) - [Tool descriptions and agent success](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/) ## Neighbouring terms - [Tool annotations](https://agentmcpdirectory.com/glossary/tool-annotations/): Hints on a tool such as readOnlyHint and destructiveHint that tell clients how risky a call is. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/glossary/webmcp/index.md) ## Sources - [Source for the WebMCP example](https://github.com/webmachinelearning/webmcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Guides: build and ship for agents | Agent MCP Directory" description: "14 guides for shipping an MCP server, OAuth for agents, a CLI, WebMCP and OpenAPI, each with dated sources and this directory's numbers." canonical: https://agentmcpdirectory.com/guides site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Guides" --- # Guides: build and ship for agents | Agent MCP Directory > 14 guides for shipping an MCP server, OAuth for agents, a CLI, WebMCP and OpenAPI, each with dated sources and this directory's numbers. Source: https://agentmcpdirectory.com/guides Site: Agent MCP Directory Last reviewed: 2026-11-05 # Guides 14 guides for the act layer: building a remote MCP server, signing agents in with OAuth, shipping a CLI, adding WebMCP, exposing OpenAPI, getting listed, and testing the way an agent will. Every step is tied to a dated source and every guide shows what this directory measured. | Guide | The job | | --- | --- | | Build and ship a remote MCP server on Cloudflare or Vercel | Get a Streamable HTTP server live with auth on either host, with the exact packages and commands. | | OAuth for MCP servers: CIMD first, DCR for older clients | Implement the 2026-07-28 authorization flow end to end and know which registration methods clients will try. | | Put a CLI on npm for agents and document it | Ship a CLI an agent can run without a browser, with machine output and an exit code CI can read, using Ora, Stripe and Vercel as worked cases. | | Add WebMCP to a page | Register page tools through document.modelContext and know which browsers and agents will call them today. | | MCP, A2A and WebMCP by job | Choose the surface by the job: tools on a server, delegation to another agent, or actions on a live page. | | Get listed in each MCP registry | Publish once to the official registry and submit where review applies, with what each one checks. | | Test your MCP server the way an agent will | Run the calls a client makes, in order, read-only, and record what came back. | | What tool descriptions do to agent success | Write tool names, descriptions, schemas and annotations that agents select correctly and that reviewers accept. | | Expose an OpenAPI file agents can find | Publish the OpenAPI file where agents follow links to it, and decide when to wrap it as MCP. | | Keep an MCP server agent ready in CI | Fail the build when discovery, auth metadata or tool annotations regress. | | Remote MCP auth patterns compared | Pick between an open server, an API key and OAuth with or without client registration, and see what each looks like to an agent and in this directory. | | Publish an MCP server card | Describe an MCP server in a small JSON file that agents and scanners can read before they connect, using Ora's own cards as the worked example. | | How many tools an MCP server should list | Choose a tool count by what the servers in this directory list, what scanners reward and what Ora's own two servers do. | | Which MCP protocol versions and transports servers speak | See which protocol versions and transports the open MCP servers in this directory answered with, and which to support today. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/index.md) ## Sources - [Build and ship a remote MCP server on Cloudflare or Vercel](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026 - [OAuth for MCP servers: CIMD first, DCR for older clients](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 - [Put a CLI on npm for agents and document it](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 4 November 2026 - [Add WebMCP to a page](https://github.com/webmachinelearning/webmcp), read 4 November 2026 - [MCP, A2A and WebMCP by job](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026 - [Get listed in each MCP registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [Test your MCP server the way an agent will](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [What tool descriptions do to agent success](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 4 November 2026 - [Expose an OpenAPI file agents can find](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 4 November 2026 - [Publish an MCP server card](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 5 November 2026 - [How many tools an MCP server should list](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Add WebMCP to a page | Agent MCP Directory" description: "Add WebMCP to a page. Register page tools through document.modelContext and know which browsers and agents will call them today." canonical: https://agentmcpdirectory.com/guides/add-webmcp-to-a-page site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # Add WebMCP to a page | Agent MCP Directory > Add WebMCP to a page. Register page tools through document.modelContext and know which browsers and agents will call them today. Source: https://agentmcpdirectory.com/guides/add-webmcp-to-a-page Site: Agent MCP Directory Last reviewed: 2026-11-04 # Add WebMCP to a page Register page tools through document.modelContext and know which browsers and agents will call them today. The shared crawl found a WebMCP hint on 25 of 7,545 top-10,000 home pages. First step: Feature-detect document.modelContext. Last step: Test in a browser with the origin trial or flag enabled. ## Steps 1. Feature-detect document.modelContext. 2. Call registerTool with name, description, input schema and handler. 3. Set allow="tools" on cross-origin iframes that need it. 4. Test in a browser with the origin trial or flag enabled. ## What the sources say - The draft API is document.modelContext with registerTool(), getTools(), executeTool() and a toolchange event. ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) - Cross-origin iframes need Permissions Policy allow="tools". ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) - TypeScript definitions ship as webmcp-types on npm. ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) - nekuda's FAQ (October 2026): Chrome and Edge test WebMCP in an origin trial, Brave behind a flag, Firefox and Safari have none, and Gemini in Chrome and Claude for Chrome do not use WebMCP tools yet. ([webmcp.com](https://webmcp.com/), read 4 November 2026) - Ora's 30 Sep 2026 post demoed a WebMCP tool returning an MCP App View, requiring chrome://flags/#enable-webmcp-testing. ([ora.ai](https://ora.ai/blog/when-a-webmcp-tool-returns-an-mcp-app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), dated 30 September 2026, read 4 November 2026) ## How common it is The crawl reads each home page's initial HTML for a WebMCP hint. It found one on 25 of 7,545 home pages in the top 10,000 and on 59 of 3,393 on Ora's leaderboard. A hint in the HTML is not a working tool; check in a browser that registers it. ## Domains with a hint [agent-ready.dev](https://agentmcpdirectory.com/directory/agent-ready-dev/), agentready.org, [allbirds.com](https://agentmcpdirectory.com/directory/allbirds-com/), astronomer.io, august.com, awaytravel.com, bristlehealth.com, [browserless.io](https://agentmcpdirectory.com/directory/browserless-io/), casper.com, chiikawamarket.jp, circle.so, [circleci.com](https://agentmcpdirectory.com/directory/circleci-com/), [cloudflare.com](https://agentmcpdirectory.com/directory/cloudflare-com/), cookiebot.com, cratejoy.com, curacel.co, daisonet.com, [dartai.com](https://agentmcpdirectory.com/directory/dartai-com/), deepnight.ai, discoverpilgrim.com, ecoflow.com, elementor.com, everlane.com, evernote.com, feverup.com, flaviar.com, flexfits.com, getbinks.com, getcargo.ai, getcargo.io, getlago.com, givelegacy.com, glossier.com, gymshark.com, heypocket.com, [hostinger.com](https://agentmcpdirectory.com/directory/hostinger-com/), hypeandvice.com, isitagentready.com, linksys.com, lionpose.com, lucy.co, lusbrands.com, matagora.com, [monday.com](https://agentmcpdirectory.com/directory/monday-com/), mynextderma.com, nanit.com, naturallclub.com, nishatlinen.com, onrender.com, [ora.ai](https://agentmcpdirectory.com/directory/ora-ai/), pages.dev, playably.ai, popl.co, [primitive.dev](https://agentmcpdirectory.com/directory/primitive-dev/), quickchat.ai, rarebird.coffee, [render.com](https://agentmcpdirectory.com/directory/render-com/), rungroundcontrol.com, saya.pk, shipreal.dev, shoplocale.com, shoptiques.com, signnow.com, socksoho.com, soteriskin.com, soundboks.com, [telnyx.com](https://agentmcpdirectory.com/directory/telnyx-com/), theessential.com, usenourish.com, [usercentrics.eu](https://agentmcpdirectory.com/directory/usercentrics-eu/), usergems.com, usetaiga.com, vendah.com.br, webmcp.com, whitepages.com, whoosh.com, workers.dev, wpastra.com, wyndly.com, wyze.com, wyzecam.com, [youspot.com](https://agentmcpdirectory.com/directory/youspot-com/), zbiotics.com, zellbury.com, zenrows.com. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/add-webmcp-to-a-page/index.md) ## Sources - [Add WebMCP to a page](https://github.com/webmachinelearning/webmcp), read 4 November 2026 - [webmcp.com](https://webmcp.com/), read 4 November 2026 - [ora.ai/blog/when-a-webmcp-tool-returns-an-mcp-app](https://ora.ai/blog/when-a-webmcp-tool-returns-an-mcp-app?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Build and ship a remote MCP server | Agent MCP Directory" description: "Build and ship a remote MCP server on Cloudflare or Vercel. Get a Streamable HTTP server live with auth on either host, with the exact packages and commands." canonical: https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # Build and ship a remote MCP server | Agent MCP Directory > Build and ship a remote MCP server on Cloudflare or Vercel. Get a Streamable HTTP server live with auth on either host, with the exact packages and commands. Source: https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel Site: Agent MCP Directory Last reviewed: 2026-11-04 # Build and ship a remote MCP server on Cloudflare or Vercel Get a Streamable HTTP server live with auth on either host, with the exact packages and commands. Of 817 reachable endpoints in the directory, 812 speak Streamable HTTP. Verified handshakes took 1,175 ms at the median. First step: Cloudflare: scaffold the remote-mcp-authless template, run npm start, deploy with npx wrangler@latest deploy. ## Steps 1. Cloudflare: scaffold the remote-mcp-authless template, run npm start, deploy with npx wrangler@latest deploy. 2. Vercel: install mcp-handler@2.1.1, add app/api/mcp/route.ts, deploy. 3. Add auth: Workers OAuth Provider on Cloudflare, withMcpAuth plus your authorization server on Vercel. 4. Test with the MCP Inspector before connecting a client. ## What the sources say - Cloudflare scaffold: npm create cloudflare@latest -- remote-mcp-server-authless --template=cloudflare/ai/demos/remote-mcp-authless; local endpoint http://localhost:8788/mcp. ([developers.cloudflare.com](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026) - createMcpHandler on Cloudflare is stateless and needs no Durable Object; persist state in KV, D1 or a Durable Object. ([developers.cloudflare.com](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026) - Vercel: npm i mcp-handler@2.1.1 @modelcontextprotocol/server@2 zod@4 on Node.js 20 or later; export the handler as GET and POST. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - mcp-handler v2 dropped HTTP+SSE and Redis configuration. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - Test locally with npx @modelcontextprotocol/inspector@latest at http://127.0.0.1:6274 using the Streamable HTTP option. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - Cloudflare product servers retired /sse on 22 Oct 2026, so new servers should serve /mcp only. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), dated 22 October 2026, read 4 November 2026) ## What the directory sees on the wire | Transport | Endpoints | | --- | --- | | streamable-http | 812 | | sse | 5 | Handshakes with no credentials took 1,175 ms at the median, 2,222 ms at the 90th percentile and 4,442 ms at the slowest, across 263 verified servers. Host details and evidence: [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/), [Vercel](https://agentmcpdirectory.com/hosts/vercel/) and [Cloudflare vs Vercel](https://agentmcpdirectory.com/compare/cloudflare-vs-vercel/). ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/index.md) ## Sources - [Build and ship a remote MCP server on Cloudflare or Vercel](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026 - [vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Expose an OpenAPI file agents can find | Agent MCP Directory" description: "Expose an OpenAPI file agents can find. Publish the OpenAPI file where agents follow links to it, and decide when to wrap it as MCP." canonical: https://agentmcpdirectory.com/guides/expose-openapi-agents-can-find site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # Expose an OpenAPI file agents can find | Agent MCP Directory > Expose an OpenAPI file agents can find. Publish the OpenAPI file where agents follow links to it, and decide when to wrap it as MCP. Source: https://agentmcpdirectory.com/guides/expose-openapi-agents-can-find Site: Agent MCP Directory Last reviewed: 2026-11-04 # Expose an OpenAPI file agents can find Publish the OpenAPI file where agents follow links to it, and decide when to wrap it as MCP. 156 directory companies publish an OpenAPI file, and 21 of 7,472 top-10,000 domains do. First step: Serve openapi.json at a stable URL. ## Steps 1. Serve openapi.json at a stable URL. 2. Link it from docs and the home page. 3. Consider agents.json flows for multi-call tasks. 4. Wrap key operations as MCP tools through a gateway or your own server. ## What the sources say - Ora's lab found agents reached openapi.json in 21 percent of traced runs on sites that ship one, 97 percent through a link (19 Oct 2026). ([ora.ai](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), dated 19 October 2026, read 4 November 2026) - AgentReady.org lists a public API with OpenAPI as an act-layer SHOULD. ([ora.ai](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), dated 19 October 2026, read 4 November 2026) - agents.json 0.1.0 extends OpenAPI with flows and links at /.well-known/agents.json. ([github.com](https://github.com/wild-card-ai/agents-json), read 4 November 2026) - Kong's AI MCP Server entity turns existing APIs into MCP tools. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) - Stripe exposes its API through stripe\_api\_search, stripe\_api\_details, stripe\_api\_read and stripe\_api\_write instead of one tool per method. ([docs.stripe.com](https://docs.stripe.com/mcp), read 4 November 2026) ## How many publish one, and how it was found 156 of 1,336 directory companies publish an OpenAPI file at a path or in their docs. In the top 10,000, 21 of 7,472 probed domains serve a valid /openapi.json (0.28%). | Route | Companies | | --- | --- | | a direct request at the root path | 146 | | shared crawl of the top domains | 7 | | named in vendor documentation | 3 | Ora's lab found agents reached openapi.json on 21 percent of traced runs on sites that ship one, and 97 percent of those fetches came through a link ([source](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026; a vendor-published finding). Link the file from your docs. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/expose-openapi-agents-can-find/index.md) ## Sources - [Expose an OpenAPI file agents can find](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026 - [github.com/wild-card-ai/agents-json](https://github.com/wild-card-ai/agents-json), read 4 November 2026 - [developer.konghq.com/ai-gateway](https://developer.konghq.com/ai-gateway/), read 4 November 2026 - [docs.stripe.com/mcp](https://docs.stripe.com/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Get listed in each MCP registry | Agent MCP Directory" description: "Get listed in each MCP registry. Publish once to the official registry and submit where review applies, with what each one checks." canonical: https://agentmcpdirectory.com/guides/get-listed-in-registries site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # Get listed in each MCP registry | Agent MCP Directory > Get listed in each MCP registry. Publish once to the official registry and submit where review applies, with what each one checks. Source: https://agentmcpdirectory.com/guides/get-listed-in-registries Site: Agent MCP Directory Last reviewed: 2026-11-04 # Get listed in each MCP registry Publish once to the official registry and submit where review applies, with what each one checks. In the directory, 493 companies are in the official registry and 504 in the GitHub registry. First step: Official registry: mcp-publisher with GitHub, DNS or HTTP namespace proof. ## Steps 1. Official registry: mcp-publisher with GitHub, DNS or HTTP namespace proof. 2. Claude Connectors Directory: developer portal, annotations, OAuth. 3. GitHub MCP Registry: check your listing through the API. 4. Glama: Add Server; claim your listing. ## What the sources say - Publishing to the official registry uses the mcp-publisher CLI; pull requests do not list servers. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) - Reverse-DNS namespaces need DNS or HTTP proof; io.github./ needs that GitHub login. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) - Claude Connectors Directory needs a remote HTTPS URL, OAuth 2.0 for user data and title plus readOnlyHint or destructiveHint on every tool. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) - The GitHub MCP Registry API at api.mcp.github.com/v0/servers answered without a key on 4 Nov 2026 and listed 773 entries. ([api.mcp.github.com](https://api.mcp.github.com/v0/servers), read 4 November 2026) - Glama lets anyone add a server; 10,287 of 115,804 listings were claimed on 4 Nov 2026. ([glama.ai](https://glama.ai/mcp/servers), read 4 November 2026) ## Registries compared on submission | Registry | How a server gets in | Discoverability | | --- | --- | --- | | Smithery | unclear after acquisition | catalog browse only | | Glama | open, Add Server button | API with key and attribution | | Official MCP Registry | CLI with namespace verification | open paginated API | | GitHub MCP Registry | not documented on the page | open API and install buttons | | Claude Connectors Directory | portal, automated scan, optional human review | inside Claude | Directory companies listed: 493 in the official MCP Registry, 504 in the GitHub MCP Registry and 117 in the awesome-remote-mcp-servers list. A listing is only part of discovery; [a server card](https://agentmcpdirectory.com/guides/publish-an-mcp-server-card/) tells an agent what the server is before it connects. ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/get-listed-in-registries/index.md) ## Sources - [Get listed in each MCP registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 - [api.mcp.github.com/v0/servers](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [glama.ai/mcp/servers](https://glama.ai/mcp/servers), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "How many tools an MCP server should list | Agent MCP Directory" description: "How many tools an MCP server should list. Choose a tool count by what the servers in this directory list. 5 steps, each with a dated source." canonical: https://agentmcpdirectory.com/guides/how-many-tools-an-mcp-server-should-list site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Guides" --- # How many tools an MCP server should list | Agent MCP Directory > How many tools an MCP server should list. Choose a tool count by what the servers in this directory list. 5 steps, each with a dated source. Source: https://agentmcpdirectory.com/guides/how-many-tools-an-mcp-server-should-list Site: Agent MCP Directory Last reviewed: 2026-11-05 # How many tools an MCP server should list Choose a tool count by what the servers in this directory list, what scanners reward and what Ora's own two servers do. The median open server lists 8 tools and 31 list more than forty. First step: Count what tools/list returns; an agent reads that list before anything else. ## Steps 1. Count what tools/list returns; an agent reads that list before anything else. 2. Group tools by job and merge near-duplicates; fewer sharp tools beat many overlapping ones. 3. Name tools by action and object so the list reads at a glance. 4. Keep a docs server small and focused; let a product server be as broad as the product. 5. Re-count after each release. ## What the sources say - Ora's tool-listing check calls tools/list and grades the surface: product servers earn on breadth and docs servers on focus. ([ora.ai](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora's main MCP server lists 18 tools and its docs MCP server lists three: search\_docs, get\_docs\_page and get\_endpoint. ([ora.ai](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Arcade's rescan of 30 September 2026 found quality peaked at 16 to 31 tools per server; this is vendor research. ([www.arcade.dev](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 4 November 2026) - The 2026-07-28 MCP specification says servers SHOULD return tools in a deterministic order. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) ## Tool counts in the directory The 263 open servers by the number of tools they listed on 4 November 2026. The table has the counts and shares. | Tools listed | Servers | Share | | --- | --- | --- | | 1 | 5 | 1.9% | | 2-5 | 86 | 32.7% | | 6-10 | 65 | 24.7% | | 11-20 | 49 | 18.6% | | 21-40 | 27 | 10.3% | | 41-100 | 24 | 9.1% | | 100+ | 7 | 2.7% | ## The longest lists | Company | Tools | Ora score | | --- | --- | --- | | Courier courier.com | 173 | 57 C | | YouSpot youspot.com | 171 | 98 A+ | | AthenaHQ athenahq.ai | 113 | 67 C | | Ciphyr ciphyr.ai | 112 | | | Okfindex okfindex.com | 107 | | | Almxpp almxpp.com | 104 | | | AgentBIT agentbit.app | 101 | | | DC Hub dchub.cloud | 94 | | The median is 8, the largest list has 173 tools, and Ora's own main server lists 18 and its docs server three. Arcade's finding that quality peaks between 16 and 31 tools is vendor research and covers far more servers than this directory. [What Ora grades in a tool list](https://agentmcpdirectory.com/mcp-checks/#servers). ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/how-many-tools-an-mcp-server-should-list/index.md) ## Sources - [How many tools an MCP server should list](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [ora.ai/llms-full.txt](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 4 November 2026 - [modelcontextprotocol.io/specification/2026-07-28/changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [Ora leaderboard, GET /api/leaderboard](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Keep an MCP server agent ready in CI | Agent MCP Directory" description: "Keep an MCP server agent ready in CI. Fail the build when discovery, auth metadata or tool annotations regress. 4 steps, each with a dated source." canonical: https://agentmcpdirectory.com/guides/keep-mcp-agent-ready-in-ci site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # Keep an MCP server agent ready in CI | Agent MCP Directory > Keep an MCP server agent ready in CI. Fail the build when discovery, auth metadata or tool annotations regress. 4 steps, each with a dated source. Source: https://agentmcpdirectory.com/guides/keep-mcp-agent-ready-in-ci Site: Agent MCP Directory Last reviewed: 2026-11-04 # Keep an MCP server agent ready in CI Fail the build when discovery, auth metadata or tool annotations regress. The checks below match what this directory's connector records for every row. First step: Run a read-only connector against preview deploys. Last step: Gate the site score with a CLI threshold. ## Steps 1. Run a read-only connector against preview deploys. 2. Assert tools/list matches a snapshot. 3. Assert /.well-known/oauth-protected-resource returns JSON. 4. Gate the site score with a CLI threshold. ## What the sources say - npx ax audit --min-score 70 exits non-zero below the threshold and fails a CI step. ([ora.ai](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026) - Servers SHOULD return tools in deterministic order, which makes tools/list snapshots stable. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Vercel preview deployments with Deployment Protection and Rolling Releases are listed for MCP servers. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - HTTP+SSE is Deprecated in 2026-07-28 with at least a twelve-month window; test the Streamable HTTP endpoint. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Stripe will stop accepting full-access secret keys and untagged restricted keys on its MCP server in December 2026; migrate by 30 Nov 2026. ([docs.stripe.com](https://docs.stripe.com/mcp), dated 30 November 2026, read 4 November 2026) ## What a monthly re-check records - The endpoint, transport and protocol revision the server answered with. - The auth type, and the OAuth metadata the server published. - The tool, resource and prompt counts, and the tool names. - The time of the handshake and how long it took. - Whether the server was listed in the official and GitHub registries. See [the method](https://agentmcpdirectory.com/method/) for the status words and [the data page](https://agentmcpdirectory.com/data/) for every column. The CLI gate in the steps above is Ora's. [Why Ora is the pick, and where it falls short](https://agentmcpdirectory.com/test-your-mcp-server/). ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/keep-mcp-agent-ready-in-ci/index.md) ## Sources - [Keep an MCP server agent ready in CI](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026 - [modelcontextprotocol.io/specification/2026-07-28/changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [docs.stripe.com/mcp](https://docs.stripe.com/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Which MCP protocol versions and transports | Agent MCP Directory" description: "Which MCP protocol versions and transports servers speak. See which protocol versions and transports the open MCP servers in this directory answered." canonical: https://agentmcpdirectory.com/guides/mcp-protocol-versions-and-transports site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Guides" --- # Which MCP protocol versions and transports | Agent MCP Directory > Which MCP protocol versions and transports servers speak. See which protocol versions and transports the open MCP servers in this directory answered. Source: https://agentmcpdirectory.com/guides/mcp-protocol-versions-and-transports Site: Agent MCP Directory Last reviewed: 2026-11-05 # Which MCP protocol versions and transports servers speak See which protocol versions and transports the open MCP servers in this directory answered with, and which to support today. 263 open servers answered with 5 different protocol versions. First step: Read the protocol version your server returns in the handshake. ## Steps 1. Read the protocol version your server returns in the handshake. 2. Serve Streamable HTTP; HTTP+SSE is deprecated in the 2026-07-28 revision. 3. List the versions you support in your server card. 4. Test with a client from each era before dropping an old version. ## What the sources say - The 2026-07-28 MCP revision deprecates HTTP+SSE with a window of at least twelve months. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Servers on the 2026-07-28 revision MUST implement server/discover; earlier revisions open with an initialize handshake. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Ora's server cards list supported protocol versions 2025-11-25 and 2025-06-18 for both of its MCP servers. ([ora.ai](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora's integrations page says its server is compatible with clients that support protocol revisions through 2025-11-25. ([ora.ai](https://ora.ai/integrations?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora's check for a modern transport gives credit to a server that speaks Streamable HTTP and not only the legacy transport. ([ora.ai](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) ## What the open servers answered Protocol version in the handshake of the 263 open servers, 4 November 2026. The table has the same counts. | Protocol version | Servers | Share | | --- | --- | --- | | 2024-11-05 | 9 | 3.4% | | 2025-03-26 | 11 | 4.2% | | 2025-06-18 | 40 | 15.2% | | 2025-11-25 | 187 | 71.1% | | 2026-07-28 | 16 | 6.1% | ## Transports | Transport | Endpoints | | --- | --- | | streamable-http | 812 | | sse | 5 | A server that lists an older revision still works with clients from that era, and Ora's server cards list two revisions at once. [How to put the list in a card](https://agentmcpdirectory.com/guides/publish-an-mcp-server-card/) and [how Ora checks the transport](https://agentmcpdirectory.com/mcp-checks/#servers). ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/mcp-protocol-versions-and-transports/index.md) ## Sources - [Which MCP protocol versions and transports servers speak](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [ora.ai/api/mcp/server-card](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [ora.ai/integrations](https://ora.ai/integrations?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [ora.ai/api/checks](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP, A2A and WebMCP by job | Agent MCP Directory" description: "MCP, A2A and WebMCP by job. Choose the surface by the job: tools on a server, delegation to another agent, or actions on a live page." canonical: https://agentmcpdirectory.com/guides/mcp-vs-a2a-vs-webmcp site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # MCP, A2A and WebMCP by job | Agent MCP Directory > MCP, A2A and WebMCP by job. Choose the surface by the job: tools on a server, delegation to another agent, or actions on a live page. Source: https://agentmcpdirectory.com/guides/mcp-vs-a2a-vs-webmcp Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP, A2A and WebMCP by job Choose the surface by the job: tools on a server, delegation to another agent, or actions on a live page. A table below sets the three side by side. Use MCP for tools and data behind an API, A2A when another agent should take a task and WebMCP when a user is on the page and the agent acts there. ## Steps 1. Tools and data behind an API: MCP. 2. Another agent should take a task: A2A Agent Card. 3. A user is on the page and the agent acts there: WebMCP. ## What the sources say - MCP standard transports are stdio and Streamable HTTP. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026) - A2A 1.0.0 binds to JSON-RPC, gRPC or HTTP+JSON and publishes /.well-known/agent-card.json. ([a2a-protocol.org](https://a2a-protocol.org/latest/specification/), read 4 November 2026) - WebMCP tools live in the page and are reached through document.modelContext. ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) - MCP and A2A are both projects of the Agentic AI Foundation since A2A joined on 27 Aug 2026. ([a2a-protocol.org](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), dated 27 August 2026, read 4 November 2026) - Kong AI Gateway reports OpenTelemetry metrics for AI, MCP and A2A traffic side by side. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) ## The three side by side | Standard | What it is | Status and version | | --- | --- | --- | | Model Context Protocol | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | | Agent2Agent | A protocol for agents to discover each other through an Agent Card and exchange tasks and messages. | Specification 1.0.0 is the latest release; joined the Agentic AI Foundation on 27 Aug 2026. | | WebMCP | A browser API that lets a page register JavaScript functions as tools, with descriptions and schemas, that an in-browser agent can call. | Draft specification; Chrome and Edge test it in an origin trial, Brave behind a flag, no Firefox or Safari implementation (nekuda FAQ, October 2026). | Pairwise: [MCP vs A2A](https://agentmcpdirectory.com/compare/mcp-vs-a2a/), [MCP vs WebMCP](https://agentmcpdirectory.com/compare/mcp-vs-webmcp/) and [WebMCP vs agents.json](https://agentmcpdirectory.com/compare/webmcp-vs-agents-json/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/mcp-vs-a2a-vs-webmcp/index.md) ## Sources - [MCP, A2A and WebMCP by job](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026 - [a2a-protocol.org/latest/specification](https://a2a-protocol.org/latest/specification/), read 4 November 2026 - [github.com/webmachinelearning/webmcp](https://github.com/webmachinelearning/webmcp), read 4 November 2026 - [a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 - [developer.konghq.com/ai-gateway](https://developer.konghq.com/ai-gateway/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "OAuth for MCP servers: CIMD first, DCR | Agent MCP Directory" description: "OAuth for MCP servers: CIMD first, DCR for older clients. Implement the 2026-07-28 authorization flow end to end and know which registration methods clients." canonical: https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # OAuth for MCP servers: CIMD first, DCR | Agent MCP Directory > OAuth for MCP servers: CIMD first, DCR for older clients. Implement the 2026-07-28 authorization flow end to end and know which registration methods clients. Source: https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr Site: Agent MCP Directory Last reviewed: 2026-11-04 # OAuth for MCP servers: CIMD first, DCR for older clients Implement the 2026-07-28 authorization flow end to end and know which registration methods clients will try. In the directory, 517 endpoints offer dynamic client registration and 16 do not. First step: Return 401 with WWW-Authenticate resource\_metadata. Last step: Validate audience per RFC 8707 and iss per RFC 9207. ## Steps 1. Return 401 with WWW-Authenticate resource\_metadata. 2. Serve /.well-known/oauth-protected-resource (RFC 9728). 3. Point to an authorization server with RFC 8414 or OIDC discovery. 4. Accept CIMD client IDs; keep DCR for older clients. 5. Validate audience per RFC 8707 and iss per RFC 9207. ## What the sources say - MCP servers MUST implement OAuth 2.0 Protected Resource Metadata (RFC 9728). ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Clients obtain a client ID through Client ID Metadata Documents, pre-registration or Dynamic Client Registration; CIMD is SHOULD and DCR is MAY and deprecated. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Clients MUST send the resource parameter in both authorization and token requests, using the canonical server URI. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Servers SHOULD put a scope parameter in the WWW-Authenticate header, and SHOULD return 403 insufficient\_scope with all scopes the operation needs in one challenge. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Workers OAuth Provider v1 enables CIMD with clientIdMetadataDocumentEnabled and keeps DCR. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), dated 1 October 2026, read 4 November 2026) - Vercel MCP accepts CIMD clients without review since 2 Nov 2026; logo\_uri must be PNG or JPEG under 100 KB. ([vercel.com](https://vercel.com/docs/agent-resources/vercel-mcp), dated 2 November 2026, read 4 November 2026) ## What the directory sees | Auth type | Endpoints | | --- | --- | | No authentication | 263 | | API key | 19 | | OAuth with client registration | 517 | | OAuth without client registration | 16 | | Auth not determined | 2 | Dynamic client registration is deprecated in the 2026-07-28 specification, yet it is still the route 517 endpoints use; 191 endpoints state that they support client ID metadata documents. Which route servers actually take is in [the auth patterns compared](https://agentmcpdirectory.com/guides/remote-mcp-auth-patterns/). ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/index.md) ## Sources - [OAuth for MCP servers: CIMD first, DCR for older clients](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 - [developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [vercel.com/docs/agent-resources/vercel-mcp](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Publish an MCP server card | Agent MCP Directory" description: "Publish an MCP server card. Describe an MCP server in a small JSON file that agents and scanners can read before they connect." canonical: https://agentmcpdirectory.com/guides/publish-an-mcp-server-card site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Guides" --- # Publish an MCP server card | Agent MCP Directory > Publish an MCP server card. Describe an MCP server in a small JSON file that agents and scanners can read before they connect. Source: https://agentmcpdirectory.com/guides/publish-an-mcp-server-card Site: Agent MCP Directory Last reviewed: 2026-11-05 # Publish an MCP server card Describe an MCP server in a small JSON file that agents and scanners can read before they connect, using Ora's own cards as the worked example. 19 of 7,470 probed top-10,000 domains serve an MCP discovery file at /.well-known/mcp.json. First step: Choose the address: the server URL plus /server-card, or an entry in /.well-known/ai-catalog.json. ## Steps 1. Choose the address: the server URL plus /server-card, or an entry in /.well-known/ai-catalog.json. 2. Write the card: name, title, version, description, websiteUrl, icons and a remotes entry with type, url and supportedProtocolVersions. 3. Declare the kind of server, product or docs, so a scanner judges it on the right bar. 4. Serve it as JSON and link it from the docs; agents follow links. 5. Scan the server and confirm the server-card check passes. ## What the sources say - Ora serves a server card for its main MCP server at ora.ai/api/mcp/server-card; it names the server ai.ora/mcp, kind product, and lists a streamable-http remote at ora.ai/api/mcp with protocol versions 2025-11-25 and 2025-06-18. ([ora.ai](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora serves a second card at ora.ai/api/docs/mcp/server-card for its read-only docs server, declaring the kind docs; both cards point their $schema at static.modelcontextprotocol.io/schemas/v1/server-card.schema.json. ([ora.ai](https://ora.ai/api/docs/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora's server-card check looks for a card at the server URL plus /server-card or an entry in /.well-known/ai-catalog.json. ([ora.ai](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora's full documentation says its docs MCP server's card is at https://ora.ai/api/docs/mcp/server-card. ([ora.ai](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - The MCP maintainers' roadmap says server cards continue in a Working Group. ([blog.modelcontextprotocol.io](https://blog.modelcontextprotocol.io/posts/mcp-roadmap/), read 4 November 2026) - The 2026-07-28 core specification prescribes no .well-known discovery file; server cards are still Working Group work. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/latest), read 4 November 2026) - Mintlify says it publishes discovery files at /.well-known/mcp, /.well-known/mcp.json, /.well-known/mcp/server-card.json and /.well-known/mcp/server-cards.json. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) ## A worked example: Ora's two cards Ora serves a card for each of its two MCP servers. They share a schema and differ in name, kind and address; the protocol versions are the same. The main card, as served on 5 November 2026: ```json { "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json", "name": "ai.ora/mcp", "title": "ora", "version": "1.38.0", "description": "Find products, check agent-readiness scores, run scans and checks, and read or submit feedback.", "websiteUrl": "https://ora.ai/mcp", "icons": [ { "src": "https://ora.ai/icon.png" } ], "remotes": [ { "type": "streamable-http", "url": "https://ora.ai/api/mcp", "supportedProtocolVersions": [ "2025-11-25", "2025-06-18" ] } ], "url": "https://ora.ai/api/mcp", "transport": "streamable-http", "kind": "product", "_meta": { "ai.ora/kind": "product" } } ``` | Field | Main server | Docs server | | --- | --- | --- | | name | ai.ora/mcp | ai.ora/docs | | title | ora | ora Docs | | kind | product | docs | | remote type and URL | streamable-http, https://ora.ai/api/mcp | streamable-http, https://ora.ai/api/docs/mcp | | supportedProtocolVersions | 2025-11-25, 2025-06-18 | 2025-11-25, 2025-06-18 | | version | 1.38.0 | 1.38.0 | ## Who publishes a discovery file The Act Layer Census probed 7,470 of the top 10,000 domains for /.well-known/mcp.json and found 19 valid files (0.25%). Of the 1,336 companies in the directory, 39 serve one. A card is a different file from that manifest; Ora's check accepts a card at the server URL plus /server-card or a listing in /.well-known/ai-catalog.json. [The census](https://agentmcpdirectory.com/census/). The shape of a card is still settling: the MCP maintainers keep server cards in a Working Group, and the core specification names no discovery file. Publish the card where a scanner looks and keep the fields in the schema's own names. [How Ora checks it](https://agentmcpdirectory.com/mcp-checks/#servers). ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/publish-an-mcp-server-card/index.md) ## Sources - [Publish an MCP server card](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [ora.ai/api/docs/mcp/server-card](https://ora.ai/api/docs/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [ora.ai/api/checks](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [ora.ai/llms-full.txt](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [blog.modelcontextprotocol.io/posts/mcp-roadmap](https://blog.modelcontextprotocol.io/posts/mcp-roadmap/), read 4 November 2026 - [modelcontextprotocol.io/specification/latest](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 - [www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Remote MCP auth patterns compared | Agent MCP Directory" description: "Remote MCP auth patterns compared. Pick between an open server, an API key and OAuth with or without client registration." canonical: https://agentmcpdirectory.com/guides/remote-mcp-auth-patterns site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Guides" --- # Remote MCP auth patterns compared | Agent MCP Directory > Remote MCP auth patterns compared. Pick between an open server, an API key and OAuth with or without client registration. Source: https://agentmcpdirectory.com/guides/remote-mcp-auth-patterns Site: Agent MCP Directory Last reviewed: 2026-11-05 # Remote MCP auth patterns compared Pick between an open server, an API key and OAuth with or without client registration, and see what each looks like to an agent and in this directory. Of 817 reachable endpoints, 263 need no credentials and 533 publish OAuth metadata. ## Steps 1. Decide who the server is for: a public docs server can stay open, a product server acts for a signed-in user. 2. Open: list tools to any client and keep anything sensitive out of reach. 3. API key: answer 401 with a message a person can act on; an agent cannot register itself for a key. 4. OAuth: publish protected resource metadata so a client finds the flow without a person wiring it. 5. Test the 401 challenge, the metadata documents and PKCE with S256 before launch. ## What the sources say - Ora's catalog grades auth by fit: docs MCP servers should be public and product MCP servers should require OAuth. ([ora.ai](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora checks OAuth metadata under RFC 8414 as a way for agents to discover the sign-in flow automatically. ([ora.ai](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - Ora checks that the OAuth flow supports PKCE with the S256 method. ([ora.ai](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) - The 2026-07-28 MCP specification requires servers to implement OAuth 2.0 Protected Resource Metadata (RFC 9728). ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Clients obtain a client ID through Client ID Metadata Documents, pre-registration or Dynamic Client Registration; the specification marks CIMD as SHOULD and DCR as MAY and deprecated. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Ora says that when an MCP server requires authentication, a scan returns MCP\_AUTH\_REQUIRED with no score or grade. ([ora.ai](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026) ## The four patterns in the directory Reachable endpoints by the auth type the connector saw on 4 November 2026. The table has the same counts, what a client sees and four of the most visited examples. | Pattern | Endpoints | Tools listed | What a client sees | Examples | | --- | --- | --- | --- | --- | | No authentication | 263 | 263 | The server listed its tools to a client that sent no credentials. | Google, Cloudflare, Google Cloud, Microsoft | | API key | 19 | 0 | The server answered 401 or 403 and asks for a key or bearer token with no OAuth metadata for an agent to follow. | StackOverflow, Appcircle, Bitculator, Cavyro | | OAuth with client registration | 517 | 0 | The server publishes OAuth metadata and a registration endpoint, so a client can register itself without a human filling in a form first. | Sentry, PayPal, Stripe, Amplitude | | OAuth without client registration | 16 | 0 | The server publishes OAuth metadata but no registration endpoint, so a client must be registered by hand or identified by a client ID metadata document. | GitHub, Microsoft 365, Zoom, HubSpot | ## What a scanner expects Ora's catalog grades the match between a server's auth and its job: docs servers should be public and product servers should require OAuth, and its check asks whether the auth matches what the server does. A server that requires sign-in cannot be scored from outside at all; Ora returns `MCP_AUTH_REQUIRED` with no score or grade. [How Ora tests an MCP server](https://agentmcpdirectory.com/test-your-mcp-server/) and [the OAuth checks](https://agentmcpdirectory.com/mcp-checks/#servers). The OAuth route itself, with client ID metadata documents and dynamic registration, is in [the OAuth guide](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/). ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/remote-mcp-auth-patterns/index.md) ## Sources - [Remote MCP auth patterns compared](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 - [ora.ai/api/checks](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [ora.ai/llms.txt](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Put a CLI on npm for agents and document it | Agent MCP Directory" description: "Put a CLI on npm for agents and document it. Ship a CLI an agent can run without a browser, with machine output and an exit code CI can read, using Ora." canonical: https://agentmcpdirectory.com/guides/ship-a-cli-for-agents site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Guides" --- # Put a CLI on npm for agents and document it | Agent MCP Directory > Put a CLI on npm for agents and document it. Ship a CLI an agent can run without a browser, with machine output and an exit code CI can read, using Ora. Source: https://agentmcpdirectory.com/guides/ship-a-cli-for-agents Site: Agent MCP Directory Last reviewed: 2026-11-05 # Put a CLI on npm for agents and document it Ship a CLI an agent can run without a browser, with machine output and an exit code CI can read, using Ora, Stripe and Vercel as worked cases. 36 of 1,336 directory companies have a CLI package on record. First step: Make it runnable with npx and no account for read-only commands. ## Steps 1. Make it runnable with npx and no account for read-only commands. 2. Offer --json output. 3. Fail with a non-zero exit code on a threshold. 4. Have the CLI configure your MCP server for detected agents. ## What the sources say - Ora's npx ax audit runs with zero install and no account; --json returns the full report; --min-score exits non-zero below the threshold. ([ora.ai](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026) - Stripe's stripe agent setup (from @stripe/cli) detects installed agents and configures the MCP server and skills. ([docs.stripe.com](https://docs.stripe.com/mcp), read 4 November 2026) - Vercel's npx add-mcp https://mcp.vercel.com detects AI clients and configures each; -y skips confirmation and -g installs globally. ([vercel.com](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026) - Neon's npx neon@latest init sets up the MCP server, skills and a linked project. ([neon.com](https://neon.com/docs/ai/neon-mcp-server), read 4 November 2026) - AgentReady.org accepts a CLI in place of an MCP server for the act-layer MUST. ([ora.ai](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), dated 19 October 2026, read 4 November 2026) ## Case studies, asked the same questions | Company | Package | Latest | Last publish | Commands | | --- | --- | --- | --- | --- | | Neon | neonctl (npm) | 8.18.0 | 2026-11-03 | neon, neonctl | | Shopify | @shopify/cli (npm) | 5.0.1 | 2026-11-04 | shopify | | Supabase | supabase (npm) | 3.0.0 | 2026-11-02 | supabase | | Vercel | vercel (npm) | 65.11.0 | 2026-11-03 | vc, vercel | | Stripe | @stripe/cli (npm) | 1.55.8 | 2026-11-03 | stripe | | Ora | ax (npm) | 0.10.3 | 2026-10-28 | ax | Ora's CLI is documented at [ora.ai/docs/cli](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide): `npx ax audit yourdomain.com` scores a domain, and the documented flags include `--json` for machine-readable output and `--min-score` for a pass or fail exit in CI. The npm record for `ax` was read separately from the directory run on 4 November 2026. Stripe's CLI is on npm as `@stripe/cli` (v1.55.8, published 3 November 2026, command `stripe`, read on 5 November 2026); its [README](https://raw.githubusercontent.com/stripe/stripe-cli/master/README.md) also lists Homebrew, Scoop and a Docker image. A flag for machine-readable output was checked for Ora's CLI only (`--json`); Stripe's was not. ## Every CLI on record | Company | Package | Latest | Last publish | | --- | --- | --- | --- | | Amazon Web Services | awscli | 1.46.2 | 2026-10-21 | | Anthropic | @anthropic-ai/claude-code | 2.1.318 | 2026-11-03 | | Apify | apify-cli | 1.11.0 | 2026-10-29 | | Canva | @canva/cli | 2.17.0 | 2026-11-02 | | Cloudflare | wrangler | 4.157.0 | 2026-11-03 | | Composio | composio | 0.31.0 | 2026-11-03 | | Contentful | contentful-cli | 4.0.14 | 2026-11-02 | | Convex | convex | 1.49.0 | 2026-10-30 | | Datadog | @datadog/datadog-ci | 5.27.0 | 2026-11-04 | | Deno | deno | 2.9.6 | 2026-08-27 | | Expo | eas-cli | 27.4.1 | 2026-11-04 | | Firebase | firebase-tools | 15.35.0 | 2026-11-04 | | Google Gemini | @google/gemini-cli | 0.66.0 | 2026-10-27 | | Heroku | heroku | 11.12.1 | 2026-10-22 | | HubSpot | @hubspot/cli | 8.18.0 | 2026-10-27 | | Hugging Face | huggingface_hub | 2.4.0 | 2026-10-29 | | Microsoft Learn | azure-cli | 2.92.0 | 2026-11-03 | | Mintlify | mint | 4.2.1201 | 2026-11-04 | | Modal | modal | 1.6.3 | 2026-10-27 | | Neon | neonctl | 8.18.0 | 2026-11-03 | | Netlify | netlify-cli | 27.16.2 | 2026-11-02 | | ngrok | ngrok | 5.0.0-beta.2 | 2023-05-07 | | OpenAI | @openai/codex | 0.166.0 | 2026-10-29 | | Prisma | prisma | 8.0.0-rc.30 | 2026-11-03 | | Railway | @railway/cli | 5.71.0 | 2026-10-19 | | Salesforce | @salesforce/cli | 2.157.8 | 2026-11-03 | | Sanity | @sanity/cli | 8.27.0 | 2026-10-30 | | Sentry | @sentry/cli | 3.8.2 | 2026-10-22 | | Shopify | @shopify/cli | 5.0.1 | 2026-11-04 | | Snowflake | snowflake-cli | 3.32.1 | 2026-11-02 | | Supabase | supabase | 3.0.0 | 2026-11-02 | | Twilio | twilio-cli | 7.2.0 | 2026-10-13 | | Vercel | vercel | 65.11.0 | 2026-11-03 | | Webflow | @webflow/webflow-cli | 2.15.0 | 2026-10-27 | | Wix | @wix/cli | 1.2.8 | 2026-11-01 | | Zapier | zapier-platform-cli | 19.3.0 | 2026-10-30 | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/index.md) ## Sources - [Put a CLI on npm for agents and document it](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026 - [docs.stripe.com/mcp](https://docs.stripe.com/mcp), read 4 November 2026 - [vercel.com/docs/agent-resources/vercel-mcp](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 - [neon.com/docs/ai/neon-mcp-server](https://neon.com/docs/ai/neon-mcp-server), read 4 November 2026 - [ora.ai/blog/agentready-launch](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 4 November 2026 - [npm record for ax](https://registry.npmjs.org/ax), read 4 November 2026 - [npm record for @stripe/cli](https://registry.npmjs.org/@stripe%2Fcli), read 5 November 2026 - [Stripe CLI release v1.55.8](https://github.com/stripe/stripe-cli/releases/tag/v1.55.8), read 5 November 2026 - [Stripe CLI documentation](https://docs.stripe.com/stripe-cli), read 5 November 2026 (vendor documentation) Last reviewed 5 November 2026 --- --- title: "Test your MCP server the way an agent will | Agent MCP Directory" description: "Test your MCP server the way an agent will. Run the calls a client makes, in order, read-only, and record what came back." canonical: https://agentmcpdirectory.com/guides/test-mcp-like-an-agent site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # Test your MCP server the way an agent will | Agent MCP Directory > Test your MCP server the way an agent will. Run the calls a client makes, in order, read-only, and record what came back. Source: https://agentmcpdirectory.com/guides/test-mcp-like-an-agent Site: Agent MCP Directory Last reviewed: 2026-11-04 # Test your MCP server the way an agent will Run the calls a client makes, in order, read-only, and record what came back. Across 263 verified servers the handshake took 1,175 ms at the median. First step: Call server/discover (2026-07-28) or initialize (older servers). Last step: Never call a tool that changes state in a test. ## Steps 1. Call server/discover (2026-07-28) or initialize (older servers). 2. List tools, resources and prompts. 3. Check the 401 challenge and resource metadata. 4. Never call a tool that changes state in a test. ## What the sources say - 2026-07-28 servers MUST implement server/discover; clients MAY call it first or use it to probe older stdio servers. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Earlier revisions used an initialize handshake; clients detect the era and fall back, per the versioning page. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026) - List results now carry ttlMs and cacheScope, and servers SHOULD return tools in a deterministic order. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Unauthenticated requests should get 401 with a WWW-Authenticate header naming resource\_metadata. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Claude's submission flow asks you to confirm every tool was run through MCP Inspector or a custom connector. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) ## What the directory's connector does - It requests the endpoint with a read-only client and sends only the methods on the allowlist: `initialize`, `notifications/initialized`, `tools/list`, `resources/list`, `prompts/list` and `ping`. - It tries the 2026-07-28 revision first and falls back to 2025-11-25, then to the legacy SSE transport. - It never calls a tool. - At the median a verified server answered in 1,175 ms; the 90th percentile was 2,222 ms. The full method, including the allowlist, is on [the method page](https://agentmcpdirectory.com/method/#allowlist). To score a server on the checks an agent depends on, rather than read raw calls, use [Ora, the pick for testing an MCP server](https://agentmcpdirectory.com/test-your-mcp-server/); [the 28 checks](https://agentmcpdirectory.com/mcp-checks/) say what it looks at. ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/test-mcp-like-an-agent/index.md) ## Sources - [Test your MCP server the way an agent will](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [modelcontextprotocol.io/specification/2026-07-28/basic/transports](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026 - [modelcontextprotocol.io/specification/2026-07-28/basic/authorization](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 - [claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "What tool descriptions do to agent success | Agent MCP Directory" description: "What tool descriptions do to agent success. Write tool names, descriptions, schemas and annotations that agents select correctly and that reviewers accept." canonical: https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Guides" --- # What tool descriptions do to agent success | Agent MCP Directory > What tool descriptions do to agent success. Write tool names, descriptions, schemas and annotations that agents select correctly and that reviewers accept. Source: https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success Site: Agent MCP Directory Last reviewed: 2026-11-04 # What tool descriptions do to agent success Write tool names, descriptions, schemas and annotations that agents select correctly and that reviewers accept. The median open server lists 8 tools; the largest lists 173. First step: Name tools by action and object. Last step: Keep the tool count moderate. ## Steps 1. Name tools by action and object. 2. Describe inputs, outputs and failure. 3. Add title and readOnlyHint or destructiveHint. 4. Keep the tool count moderate. ## What the sources say - Arcade's rescan (30 Sep 2026) scored average tool names at 79 and descriptions and input schemas at 57 each; seven in ten servers give no useful guidance when a call fails. Vendor research. ([www.arcade.dev](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), dated 30 September 2026, read 4 November 2026) - In the same rescan, tool annotations added nearly 11 points, and quality peaked at 16 to 31 tools per server. ([www.arcade.dev](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), dated 30 September 2026, read 4 November 2026) - Nearly 17,000 servers ship a destructive or irreversible tool, and only 14 percent declare safety annotations (Arcade, 30 Sep 2026). ([www.arcade.dev](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), dated 30 September 2026, read 4 November 2026) - Claude's directory requires a title and readOnlyHint or destructiveHint on every tool. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) - The 2025-11-25 revision added guidance on tool names (SEP-986) and input validation errors returned as tool execution errors so models can self-correct. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2025-11-25/changelog), dated 25 November 2025, read 4 November 2026) ## What public servers look like Across 263 open servers the median tool count is 8, 31 list more than 40 tools, and the largest lists 173. Of 3,541 recorded tool names, 837 start with get, 253 start with list, 177 start with search, 97 start with create, 40 start with update, 33 start with delete. | Company | Tools | First names | | --- | --- | --- | | Courier | 173 | list_messages, get_message, get_message_content | | YouSpot | 171 | read_web_page, web_search, check_page_changes | | AthenaHQ | 113 | open_ai_access, check_public_ai_access, get_prompt_schedules | | Ciphyr | 112 | create_passport, whoami, invite_agent | | Okfindex | 107 | api_index, search_bundles, get_bundle | | Almxpp | 104 | validate_best_practices, find_extensions, ado_create_bug_from_test | | AgentBIT | 101 | agentbit_discover, agentbit_route, agentbit.address_eip55 | | DC Hub | 94 | execute_plan, claim_free_key, search | How many tools a server lists is a separate question: [the tool-count guide](https://agentmcpdirectory.com/guides/how-many-tools-an-mcp-server-should-list/) shows what the directory's servers do. ## Testing your own MCP server Ora scans an MCP server URL and runs 28 of its 132 public checks on it, with check sets that differ for a docs server and a product server. It is the check this directory recommends; it reads public URLs only and publishes no repeat-scan data. [The reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/guides/tool-descriptions-and-agent-success/index.md) ## Sources - [What tool descriptions do to agent success](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 4 November 2026 - [claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 - [modelcontextprotocol.io/specification/2025-11-25/changelog](https://modelcontextprotocol.io/specification/2025-11-25/changelog), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP hosts, registries and gateways compared | Agent MCP Directory" description: "16 MCP hosts, registries and AI gateways scored on one published rubric, with the evidence and a read date on every cell." canonical: https://agentmcpdirectory.com/hosts site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # MCP hosts, registries and gateways compared | Agent MCP Directory > 16 MCP hosts, registries and AI gateways scored on one published rubric, with the evidence and a read date on every cell. Source: https://agentmcpdirectory.com/hosts Site: Agent MCP Directory Last reviewed: 2026-11-04 # Hosts, registries and gateways compared 16 products that host, list or front MCP servers, read on 4 November 2026 and scored on one published rubric: transport, sign-in, per-tool scoping, limits, price and discoverability. Every cell carries its evidence and a source link; nothing is scored without one. ## Hosts and tool gateways | Product | Remote transport | OAuth with client registration | Per-tool auth scoping | Hosting and scale limits | Pricing | | --- | --- | --- | --- | --- | --- | | Cloudflare | Streamable HTTP only | yes, DCR and CIMD | yes, at the portal | 80 servers per portal | not published for MCP | | Vercel | Streamable HTTP only | bring your own AS; CIMD on Vercel MCP | scopes per handler | Vercel Functions limits | Functions pricing | | Composio | HTTP | Composio holds app OAuth | yes, allowed_tools | 2,000 to 10,000 requests a minute | 0 / 29 USD / custom | | Zapier MCP | Streamable HTTP only | OAuth for clients | yes, app and action level | task quota | included, tasks per call | | Mintlify MCP | Streamable HTTP | client credentials at /authed/mcp/oauth/token | public versus authed endpoints | published rate limits | MCP included; WebMCP Pro or Enterprise | | Apify MCP | Streamable HTTP and stdio | OAuth | tools parameter selects Actors | Actor run limits | per Actor run | | Browserbase MCP | Streamable HTTP | no, API key in URL | no | not stated | not stated on MCP pages | ## Registries and directories | Product | Remote transport | Registry submission | Discoverability by agents | Own server in the registries | | --- | --- | --- | --- | --- | | Smithery | Streamable HTTP (registry entries) | unclear after acquisition | catalog browse only | no own server found | | Glama | lists both | open, Add Server button | API with key and attribution | not found | | Official MCP Registry | records both | CLI with namespace verification | open paginated API | not applicable | | GitHub MCP Registry | records remotes | not documented on the page | open API and install buttons | yes | | Claude Connectors Directory | remote HTTPS required | portal, automated scan, optional human review | inside Claude | docs server listed | ## AI gateways | Product | Protocols fronted | Auth passthrough | Caching | Pricing | Observability | | --- | --- | --- | --- | --- | --- | | Cloudflare AI Gateway | model APIs; MCP goes through portals | BYOK or Unified Billing | yes, free | free core, 5 percent on credits | analytics and logs | | Vercel AI Gateway | model APIs | BYOK with system fallback | not on the pricing page | no markup, paid add-ons | budgets, reporting, trace drains | | Portkey | model APIs and MCP | credential injection | simple cache, 1-day TTL on Developer | free / 49 USD / custom | per tool call logs | | Kong AI Gateway | model APIs, MCP, A2A | OAuth2 auth strategies | semantic cache | not published on the docs page | OpenTelemetry, Konnect dashboards, audit logs | ## The rubric | Remote transport | Which remote transports the product serves or lists: Streamable HTTP, or the deprecated HTTP+SSE. | | --- | --- | | OAuth with client registration | Whether an agent can sign in without a human creating an app first: dynamic client registration or client ID metadata documents. | | Per-tool auth scoping | Whether access can be limited tool by tool, not only for the server as a whole. | | Hosting and scale limits | Limits the vendor publishes on servers, calls, size or concurrency. | | Observability | What logs, analytics or health checks the owner of a server gets. | | Pricing | The published price, with the date it was read. | | Registry submission | How a server gets listed and whether the listing is verified. | | Discoverability by agents | Whether an agent can find servers through the product, by a public catalog or an API. | | Own server in the registries | Whether the vendor's own MCP server is listed where agents look, checked against the official registry. | AI gateways use their own five-line rubric, because they sit in front of model APIs and tools rather than hosting a server. | Protocols fronted | Which protocols the gateway sits in front of: model APIs, MCP, A2A. | | --- | --- | | Auth passthrough | How caller identity and provider keys pass through the gateway. | | Caching | What the gateway caches and how. | | Pricing | The published price, with the date it was read. | | Observability | What logs and traces the gateway exposes. | ## Head-to-heads - [Cloudflare vs Vercel](https://agentmcpdirectory.com/compare/cloudflare-vs-vercel/) - [Smithery vs Glama](https://agentmcpdirectory.com/compare/smithery-vs-glama/) - [Composio vs Zapier MCP](https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp/) - [Official MCP Registry vs GitHub MCP Registry](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry/) - [Official MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory/) - [GitHub MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory/) - [Cloudflare vs Composio](https://agentmcpdirectory.com/compare/cloudflare-vs-composio/) - [Vercel vs Mintlify MCP](https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp/) - [Apify MCP vs Browserbase MCP](https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase/) - [Cloudflare AI Gateway vs Vercel AI Gateway](https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway/) - [Portkey vs Kong AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway/) - [Portkey vs Cloudflare AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway/) - [Zapier MCP vs Apify MCP](https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp/) - [Smithery vs Official MCP Registry](https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry/) - [Glama vs Official MCP Registry](https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry/) - [Composio vs Portkey](https://agentmcpdirectory.com/compare/composio-vs-portkey/) Standards are compared in [the reference entries](https://agentmcpdirectory.com/compare/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/index.md) ## Sources - [Cloudflare home](https://developers.cloudflare.com/agents/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/agents/guides/remote-mcp-server](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026 - [Cloudflare: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.cloudflare.mcp%2Fmcp), read 4 November 2026 - [Vercel home](https://vercel.com/docs/mcp), read 4 November 2026 - [Vercel: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Vercel: vercel.com/docs/agent-resources/vercel-mcp](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 - [Vercel: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.vercel%2Fvercel-mcp), read 4 November 2026 - [Smithery home](https://smithery.ai/), read 4 November 2026 - [Smithery: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=ai.smithery), read 4 November 2026 - [Smithery: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Glama home](https://glama.ai/mcp/servers), read 4 November 2026 - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [Glama: glama.ai/pricing](https://glama.ai/pricing), read 4 November 2026 - [Composio home](https://composio.dev/), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Composio: composio.dev/pricing](https://composio.dev/pricing), read 4 November 2026 - [Composio: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.ComposioHQ%2Fcomposio), read 4 November 2026 - [Zapier MCP home](https://zapier.com/mcp), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Zapier MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.zapier%2Fmcp), read 4 November 2026 - [Official MCP Registry home](https://registry.modelcontextprotocol.io/), read 4 November 2026 - [Official MCP Registry: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [GitHub MCP Registry home](https://github.com/mcp), read 4 November 2026 - [GitHub MCP Registry: api.mcp.github.com/v0/servers](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [GitHub MCP Registry: github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), read 4 November 2026 - [GitHub MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.github%2Fgithub-mcp-server), read 4 November 2026 - [Claude Connectors Directory home](https://claude.com/connectors), read 4 November 2026 - [Claude Connectors Directory: claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 - [Claude Connectors Directory: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.claude.platform%2Fdocs), read 4 November 2026 - [Mintlify MCP home](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Mintlify MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.mintlify), read 4 November 2026 - [Apify MCP home](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Apify MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.apify%2Fapify-mcp-server), read 4 November 2026 - [Browserbase MCP home](https://docs.browserbase.com/integrations/mcp/introduction), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Apify MCP: rubric and evidence | Agent MCP Directory" description: "Apify MCP: Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search." canonical: https://agentmcpdirectory.com/hosts/apify-mcp site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Apify MCP: rubric and evidence | Agent MCP Directory > Apify MCP: Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search. Source: https://agentmcpdirectory.com/hosts/apify-mcp Site: Agent MCP Directory Last reviewed: 2026-11-04 # Apify MCP Apify MCP: Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only. Remote transport: Streamable HTTP and stdio. Price read 4 November 2026: No separate MCP price. ## Fact sheet | Product | Apify MCP | | --- | --- | | Operator | Apify | | Kind | host | | Home | docs.apify.com | | Pricing | No separate MCP price; Actor runs are the billable unit (read 2026-11-04). (source, read 4 November 2026) | | In this directory | Apify: sign-in required, tools not seen, not counted | | Vendor profile | Apify | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | Streamable HTTP and stdio | Per docs, as stated on the source page. | docs.apify.com, read 2026-11-04 | | OAuth with client registration | OAuth | Browser opens on first connection. | docs.apify.com, read 2026-11-04 | | Per-tool auth scoping | tools parameter selects Actors | Full-permission Actors excluded. | docs.apify.com, read 2026-11-04 | | Hosting and scale limits | Actor run limits | Not MCP specific. | docs.apify.com, read 2026-11-04 | | Observability | run status and storage IDs | Through call-actor. | docs.apify.com, read 2026-11-04 | | Pricing | per Actor run | Per docs, as stated on the source page. | docs.apify.com, read 2026-11-04 | | Registry submission | Apify Store for Actors | Actors become tools by name. | docs.apify.com, read 2026-11-04 | | Discoverability by agents | search-actors tool | Agents find Actors at run time. | docs.apify.com, read 2026-11-04 | | Own server in the registries | yes | com.apify/apify-mcp-server active. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not return Actor results from call-actor directly. - Does not expose full-permission Actors to search or execution. ## Dated facts - Hosted endpoint https://mcp.apify.com over Streamable HTTP; a local stdio option runs with npx @apify/actors-mcp-server on Node.js 18+. ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026) - Authentication is OAuth (recommended) or Authorization: Bearer with an APIFY\_TOKEN. ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026) - Without an account, only search-actors, fetch-actor-details, search-apify-docs and fetch-apify-docs may be enabled. ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026) - call-actor returns run status and storage IDs, not results; get-dataset-items reads the output. ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026) - Per-request payments through Skyfire work only with pay-per-event Actors. ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026) - Ora lists apify.com at 96 on its leaderboard (4 Nov 2026 sample). ([ora.ai](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 4 November 2026) ## Compare and alternatives - [Alternatives to Apify MCP](https://agentmcpdirectory.com/hosts/apify-mcp/alternatives/) - [Apify MCP vs Browserbase MCP](https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase/) - [Zapier MCP vs Apify MCP](https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/apify-mcp/index.md) ## Sources - [Apify MCP home](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Apify MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.apify%2Fapify-mcp-server), read 4 November 2026 - [Apify MCP: ora.ai/leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Apify MCP alternatives | Agent MCP Directory" description: "6 alternatives to Apify MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/apify-mcp/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Apify MCP alternatives | Agent MCP Directory > 6 alternatives to Apify MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/apify-mcp/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Apify MCP Apify MCP has 6 alternatives on this directory's rubric: Cloudflare, Vercel, Composio, Zapier MCP, Mintlify MCP, Browserbase MCP. Each entry below states one difference between it and Apify MCP, with the evidence and a source link. Apify MCP is operated by Apify. ## The 6 alternatives ### Cloudflare Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals. Difference on oauth with client registration: Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. [Cloudflare profile](https://agentmcpdirectory.com/hosts/cloudflare/) ### Vercel Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Difference on oauth with client registration: Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. [Vercel profile](https://agentmcpdirectory.com/hosts/vercel/) ### Composio A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Difference on oauth with client registration: Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented. [Composio profile](https://agentmcpdirectory.com/hosts/composio/) ### Zapier MCP Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Difference on oauth with client registration: Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Most clients sign in with OAuth; DCR not stated. [Zapier MCP profile](https://agentmcpdirectory.com/hosts/zapier-mcp/), [Zapier MCP vs Apify MCP](https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp/) ### Mintlify MCP Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files. Difference on oauth with client registration: Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. [Mintlify MCP profile](https://agentmcpdirectory.com/hosts/mintlify-mcp/) ### Browserbase MCP A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string. Difference on oauth with client registration: Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Query parameter auth. [Browserbase MCP profile](https://agentmcpdirectory.com/hosts/browserbase/), [Apify MCP vs Browserbase MCP](https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/apify-mcp/alternatives/index.md) ## Sources - [Apify MCP home](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Mintlify MCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Browserbase MCP: rubric and evidence | Agent MCP Directory" description: "Browserbase MCP: A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key." canonical: https://agentmcpdirectory.com/hosts/browserbase site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Browserbase MCP: rubric and evidence | Agent MCP Directory > Browserbase MCP: A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key. Source: https://agentmcpdirectory.com/hosts/browserbase Site: Agent MCP Directory Last reviewed: 2026-11-04 # Browserbase MCP Browserbase MCP (Browserbase): A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string. Remote transport: Streamable HTTP. Does not offer OAuth on the documented hosted endpoint. Scored on the same rubric as 15 other products. ## Fact sheet | Product | Browserbase MCP | | --- | --- | | Operator | Browserbase | | Kind | host | | Home | docs.browserbase.com | | In this directory | Browserbase: no MCP endpoint on record | | Vendor profile | Browserbase | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | Streamable HTTP | Per docs, as stated on the source page. | docs.browserbase.com, read 2026-11-04 | | OAuth with client registration | no, API key in URL | Query parameter auth. | docs.browserbase.com, read 2026-11-04 | | Per-tool auth scoping | no | Single key, as stated on the source page. | docs.browserbase.com, read 2026-11-04 | | Hosting and scale limits | not stated | Not on MCP pages. | docs.browserbase.com, read 2026-11-04 | | Observability | session lifecycle tools | start and end tools. | docs.browserbase.com, read 2026-11-04 | | Pricing | not stated on MCP pages | Not mentioned. | docs.browserbase.com, read 2026-11-04 | | Registry submission | not a registry | Single server. | docs.browserbase.com, read 2026-11-04 | | Discoverability by agents | docs only | No .well-known noted. | docs.browserbase.com, read 2026-11-04 | | Own server in the registries | listed without remote | Official registry entry has no remote. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not offer OAuth on the documented hosted endpoint. - Puts the API key in the URL, where logs can capture it. ## Dated facts - Hosted endpoint https://mcp.browserbase.com/mcp over Streamable HTTP. ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026) - The API key is passed as the browserbaseApiKey query parameter; the setup page mentions no header or OAuth option. ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026) - Tools are navigate, act, observe, extract, start and end, each with an optional sessionId. ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026) - The server is built on Stagehand. ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/introduction), read 4 November 2026) - io.github.browserbase/mcp-server-browserbase is in the official registry without a remote; a Smithery-hosted copy lists a server.smithery.ai remote. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=browserbase), read 4 November 2026) ## Compare and alternatives - [Alternatives to Browserbase MCP](https://agentmcpdirectory.com/hosts/browserbase/alternatives/) - [Apify MCP vs Browserbase MCP](https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/browserbase/index.md) ## Sources - [Browserbase MCP home](https://docs.browserbase.com/integrations/mcp/introduction), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 - [Browserbase MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=browserbase), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Browserbase MCP alternatives | Agent MCP Directory" description: "6 alternatives to Browserbase MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/browserbase/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Browserbase MCP alternatives | Agent MCP Directory > 6 alternatives to Browserbase MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/browserbase/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Browserbase MCP Browserbase MCP has 6 alternatives on this directory's rubric: Cloudflare, Vercel, Composio, Zapier MCP, Mintlify MCP, Apify MCP. Each entry below states one difference between it and Browserbase MCP, with the evidence and a source link. Browserbase MCP is operated by Browserbase. ## The 6 alternatives ### Cloudflare Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals. Difference on oauth with client registration: Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026); Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. [Cloudflare profile](https://agentmcpdirectory.com/hosts/cloudflare/) ### Vercel Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Difference on oauth with client registration: Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026); Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. [Vercel profile](https://agentmcpdirectory.com/hosts/vercel/) ### Composio A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Difference on oauth with client registration: Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026); Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented. [Composio profile](https://agentmcpdirectory.com/hosts/composio/) ### Zapier MCP Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Difference on oauth with client registration: Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026); Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026). Most clients sign in with OAuth; DCR not stated. [Zapier MCP profile](https://agentmcpdirectory.com/hosts/zapier-mcp/) ### Mintlify MCP Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files. Difference on oauth with client registration: Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026); Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. [Mintlify MCP profile](https://agentmcpdirectory.com/hosts/mintlify-mcp/) ### Apify MCP Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only. Difference on oauth with client registration: Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026); Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026). Browser opens on first connection. [Apify MCP profile](https://agentmcpdirectory.com/hosts/apify-mcp/), [Apify MCP vs Browserbase MCP](https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/browserbase/alternatives/index.md) ## Sources - [Browserbase MCP home](https://docs.browserbase.com/integrations/mcp/introduction), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Mintlify MCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Apify MCP: docs.apify.com/platform/integrations/mcp](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Claude Connectors Directory: rubric | Agent MCP Directory" description: "Claude Connectors Directory: Anthropic's reviewed directory of remote MCP connectors for Claude. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/claude-connectors-directory site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Claude Connectors Directory: rubric | Agent MCP Directory > Claude Connectors Directory: Anthropic's reviewed directory of remote MCP connectors for Claude. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/claude-connectors-directory Site: Agent MCP Directory Last reviewed: 2026-11-04 # Claude Connectors Directory Claude Connectors Directory: Anthropic's reviewed directory of remote MCP connectors for Claude, submitted through a developer portal with required tool annotations and OAuth for user data. Remote transport: remote HTTPS required. Price read 4 November 2026: Submission needs any paid Claude plan (read 2026-11-04). ## Fact sheet | Product | Claude Connectors Directory | | --- | --- | | Operator | Anthropic | | Kind | registry or directory | | Home | claude.com | | Pricing | Submission needs any paid Claude plan (read 2026-11-04). (source, read 4 November 2026) | | Vendor profile | Anthropic | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | remote HTTPS required | Local servers not accepted as connectors. | claude.com, read 2026-11-04 | | OAuth with client registration | OAuth 2.0 required for user data | Anthropic can hold your OAuth client. | claude.com, read 2026-11-04 | | Per-tool auth scoping | annotations required | readOnlyHint or destructiveHint per tool. | claude.com, read 2026-11-04 | | Hosting and scale limits | not a host | Directory only. | claude.com, read 2026-11-04 | | Observability | health and usage metrics after publication | Per the submission page. | claude.com, read 2026-11-04 | | Pricing | paid Claude plan to submit | Per the submission page. | claude.com, read 2026-11-04 | | Registry submission | portal, automated scan, optional human review | Community by default, Verified later. | claude.com, read 2026-11-04 | | Discoverability by agents | inside Claude | Directory at claude.com/connectors. | claude.com, read 2026-11-04 | | Own server in the registries | docs server listed | com.claude.platform/docs is in the official registry. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not list local stdio servers as connectors. - Does not let the submitter edit the card disclaimer. ## Dated facts - The directory listed 1,064 connectors and 528 plugins on 4 Nov 2026. ([claude.com](https://claude.com/connectors), read 4 November 2026) - Submissions must be remote HTTPS servers; local MCPB desktop extensions are no longer accepted and go in plugins instead. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) - Every tool needs a title and a readOnlyHint or destructiveHint annotation; the portal flags tools that lack them. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) - Authenticated services must use OAuth 2.0; public data may use no authentication. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) - After submission Anthropic scans automatically and by default lists the server as a Community connector; some get human review. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) - Anyone on a paid Claude plan can submit through claude.ai/directory/manage. ([claude.com](https://claude.com/docs/connectors/building/submission), read 4 November 2026) ## Compare and alternatives - [Alternatives to Claude Connectors Directory](https://agentmcpdirectory.com/hosts/claude-connectors-directory/alternatives/) - [Official MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory/) - [GitHub MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/claude-connectors-directory/index.md) ## Sources - [Claude Connectors Directory home](https://claude.com/connectors), read 4 November 2026 - [Claude Connectors Directory pricing](https://claude.com/docs/connectors/building/submission), read 4 November 2026 - [Claude Connectors Directory: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.claude.platform%2Fdocs), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Claude Connectors Directory alternatives | Agent MCP Directory" description: "4 alternatives to Claude Connectors Directory for listing MCP servers, each with one sourced difference. Evidence linked on every line." canonical: https://agentmcpdirectory.com/hosts/claude-connectors-directory/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Claude Connectors Directory alternatives | Agent MCP Directory > 4 alternatives to Claude Connectors Directory for listing MCP servers, each with one sourced difference. Evidence linked on every line. Source: https://agentmcpdirectory.com/hosts/claude-connectors-directory/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Claude Connectors Directory Claude Connectors Directory has 4 alternatives on this directory's rubric: Smithery, Glama, Official MCP Registry, GitHub MCP Registry. Each entry below states one difference between it and Claude Connectors Directory, with the evidence and a source link. Claude Connectors Directory is operated by Anthropic. ## The 4 alternatives ### Smithery A public catalog and former hosting platform for MCP servers, acquired by Arcade in August 2026; its MCP Proxy and managed identity features shut down on 31 Oct 2026. Difference on oauth with client registration: Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026); Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026). Managed identity shut down 31 Oct 2026. [Smithery profile](https://agentmcpdirectory.com/hosts/smithery/) ### Glama An MCP directory listing open-source servers and remote connectors with letter grades for license, quality and maintenance, plus hosting and gateway products. Difference on oauth with client registration: Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026); Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026). Connectors can be filtered by OAuth 2.0; Glama does not document DCR itself. [Glama profile](https://agentmcpdirectory.com/hosts/glama/) ### Official MCP Registry The community metaregistry of MCP servers under the modelcontextprotocol project, published to with the mcp-publisher CLI after namespace verification; the pack calls it the Anthropic MCP registry. Difference on oauth with client registration: Official MCP Registry reads "not applicable" ([source](https://github.com/modelcontextprotocol/registry), 4 November 2026); Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026). The registry records metadata, not auth. [Official MCP Registry profile](https://agentmcpdirectory.com/hosts/official-mcp-registry/), [Official MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory/) ### GitHub MCP Registry GitHub's curated MCP catalog with an install button per server, readable through an open API at api.mcp.github.com. Difference on oauth with client registration: GitHub MCP Registry reads "not applicable" ([source](https://github.com/mcp), 4 November 2026); Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026). Catalog only. [GitHub MCP Registry profile](https://agentmcpdirectory.com/hosts/github-mcp-registry/), [GitHub MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/claude-connectors-directory/alternatives/index.md) ## Sources - [Claude Connectors Directory home](https://claude.com/connectors), read 4 November 2026 - [Smithery: smithery.ai](https://smithery.ai/), read 4 November 2026 - [Claude Connectors Directory: claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [Official MCP Registry: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [GitHub MCP Registry: github.com/mcp](https://github.com/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Cloudflare: rubric and evidence | Agent MCP Directory" description: "Cloudflare: Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library. Evidence and sources on every line." canonical: https://agentmcpdirectory.com/hosts/cloudflare site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Cloudflare: rubric and evidence | Agent MCP Directory > Cloudflare: Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library. Evidence and sources on every line. Source: https://agentmcpdirectory.com/hosts/cloudflare Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare Cloudflare: Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals. Remote transport: Streamable HTTP only. Price read 4 November 2026: The remote MCP guide and portal docs state no separate MCP price. ## Fact sheet | Product | Cloudflare (Workers, Agents SDK, MCP server portals) | | --- | --- | | Operator | Cloudflare | | Kind | host | | Home | developers.cloudflare.com | | Pricing | The remote MCP guide and portal docs state no separate MCP price; Workers usage is billed under Workers pricing and the portal page carries no pricing (read 2026-11-04). (source, read 4 November 2026) | | In this directory | Cloudflare: has an open MCP server with tools listed | | Vendor profile | Cloudflare | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | Streamable HTTP only | Product MCP servers retired /sse on 22 Oct 2026; the guide builds Streamable HTTP servers. | developers.cloudflare.com, read 2026-11-04 | | OAuth with client registration | yes, DCR and CIMD | Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. | developers.cloudflare.com, read 2026-11-04 | | Per-tool auth scoping | yes, at the portal | Portals hide, allowlist and alias individual tools; the OAuth provider issues scoped tokens. | developers.cloudflare.com, read 2026-11-04 | | Hosting and scale limits | 80 servers per portal | The portal page states up to 80 MCP servers per portal; Workers limits apply to servers. | developers.cloudflare.com, read 2026-11-04 | | Observability | Access logs, API analytics, Logpush on Enterprise | Portal requests are logged with time, status, server, capability and duration. | developers.cloudflare.com, read 2026-11-04 | | Pricing | not published for MCP | No MCP-specific price on the guide or portal page. | developers.cloudflare.com, read 2026-11-04 | | Registry submission | not a registry | Cloudflare hosts servers; listing happens in the official or other registries. | developers.cloudflare.com, read 2026-11-04 | | Discoverability by agents | portal endpoint, no public catalog | A portal exposes one /mcp endpoint per organisation. | developers.cloudflare.com, read 2026-11-04 | | Own server in the registries | yes | com.cloudflare.mcp/mcp is active in the official registry with a Streamable HTTP remote. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not list or rank third-party MCP servers for the public. - Portals do not accept stdio-only servers. - Portal Logpush is not available below Enterprise. ## Dated facts - The remote MCP guide builds servers with createMcpHandler, which is stateless: each request gets a fresh McpServer from a factory, so no Durable Object or session is needed. ([developers.cloudflare.com](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026) - McpAgent is marked deprecated in the remote MCP guide, with a migration path to MCP SDK v2. ([developers.cloudflare.com](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026) - The authless template deploys with npm create cloudflare@latest using the remote-mcp-authless template and npx wrangler@latest deploy, serving /mcp locally on port 8788. ([developers.cloudflare.com](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026) - Workers OAuth Provider reached v1 on 1 Oct 2026 and splits the authorization server and the MCP resource server into separate Workers that check tokens over a Service Binding; v1 supports both DCR and Client ID Metadata Documents. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), dated 1 October 2026, read 4 November 2026) - Cloudflare product MCP servers stopped serving /sse on 22 Oct 2026; /sse now returns 410 Gone and points to /mcp. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), dated 22 October 2026, read 4 November 2026) - MCP server portals became generally available on 24 Sep 2026 for all Cloudflare customers. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/), dated 24 September 2026, read 4 November 2026) - A portal puts up to 80 remote HTTP MCP servers behind one endpoint, with per-tool hide, allowlist, alias and description overrides, and namespacing as {server\_id}\_{original\_name}. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) - Portals support stateless MCP 2026-07-28 clients and earlier 2025 Streamable HTTP clients; stdio-only servers must be put behind HTTP first. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) - Portal users sign in through Cloudflare Access; upstream servers can use DCR or static OAuth credentials, and machine clients can use Access service tokens. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) - Logpush export of MCP portal logs is limited to Enterprise plans; tool-call analytics are available through the API for 1 to 179 days. ([developers.cloudflare.com](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026) - The Cloudflare API MCP server added step-up authorization on 19 Oct 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), dated 19 October 2026, read 4 November 2026) - Cloudflare publishes its docs MCP server in the official registry as com.cloudflare.mcp/mcp at https://docs.mcp.cloudflare.com/mcp. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=com.cloudflare.mcp%2Fmcp), read 4 November 2026) ## Compare and alternatives - [Alternatives to Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/alternatives/) - [Cloudflare vs Vercel](https://agentmcpdirectory.com/compare/cloudflare-vs-vercel/) - [Cloudflare vs Composio](https://agentmcpdirectory.com/compare/cloudflare-vs-composio/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/cloudflare/index.md) ## Sources - [Cloudflare home](https://developers.cloudflare.com/agents/), read 4 November 2026 - [Cloudflare pricing](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/agents/guides/remote-mcp-server](https://developers.cloudflare.com/agents/guides/remote-mcp-server/), read 4 November 2026 - [Cloudflare: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.cloudflare.mcp%2Fmcp), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Cloudflare AI Gateway: rubric and evidence | Agent MCP Directory" description: "Cloudflare AI Gateway: A proxy in front of model providers with free caching, rate limiting and analytics, optional Unified Billing." canonical: https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Cloudflare AI Gateway: rubric and evidence | Agent MCP Directory > Cloudflare AI Gateway: A proxy in front of model providers with free caching, rate limiting and analytics, optional Unified Billing. Source: https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare AI Gateway Cloudflare AI Gateway (Cloudflare): A proxy in front of model providers with free caching, rate limiting and analytics, optional Unified Billing, and from 3 Nov 2026 required authentication on new gateways. Protocols fronted: model APIs; MCP goes through portals. Price read 4 November 2026: Core free. ## Fact sheet | Product | Cloudflare AI Gateway | | --- | --- | | Operator | Cloudflare | | Kind | AI gateway | | Home | developers.cloudflare.com | | Pricing | Core free; Unified Billing 5 percent on credits; logs per Workers Logs pricing for new gateways (read 2026-11-04). (source, read 4 November 2026) | | In this directory | Cloudflare: has an open MCP server with tools listed | | Vendor profile | Cloudflare | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Protocols fronted | model APIs; MCP goes through portals | MCP traffic is fronted by MCP server portals, a separate product. | developers.cloudflare.com, read 2026-11-04 | | Auth passthrough | BYOK or Unified Billing | Provider keys or Cloudflare credits. | developers.cloudflare.com, read 2026-11-04 | | Caching | yes, free | Core feature. | developers.cloudflare.com, read 2026-11-04 | | Pricing | free core, 5 percent on credits | Dated 2026-11-04. | developers.cloudflare.com, read 2026-11-04 | | Observability | analytics and logs | Workers Logs for new gateways. | developers.cloudflare.com, read 2026-11-04 | ## What it does not do - Does not front MCP servers itself; portals do that. - Does not accept PayPal for Unified Billing. ## Dated facts - Core features (analytics, caching, rate limiting) are free on all plans. ([developers.cloudflare.com](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026) - Unified Billing adds a 5 percent fee on purchased credits; provider inference passes through without markup. ([developers.cloudflare.com](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026) - Gateways created on or after 24 Sep 2026 log through Workers Logs; older gateways keep Legacy Logs (100,000 total on Workers Free, 10,000,000 per gateway on Workers Paid). ([developers.cloudflare.com](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026) - New AI Gateways require authentication from 3 Nov 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-11-03-required-authentication/), dated 3 November 2026, read 4 November 2026) - Model aliases that route across a pool of models shipped on 4 Nov 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-11-04-model-aliases/), dated 4 November 2026, read 4 November 2026) - AI Gateway added payment for inference with Machine Payments on 30 Sep 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-09-30-machine-payments/), dated 30 September 2026, read 4 November 2026) ## Compare and alternatives - [Alternatives to Cloudflare AI Gateway](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/alternatives/) - [Cloudflare AI Gateway vs Vercel AI Gateway](https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway/) - [Portkey vs Cloudflare AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/index.md) ## Sources - [Cloudflare AI Gateway home](https://developers.cloudflare.com/ai-gateway/), read 4 November 2026 - [Cloudflare AI Gateway pricing](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/changelog/post/2026-11-03-required-authentication](https://developers.cloudflare.com/changelog/post/2026-11-03-required-authentication/), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/changelog/post/2026-11-04-model-aliases](https://developers.cloudflare.com/changelog/post/2026-11-04-model-aliases/), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/changelog/post/2026-09-30-machine-payments](https://developers.cloudflare.com/changelog/post/2026-09-30-machine-payments/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Cloudflare AI Gateway alternatives | Agent MCP Directory" description: "3 alternatives to Cloudflare AI Gateway for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Cloudflare AI Gateway alternatives | Agent MCP Directory > 3 alternatives to Cloudflare AI Gateway for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Cloudflare AI Gateway Cloudflare AI Gateway has 3 alternatives on this directory's rubric: Vercel AI Gateway, Portkey, Kong AI Gateway. Each entry below states one difference between it and Cloudflare AI Gateway, with the evidence and a source link. Cloudflare AI Gateway is operated by Cloudflare. ## The 3 alternatives ### Vercel AI Gateway A model gateway that bills at provider list price with no token markup, supports BYOK without a fee, and charges for add-ons such as custom reporting and team-wide ZDR. Difference on protocols fronted: Vercel AI Gateway reads "model APIs" ([source](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), 4 November 2026); Cloudflare AI Gateway reads "model APIs; MCP goes through portals" ([source](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), 4 November 2026). MCP servers are hosted with mcp-handler, not fronted by the gateway. [Vercel AI Gateway profile](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/), [Cloudflare AI Gateway vs Vercel AI Gateway](https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway/) ### Portkey An AI gateway with an MCP Gateway that checks the caller, injects upstream credentials, provisions tools per user and logs every tool call; now sold as Prisma AIRS AI Gateway. Difference on protocols fronted: Portkey reads "model APIs and MCP" ([source](https://portkey.ai/docs/product/mcp-gateway), 4 November 2026); Cloudflare AI Gateway reads "model APIs; MCP goes through portals" ([source](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), 4 November 2026). MCP Gateway and Registry. [Portkey profile](https://agentmcpdirectory.com/hosts/portkey/), [Portkey vs Cloudflare AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway/) ### Kong AI Gateway Kong's AI Gateway 2.x adds an AI MCP Server entity that turns existing APIs into MCP tools, OAuth2 auth strategies for tool calls, semantic caching and OpenTelemetry for MCP and A2A traffic. Difference on protocols fronted: Kong AI Gateway reads "model APIs, MCP, A2A" ([source](https://developer.konghq.com/ai-gateway/), 4 November 2026); Cloudflare AI Gateway reads "model APIs; MCP goes through portals" ([source](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), 4 November 2026). OpenTelemetry covers all three. [Kong AI Gateway profile](https://agentmcpdirectory.com/hosts/kong-ai-gateway/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/alternatives/index.md) ## Sources - [Cloudflare AI Gateway home](https://developers.cloudflare.com/ai-gateway/), read 4 November 2026 - [Vercel AI Gateway: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Portkey: portkey.ai/docs/product/mcp-gateway](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 - [Kong AI Gateway: developer.konghq.com/ai-gateway](https://developer.konghq.com/ai-gateway/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Cloudflare alternatives | Agent MCP Directory" description: "6 alternatives to Cloudflare for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/cloudflare/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Cloudflare alternatives | Agent MCP Directory > 6 alternatives to Cloudflare for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/cloudflare/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Cloudflare Cloudflare has 6 alternatives on this directory's rubric: Vercel, Composio, Zapier MCP, Mintlify MCP, Apify MCP, Browserbase MCP. Each entry below states one difference between it and Cloudflare, with the evidence and a source link. Cloudflare is operated by Cloudflare. ## The 6 alternatives ### Vercel Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Difference on oauth with client registration: Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026); Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. [Vercel profile](https://agentmcpdirectory.com/hosts/vercel/), [Cloudflare vs Vercel](https://agentmcpdirectory.com/compare/cloudflare-vs-vercel/) ### Composio A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Difference on oauth with client registration: Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026); Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented. [Composio profile](https://agentmcpdirectory.com/hosts/composio/), [Cloudflare vs Composio](https://agentmcpdirectory.com/compare/cloudflare-vs-composio/) ### Zapier MCP Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Difference on oauth with client registration: Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026); Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026). Most clients sign in with OAuth; DCR not stated. [Zapier MCP profile](https://agentmcpdirectory.com/hosts/zapier-mcp/) ### Mintlify MCP Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files. Difference on oauth with client registration: Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026); Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. [Mintlify MCP profile](https://agentmcpdirectory.com/hosts/mintlify-mcp/) ### Apify MCP Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only. Difference on oauth with client registration: Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026); Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026). Browser opens on first connection. [Apify MCP profile](https://agentmcpdirectory.com/hosts/apify-mcp/) ### Browserbase MCP A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string. Difference on oauth with client registration: Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026); Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026). Query parameter auth. [Browserbase MCP profile](https://agentmcpdirectory.com/hosts/browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/cloudflare/alternatives/index.md) ## Sources - [Cloudflare home](https://developers.cloudflare.com/agents/), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Mintlify MCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Apify MCP: docs.apify.com/platform/integrations/mcp](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Composio: rubric and evidence | Agent MCP Directory" description: "Composio: A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth. Evidence and sources on every line." canonical: https://agentmcpdirectory.com/hosts/composio site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Composio: rubric and evidence | Agent MCP Directory > Composio: A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth. Evidence and sources on every line. Source: https://agentmcpdirectory.com/hosts/composio Site: Agent MCP Directory Last reviewed: 2026-11-04 # Composio Composio: A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Remote transport: HTTP. Price read 4 November 2026: Hobby 0 USD (100K tool calls a month), Pro 29 USD a month plus overage (0. ## Fact sheet | Product | Composio | | --- | --- | | Operator | Composio | | Kind | tool gateway and host | | Home | composio.dev | | Pricing | Hobby 0 USD (100K tool calls a month), Pro 29 USD a month plus overage (0.0003 USD per tool call), Enterprise custom; read 2026-11-04. (source, read 4 November 2026) | | In this directory | Composio: no MCP endpoint on record | | Vendor profile | Composio | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | HTTP | Server URL plus headers; transport variant not named. | docs.composio.dev, read 2026-11-04 | | OAuth with client registration | Composio holds app OAuth | Users authenticate toolkits through auth configs; DCR not documented. | docs.composio.dev, read 2026-11-04 | | Per-tool auth scoping | yes, allowed_tools | Tool slugs allowlisted per server. | docs.composio.dev, read 2026-11-04 | | Hosting and scale limits | 2,000 to 10,000 requests a minute | Hobby 2,000 and Pro 10,000 requests per minute. | composio.dev, read 2026-11-04 | | Observability | not detailed on these pages | No log feature described in the quickstart. | docs.composio.dev, read 2026-11-04 | | Pricing | 0 / 29 USD / custom | Dated 2026-11-04. | composio.dev, read 2026-11-04 | | Registry submission | not a registry | Composio generates servers; it does not list third parties. | docs.composio.dev, read 2026-11-04 | | Discoverability by agents | session-based tool discovery | The page recommends sessions for dynamic tool access. | docs.composio.dev, read 2026-11-04 | | Own server in the registries | yes | io.github.ComposioHQ/composio active in the official registry. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not host your own MCP server code. - Does not let you build the server URL from a server ID; you must generate it. ## Dated facts - Composio generates a user-specific MCP URL with composio.mcp.generate or POST /api/v3.1/mcp/servers/generate; consumer connections use https://connect.composio.dev/mcp. ([docs.composio.dev](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026) - Requests carry an x-api-key header, required by default for new organisations through require\_mcp\_api\_key. ([docs.composio.dev](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026) - The allowed\_tools parameter restricts a server to listed tool slugs such as GMAIL\_FETCH\_EMAILS. ([docs.composio.dev](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026) - Hobby is free with 100K tool calls a month (up to 20K on Composio-managed apps); Pro is 29 USD a month with tool-call overage at 0.0003 USD per call. ([composio.dev](https://composio.dev/pricing), read 4 November 2026) - New pricing applies to sign-ups from 15 Aug 2026; existing customers keep their plan through 31 Dec 2026. ([composio.dev](https://composio.dev/pricing), dated 15 August 2026, read 4 November 2026) - The quickstart uses both managed\_auth\_via\_composio and managed\_auth\_by\_composio in its examples, an inconsistency worth checking against the API reference. ([docs.composio.dev](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026) - Composio publishes io.github.ComposioHQ/composio in the official registry with remote https://connect.composio.dev/mcp. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.ComposioHQ%2Fcomposio), read 4 November 2026) ## Compare and alternatives - [Alternatives to Composio](https://agentmcpdirectory.com/hosts/composio/alternatives/) - [Composio vs Zapier MCP](https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp/) - [Cloudflare vs Composio](https://agentmcpdirectory.com/compare/cloudflare-vs-composio/) - [Composio vs Portkey](https://agentmcpdirectory.com/compare/composio-vs-portkey/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/composio/index.md) ## Sources - [Composio home](https://composio.dev/), read 4 November 2026 - [Composio pricing](https://composio.dev/pricing), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Composio: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.ComposioHQ%2Fcomposio), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Composio alternatives | Agent MCP Directory" description: "6 alternatives to Composio for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/composio/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Composio alternatives | Agent MCP Directory > 6 alternatives to Composio for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/composio/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Composio Composio has 6 alternatives on this directory's rubric: Cloudflare, Vercel, Zapier MCP, Mintlify MCP, Apify MCP, Browserbase MCP. Each entry below states one difference between it and Composio, with the evidence and a source link. Composio is operated by Composio. ## The 6 alternatives ### Cloudflare Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals. Difference on oauth with client registration: Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026); Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. [Cloudflare profile](https://agentmcpdirectory.com/hosts/cloudflare/), [Cloudflare vs Composio](https://agentmcpdirectory.com/compare/cloudflare-vs-composio/) ### Vercel Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Difference on oauth with client registration: Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026); Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. [Vercel profile](https://agentmcpdirectory.com/hosts/vercel/) ### Zapier MCP Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Difference on oauth with client registration: Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026); Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026). Most clients sign in with OAuth; DCR not stated. [Zapier MCP profile](https://agentmcpdirectory.com/hosts/zapier-mcp/), [Composio vs Zapier MCP](https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp/) ### Mintlify MCP Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files. Difference on oauth with client registration: Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026); Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. [Mintlify MCP profile](https://agentmcpdirectory.com/hosts/mintlify-mcp/) ### Apify MCP Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only. Difference on oauth with client registration: Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026); Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026). Browser opens on first connection. [Apify MCP profile](https://agentmcpdirectory.com/hosts/apify-mcp/) ### Browserbase MCP A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string. Difference on oauth with client registration: Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026); Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026). Query parameter auth. [Browserbase MCP profile](https://agentmcpdirectory.com/hosts/browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/composio/alternatives/index.md) ## Sources - [Composio home](https://composio.dev/), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Mintlify MCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Apify MCP: docs.apify.com/platform/integrations/mcp](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "GitHub MCP Registry: rubric and evidence | Agent MCP Directory" description: "GitHub MCP Registry: GitHub's curated MCP catalog with an install button per server, readable through an open API at api.mcp.github.com." canonical: https://agentmcpdirectory.com/hosts/github-mcp-registry site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # GitHub MCP Registry: rubric and evidence | Agent MCP Directory > GitHub MCP Registry: GitHub's curated MCP catalog with an install button per server, readable through an open API at api.mcp.github.com. Source: https://agentmcpdirectory.com/hosts/github-mcp-registry Site: Agent MCP Directory Last reviewed: 2026-11-04 # GitHub MCP Registry GitHub MCP Registry: GitHub's curated MCP catalog with an install button per server, readable through an open API at api.mcp.github.com. Remote transport: records remotes. Price read 4 November 2026: Free to browse. Does not explain on its listing page how servers are selected. ## Fact sheet | Product | GitHub MCP Registry | | --- | --- | | Operator | GitHub | | Kind | registry or directory | | Home | github.com | | Pricing | Free to browse; the API answered without a key on 2026-11-04. (source, read 4 November 2026) | | In this directory | GitHub: sign-in required, tools not seen, not counted | | Vendor profile | GitHub | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | records remotes | transport_type per remote. | api.mcp.github.com, read 2026-11-04 | | OAuth with client registration | not applicable | Catalog only. | github.com, read 2026-11-04 | | Per-tool auth scoping | not applicable | Catalog only. | github.com, read 2026-11-04 | | Hosting and scale limits | not a host | Catalog only. | github.com, read 2026-11-04 | | Observability | Copilot usage metrics count MCP servers | Since 22 Oct 2026. | github.blog, read 2026-11-04 | | Pricing | free | Open API, as stated on the source page. | api.mcp.github.com, read 2026-11-04 | | Registry submission | not documented on the page | The listing page does not describe submission. | github.com, read 2026-11-04 | | Discoverability by agents | open API and install buttons | api.mcp.github.com/v0/servers. | api.mcp.github.com, read 2026-11-04 | | Own server in the registries | yes | io.github.github/github-mcp-server active in the official registry. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not explain on its listing page how servers are selected. - Lists 773 servers, far fewer than open directories. ## Dated facts - The GitHub MCP Registry showed 773 servers on 4 Nov 2026. ([github.com](https://github.com/mcp), read 4 November 2026) - A full pull of https://api.mcp.github.com/v0/servers on 4 Nov 2026 returned 773 entries, 587 of them with a remote endpoint. ([api.mcp.github.com](https://api.mcp.github.com/v0/servers), read 4 November 2026) - Entries carry an x-github block with display name, homepage, licence, stars and whether the repository belongs to an organisation. ([api.mcp.github.com](https://api.mcp.github.com/v0/servers), read 4 November 2026) - Listed servers include Microsoft Markitdown and Playwright, GitHub, Context7 (Upstash), Supabase, Notion and Tavily. ([github.com](https://github.com/mcp), read 4 November 2026) - GitHub's own server runs remotely at https://api.githubcopilot.com/mcp/ with OAuth or a PAT, and has a --read-only flag that overrides explicitly requested write tools. ([github.com](https://github.com/github/github-mcp-server), read 4 November 2026) - On 22 Oct 2026 GitHub added custom skills, agents and MCP servers to the Copilot usage metrics API. ([github.blog](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), dated 22 October 2026, read 4 November 2026) ## Compare and alternatives - [Alternatives to GitHub MCP Registry](https://agentmcpdirectory.com/hosts/github-mcp-registry/alternatives/) - [Official MCP Registry vs GitHub MCP Registry](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry/) - [GitHub MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/github-mcp-registry/index.md) ## Sources - [GitHub MCP Registry home](https://github.com/mcp), read 4 November 2026 - [GitHub MCP Registry pricing](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [GitHub MCP Registry: github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), read 4 November 2026 - [GitHub MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.github%2Fgithub-mcp-server), read 4 November 2026 - [GitHub MCP Registry: github.com/github/github-mcp-server](https://github.com/github/github-mcp-server), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "GitHub MCP Registry alternatives | Agent MCP Directory" description: "4 alternatives to GitHub MCP Registry for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/github-mcp-registry/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # GitHub MCP Registry alternatives | Agent MCP Directory > 4 alternatives to GitHub MCP Registry for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/github-mcp-registry/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to GitHub MCP Registry GitHub MCP Registry has 4 alternatives on this directory's rubric: Smithery, Glama, Official MCP Registry, Claude Connectors Directory. Each entry below states one difference between it and GitHub MCP Registry, with the evidence and a source link. GitHub MCP Registry is operated by GitHub. ## The 4 alternatives ### Smithery A public catalog and former hosting platform for MCP servers, acquired by Arcade in August 2026; its MCP Proxy and managed identity features shut down on 31 Oct 2026. Difference on oauth with client registration: Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026); GitHub MCP Registry reads "not applicable" ([source](https://github.com/mcp), 4 November 2026). Managed identity shut down 31 Oct 2026. [Smithery profile](https://agentmcpdirectory.com/hosts/smithery/) ### Glama An MCP directory listing open-source servers and remote connectors with letter grades for license, quality and maintenance, plus hosting and gateway products. Difference on oauth with client registration: Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026); GitHub MCP Registry reads "not applicable" ([source](https://github.com/mcp), 4 November 2026). Connectors can be filtered by OAuth 2.0; Glama does not document DCR itself. [Glama profile](https://agentmcpdirectory.com/hosts/glama/) ### Official MCP Registry The community metaregistry of MCP servers under the modelcontextprotocol project, published to with the mcp-publisher CLI after namespace verification; the pack calls it the Anthropic MCP registry. Difference on remote transport: Official MCP Registry reads "records both" ([source](https://registry.modelcontextprotocol.io/v0/servers), 4 November 2026); GitHub MCP Registry reads "records remotes" ([source](https://api.mcp.github.com/v0/servers), 4 November 2026). remotes\[\].type is streamable-http or sse. [Official MCP Registry profile](https://agentmcpdirectory.com/hosts/official-mcp-registry/), [Official MCP Registry vs GitHub MCP Registry](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry/) ### Claude Connectors Directory Anthropic's reviewed directory of remote MCP connectors for Claude, submitted through a developer portal with required tool annotations and OAuth for user data. Difference on oauth with client registration: Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026); GitHub MCP Registry reads "not applicable" ([source](https://github.com/mcp), 4 November 2026). Anthropic can hold your OAuth client. [Claude Connectors Directory profile](https://agentmcpdirectory.com/hosts/claude-connectors-directory/), [GitHub MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/github-mcp-registry-vs-claude-connectors-directory/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/github-mcp-registry/alternatives/index.md) ## Sources - [GitHub MCP Registry home](https://github.com/mcp), read 4 November 2026 - [Smithery: smithery.ai](https://smithery.ai/), read 4 November 2026 - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [Official MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [GitHub MCP Registry: api.mcp.github.com/v0/servers](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [Claude Connectors Directory: claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Glama: rubric and evidence | Agent MCP Directory" description: "Glama: An MCP directory listing open-source servers and remote connectors with letter grades for license. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/glama site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Hosts and registries" --- # Glama: rubric and evidence | Agent MCP Directory > Glama: An MCP directory listing open-source servers and remote connectors with letter grades for license. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/glama Site: Agent MCP Directory Last reviewed: 2026-11-05 # Glama Glama: An MCP directory listing open-source servers and remote connectors with letter grades for license, quality and maintenance, plus hosting and gateway products. Remote transport: lists both. Does not explain how its letter grades are computed on the listing page. ## Fact sheet | Product | Glama | | --- | --- | | Operator | Glama | | Kind | registry or directory | | Home | glama.ai | | Vendor profile | Glama | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | lists both | Directory filters remote, local and hybrid servers. | glama.ai, read 2026-11-04 | | OAuth with client registration | filter only | Connectors can be filtered by OAuth 2.0; Glama does not document DCR itself. | glama.ai, read 2026-11-04 | | Per-tool auth scoping | not documented | No per-tool auth docs found. | glama.ai, read 2026-11-04 | | Hosting and scale limits | not published | Hosting product named without limits. | glama.ai, read 2026-11-04 | | Observability | health status on listings | Connectors show healthy or unhealthy status. | glama.ai, read 2026-11-04 | | Pricing | not detailed | Pricing page carries no MCP plan detail. | glama.ai, read 2026-11-04 | | Registry submission | open, Add Server button | Anyone can add a server. | glama.ai, read 2026-11-04 | | Discoverability by agents | API with key and attribution | API needs a key; records need attribution. | glama.ai, read 2026-11-04 | | Own server in the registries | not found | No Glama namespace in the official registry on 4 Nov 2026. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not explain how its letter grades are computed on the listing page. - Does not offer keyless API access. ## Dated facts - The Glama directory listed 115,804 MCP servers on 4 Nov 2026 at 19:46. ([glama.ai](https://glama.ai/mcp/servers), read 4 November 2026) - The Glama directory counted 116,152 MCP servers on 5 Nov 2026 at 14:34, 348 more than the count of the day before. ([glama.ai](https://glama.ai/mcp/servers), read 5 November 2026) - Glama tags servers by hosting type: 45,531 remote, 43,657 local and 21,761 hybrid on 4 Nov 2026. ([glama.ai](https://glama.ai/mcp/servers), read 4 November 2026) - Each server carries A to F grades for license, quality and maintenance; 10,287 servers were marked claimed. ([glama.ai](https://glama.ai/mcp/servers), read 4 November 2026) - The connectors section listed 40,288 remote MCP servers with filters for No Auth, OAuth 2.0 and health status. ([glama.ai](https://glama.ai/mcp/connectors), read 4 November 2026) - The Glama MCP API returns 401 without an API key, and its data license requires visible attribution and a link to the Glama listing wherever its records are shown. (glama.ai, read 4 November 2026) - Glama navigation lists MCP Hosting and MCP Gateway products; the pricing page says only "Native MCP support with access to 5,000+ servers". ([glama.ai](https://glama.ai/pricing), read 4 November 2026) ## Compare and alternatives - [Alternatives to Glama](https://agentmcpdirectory.com/hosts/glama/alternatives/) - [Smithery vs Glama](https://agentmcpdirectory.com/compare/smithery-vs-glama/) - [Glama vs Official MCP Registry](https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/glama/index.md) ## Sources - [Glama home](https://glama.ai/mcp/servers), read 4 November 2026 - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [Glama: glama.ai/pricing](https://glama.ai/pricing), read 4 November 2026 - [Glama: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Glama alternatives | Agent MCP Directory" description: "4 alternatives to Glama for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/glama/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Glama alternatives | Agent MCP Directory > 4 alternatives to Glama for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/glama/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Glama Glama has 4 alternatives on this directory's rubric: Smithery, Official MCP Registry, GitHub MCP Registry, Claude Connectors Directory. Each entry below states one difference between it and Glama, with the evidence and a source link. Glama is operated by Glama. ## The 4 alternatives ### Smithery A public catalog and former hosting platform for MCP servers, acquired by Arcade in August 2026; its MCP Proxy and managed identity features shut down on 31 Oct 2026. Difference on oauth with client registration: Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026); Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026). Managed identity shut down 31 Oct 2026. [Smithery profile](https://agentmcpdirectory.com/hosts/smithery/), [Smithery vs Glama](https://agentmcpdirectory.com/compare/smithery-vs-glama/) ### Official MCP Registry The community metaregistry of MCP servers under the modelcontextprotocol project, published to with the mcp-publisher CLI after namespace verification; the pack calls it the Anthropic MCP registry. Difference on oauth with client registration: Official MCP Registry reads "not applicable" ([source](https://github.com/modelcontextprotocol/registry), 4 November 2026); Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026). The registry records metadata, not auth. [Official MCP Registry profile](https://agentmcpdirectory.com/hosts/official-mcp-registry/), [Glama vs Official MCP Registry](https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry/) ### GitHub MCP Registry GitHub's curated MCP catalog with an install button per server, readable through an open API at api.mcp.github.com. Difference on oauth with client registration: GitHub MCP Registry reads "not applicable" ([source](https://github.com/mcp), 4 November 2026); Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026). Catalog only. [GitHub MCP Registry profile](https://agentmcpdirectory.com/hosts/github-mcp-registry/) ### Claude Connectors Directory Anthropic's reviewed directory of remote MCP connectors for Claude, submitted through a developer portal with required tool annotations and OAuth for user data. Difference on oauth with client registration: Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026); Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026). Anthropic can hold your OAuth client. [Claude Connectors Directory profile](https://agentmcpdirectory.com/hosts/claude-connectors-directory/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/glama/alternatives/index.md) ## Sources - [Glama home](https://glama.ai/mcp/servers), read 4 November 2026 - [Smithery: smithery.ai](https://smithery.ai/), read 4 November 2026 - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [Official MCP Registry: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [GitHub MCP Registry: github.com/mcp](https://github.com/mcp), read 4 November 2026 - [Claude Connectors Directory: claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Kong AI Gateway: rubric and evidence | Agent MCP Directory" description: "Kong AI Gateway: Kong's AI Gateway 2.x adds an AI MCP Server entity that turns existing APIs into MCP tools. Evidence and sources on every line." canonical: https://agentmcpdirectory.com/hosts/kong-ai-gateway site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Kong AI Gateway: rubric and evidence | Agent MCP Directory > Kong AI Gateway: Kong's AI Gateway 2.x adds an AI MCP Server entity that turns existing APIs into MCP tools. Evidence and sources on every line. Source: https://agentmcpdirectory.com/hosts/kong-ai-gateway Site: Agent MCP Directory Last reviewed: 2026-11-04 # Kong AI Gateway Kong AI Gateway: Kong's AI Gateway 2.x adds an AI MCP Server entity that turns existing APIs into MCP tools, OAuth2 auth strategies for tool calls, semantic caching and OpenTelemetry for MCP and A2A traffic. Protocols fronted: model APIs, MCP, A2A. ## Fact sheet | Product | Kong AI Gateway | | --- | --- | | Operator | Kong | | Kind | AI gateway | | Home | developer.konghq.com | | In this directory | Kong: sign-in required, tools not seen, not counted | | Vendor profile | Kong | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Protocols fronted | model APIs, MCP, A2A | OpenTelemetry covers all three. | developer.konghq.com, read 2026-11-04 | | Auth passthrough | OAuth2 auth strategies | Per tool call. | developer.konghq.com, read 2026-11-04 | | Caching | semantic cache | AI Semantic Cache policy. | developer.konghq.com, read 2026-11-04 | | Pricing | not published on the docs page | Konnect licensing, no prices. | developer.konghq.com, read 2026-11-04 | | Observability | OpenTelemetry, Konnect dashboards, audit logs | Per docs, as stated on the source page. | developer.konghq.com, read 2026-11-04 | ## What it does not do - The AI Gateway page does not publish prices or edition differences. - Does not name its MCP plugins on the overview page. ## Dated facts - The AI MCP Server entity turns existing APIs into tools that agents discover and call over MCP. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) - AI Auth Strategies can apply OAuth2 to agent tool calls so write actions can need tighter access than reads. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) - The AI Semantic Cache policy serves repeated or near-duplicate prompts from cache. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) - OpenTelemetry output covers per-request spans and aggregated metrics for AI, MCP and A2A traffic. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) - AI Gateway 2.x replaces the v1 AI Proxy and AI Proxy Advanced plugins with entities such as AI Model and AI Model Provider; the page lists a minimum version of 2.0. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) - Kong publishes com.konghq/konnect in the official registry with remotes at global.mcp.konghq.com and regional hosts. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=com.konghq%2Fkonnect), read 4 November 2026) ## Compare and alternatives - [Alternatives to Kong AI Gateway](https://agentmcpdirectory.com/hosts/kong-ai-gateway/alternatives/) - [Portkey vs Kong AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/kong-ai-gateway/index.md) ## Sources - [Kong AI Gateway home](https://developer.konghq.com/ai-gateway/), read 4 November 2026 - [Kong AI Gateway: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.konghq%2Fkonnect), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Kong AI Gateway alternatives | Agent MCP Directory" description: "3 alternatives to Kong AI Gateway for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/kong-ai-gateway/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Kong AI Gateway alternatives | Agent MCP Directory > 3 alternatives to Kong AI Gateway for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/kong-ai-gateway/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Kong AI Gateway Kong AI Gateway has 3 alternatives on this directory's rubric: Cloudflare AI Gateway, Vercel AI Gateway, Portkey. Each entry below states one difference between it and Kong AI Gateway, with the evidence and a source link. Kong AI Gateway is operated by Kong. ## The 3 alternatives ### Cloudflare AI Gateway A proxy in front of model providers with free caching, rate limiting and analytics, optional Unified Billing, and from 3 Nov 2026 required authentication on new gateways. Difference on protocols fronted: Cloudflare AI Gateway reads "model APIs; MCP goes through portals" ([source](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), 4 November 2026); Kong AI Gateway reads "model APIs, MCP, A2A" ([source](https://developer.konghq.com/ai-gateway/), 4 November 2026). MCP traffic is fronted by MCP server portals, a separate product. [Cloudflare AI Gateway profile](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/) ### Vercel AI Gateway A model gateway that bills at provider list price with no token markup, supports BYOK without a fee, and charges for add-ons such as custom reporting and team-wide ZDR. Difference on protocols fronted: Vercel AI Gateway reads "model APIs" ([source](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), 4 November 2026); Kong AI Gateway reads "model APIs, MCP, A2A" ([source](https://developer.konghq.com/ai-gateway/), 4 November 2026). MCP servers are hosted with mcp-handler, not fronted by the gateway. [Vercel AI Gateway profile](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/) ### Portkey An AI gateway with an MCP Gateway that checks the caller, injects upstream credentials, provisions tools per user and logs every tool call; now sold as Prisma AIRS AI Gateway. Difference on protocols fronted: Portkey reads "model APIs and MCP" ([source](https://portkey.ai/docs/product/mcp-gateway), 4 November 2026); Kong AI Gateway reads "model APIs, MCP, A2A" ([source](https://developer.konghq.com/ai-gateway/), 4 November 2026). MCP Gateway and Registry. [Portkey profile](https://agentmcpdirectory.com/hosts/portkey/), [Portkey vs Kong AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/kong-ai-gateway/alternatives/index.md) ## Sources - [Kong AI Gateway home](https://developer.konghq.com/ai-gateway/), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Vercel AI Gateway: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [Portkey: portkey.ai/docs/product/mcp-gateway](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Mintlify MCP: rubric and evidence | Agent MCP Directory" description: "Mintlify MCP: Generates a search MCP server for every Mintlify docs site at /mcp. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/mintlify-mcp site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Mintlify MCP: rubric and evidence | Agent MCP Directory > Mintlify MCP: Generates a search MCP server for every Mintlify docs site at /mcp. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/mintlify-mcp Site: Agent MCP Directory Last reviewed: 2026-11-04 # Mintlify MCP Mintlify MCP: Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files. Remote transport: Streamable HTTP. Does not generate tools from an OpenAPI file on this page. Scored on the same rubric as 15 other products. ## Fact sheet | Product | Mintlify MCP | | --- | --- | | Operator | Mintlify | | Kind | host | | Home | www.mintlify.com | | In this directory | Mintlify: has an open MCP server with tools listed | | Vendor profile | Mintlify | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | Streamable HTTP | Hosted at /mcp. | www.mintlify.com, read 2026-11-04 | | OAuth with client registration | client credentials at /authed/mcp/oauth/token | Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. | www.mintlify.com, read 2026-11-04 | | Per-tool auth scoping | public versus authed endpoints | User-group scoped content on /authed/mcp. | www.mintlify.com, read 2026-11-04 | | Hosting and scale limits | published rate limits | 5,000 to 10,000 per hour. | www.mintlify.com, read 2026-11-04 | | Observability | not detailed | Not on this page. | www.mintlify.com, read 2026-11-04 | | Pricing | MCP included; WebMCP Pro or Enterprise | Plan note for WebMCP only. | www.mintlify.com, read 2026-11-04 | | Registry submission | not a registry | Docs host, as stated on the source page. | www.mintlify.com, read 2026-11-04 | | Discoverability by agents | four .well-known discovery files | Listed on the docs page. | www.mintlify.com, read 2026-11-04 | | Own server in the registries | yes | com.mintlify/searchmcp active. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not generate tools from an OpenAPI file on this page. - Does not host arbitrary MCP server code. ## Dated facts - Mintlify hosts an auto-generated search MCP server at /mcp on the docs site URL; sites with authentication also get /authed/mcp. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) - Core tools are search, query docs filesystem and submit feedback; skill.md files are exposed as MCP resources. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) - Rate limits: 5,000 requests per hour per user IP, 10,000 per hour per site for search and filesystem calls, 5,000 per hour for authenticated calls; excess returns HTTP 429. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) - Mintlify publishes discovery files at /.well-known/mcp, /.well-known/mcp.json, /.well-known/mcp/server-card.json and /.well-known/mcp/server-cards.json. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) - WebMCP tools (search\_docs, read\_page, get\_site\_overview, read\_skill, navigate\_page) need a Pro or Enterprise plan. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) - The Mintlify docs page contains text addressed to agents asking them to send feedback to a Mintlify endpoint; this crawl did not act on it. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) - Mintlify lists com.mintlify/searchmcp and com.mintlify/adminmcp in the official registry. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=com.mintlify), read 4 November 2026) ## Compare and alternatives - [Alternatives to Mintlify MCP](https://agentmcpdirectory.com/hosts/mintlify-mcp/alternatives/) - [Vercel vs Mintlify MCP](https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/mintlify-mcp/index.md) ## Sources - [Mintlify MCP home](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Mintlify MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.mintlify), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Mintlify MCP alternatives | Agent MCP Directory" description: "6 alternatives to Mintlify MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/mintlify-mcp/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Mintlify MCP alternatives | Agent MCP Directory > 6 alternatives to Mintlify MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/mintlify-mcp/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Mintlify MCP Mintlify MCP has 6 alternatives on this directory's rubric: Cloudflare, Vercel, Composio, Zapier MCP, Apify MCP, Browserbase MCP. Each entry below states one difference between it and Mintlify MCP, with the evidence and a source link. Mintlify MCP is operated by Mintlify. ## The 6 alternatives ### Cloudflare Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals. Difference on oauth with client registration: Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026); Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. [Cloudflare profile](https://agentmcpdirectory.com/hosts/cloudflare/) ### Vercel Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Difference on oauth with client registration: Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026); Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. [Vercel profile](https://agentmcpdirectory.com/hosts/vercel/), [Vercel vs Mintlify MCP](https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp/) ### Composio A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Difference on oauth with client registration: Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026); Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented. [Composio profile](https://agentmcpdirectory.com/hosts/composio/) ### Zapier MCP Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Difference on oauth with client registration: Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026); Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026). Most clients sign in with OAuth; DCR not stated. [Zapier MCP profile](https://agentmcpdirectory.com/hosts/zapier-mcp/) ### Apify MCP Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only. Difference on oauth with client registration: Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026); Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026). Browser opens on first connection. [Apify MCP profile](https://agentmcpdirectory.com/hosts/apify-mcp/) ### Browserbase MCP A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string. Difference on oauth with client registration: Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026); Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026). Query parameter auth. [Browserbase MCP profile](https://agentmcpdirectory.com/hosts/browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/mintlify-mcp/alternatives/index.md) ## Sources - [Mintlify MCP home](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Apify MCP: docs.apify.com/platform/integrations/mcp](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Official MCP Registry: rubric and evidence | Agent MCP Directory" description: "Official MCP Registry: The community metaregistry of MCP servers under the modelcontextprotocol project. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/official-mcp-registry site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Official MCP Registry: rubric and evidence | Agent MCP Directory > Official MCP Registry: The community metaregistry of MCP servers under the modelcontextprotocol project. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/official-mcp-registry Site: Agent MCP Directory Last reviewed: 2026-11-04 # Official MCP Registry Official MCP Registry (MCP Registry Working Group): The community metaregistry of MCP servers under the modelcontextprotocol project, published to with the mcp-publisher CLI after namespace verification; the pack calls it the Anthropic MCP registry. Remote transport: records both. Price read 4 November 2026: Free to publish and read (read 2026-11-04). ## Fact sheet | Product | Official MCP Registry (registry.modelcontextprotocol.io) | | --- | --- | | Operator | MCP Registry Working Group | | Kind | registry or directory | | Home | registry.modelcontextprotocol.io | | Pricing | Free to publish and read (read 2026-11-04). (source, read 4 November 2026) | | Vendor profile | Official MCP Registry | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | records both | remotes[].type is streamable-http or sse. | registry.modelcontextprotocol.io, read 2026-11-04 | | OAuth with client registration | not applicable | The registry records metadata, not auth. | github.com, read 2026-11-04 | | Per-tool auth scoping | not applicable | No tool lists stored. | registry.modelcontextprotocol.io, read 2026-11-04 | | Hosting and scale limits | not a host | Metadata only. | github.com, read 2026-11-04 | | Observability | not applicable | Metadata only. | github.com, read 2026-11-04 | | Pricing | free | Open API, as stated on the source page. | github.com, read 2026-11-04 | | Registry submission | CLI with namespace verification | mcp-publisher plus GitHub, DNS or HTTP proof. | github.com, read 2026-11-04 | | Discoverability by agents | open paginated API | GET /v0/servers with cursor, no key. | registry.modelcontextprotocol.io, read 2026-11-04 | | Own server in the registries | not applicable | The registry is the directory. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not verify that a listed endpoint works or what its tools do. - Does not rank or grade servers. - Is still a preview; data resets are possible. ## Dated facts - The registry launched in preview on 8 Sep 2025 and its API entered a v0.1 freeze on 24 Oct 2025; v1 is planned for GA. ([github.com](https://github.com/modelcontextprotocol/registry), dated 8 September 2025, read 4 November 2026) - Publishing uses the mcp-publisher CLI, not a pull request; adding a server.json to the repo does not list a server. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) - Namespaces are verified by GitHub OAuth, GitHub OIDC from Actions, DNS or HTTP; io.github./ needs that GitHub login and reverse-DNS names need domain proof. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) - A full GET of /v0/servers with version=latest on 4 Nov 2026 returned 56,677 entries: 55,806 active and 871 deprecated. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026) - 37,977 of those entries declare at least one remote: 37,751 streamable-http remotes and 1,127 sse remotes. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026) - Entries carry the 2025-12-11 server.json schema, with remotes, packages, websiteUrl and repository fields. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026) - The registry does not grade servers; status is limited to active or deprecated in the official \_meta block. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026) ## Compare and alternatives - [Alternatives to Official MCP Registry](https://agentmcpdirectory.com/hosts/official-mcp-registry/alternatives/) - [Official MCP Registry vs GitHub MCP Registry](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry/) - [Official MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory/) - [Smithery vs Official MCP Registry](https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry/) - [Glama vs Official MCP Registry](https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/official-mcp-registry/index.md) ## Sources - [Official MCP Registry home](https://registry.modelcontextprotocol.io/), read 4 November 2026 - [Official MCP Registry pricing](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [Official MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Official MCP Registry alternatives | Agent MCP Directory" description: "4 alternatives to Official MCP Registry for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/official-mcp-registry/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Official MCP Registry alternatives | Agent MCP Directory > 4 alternatives to Official MCP Registry for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/official-mcp-registry/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Official MCP Registry Official MCP Registry has 4 alternatives on this directory's rubric: Smithery, Glama, GitHub MCP Registry, Claude Connectors Directory. Each entry below states one difference between it and Official MCP Registry, with the evidence and a source link. Official MCP Registry is operated by MCP Registry Working Group. ## The 4 alternatives ### Smithery A public catalog and former hosting platform for MCP servers, acquired by Arcade in August 2026; its MCP Proxy and managed identity features shut down on 31 Oct 2026. Difference on oauth with client registration: Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026); Official MCP Registry reads "not applicable" ([source](https://github.com/modelcontextprotocol/registry), 4 November 2026). Managed identity shut down 31 Oct 2026. [Smithery profile](https://agentmcpdirectory.com/hosts/smithery/), [Smithery vs Official MCP Registry](https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry/) ### Glama An MCP directory listing open-source servers and remote connectors with letter grades for license, quality and maintenance, plus hosting and gateway products. Difference on oauth with client registration: Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026); Official MCP Registry reads "not applicable" ([source](https://github.com/modelcontextprotocol/registry), 4 November 2026). Connectors can be filtered by OAuth 2.0; Glama does not document DCR itself. [Glama profile](https://agentmcpdirectory.com/hosts/glama/), [Glama vs Official MCP Registry](https://agentmcpdirectory.com/compare/glama-vs-official-mcp-registry/) ### GitHub MCP Registry GitHub's curated MCP catalog with an install button per server, readable through an open API at api.mcp.github.com. Difference on remote transport: GitHub MCP Registry reads "records remotes" ([source](https://api.mcp.github.com/v0/servers), 4 November 2026); Official MCP Registry reads "records both" ([source](https://registry.modelcontextprotocol.io/v0/servers), 4 November 2026). transport\_type per remote. [GitHub MCP Registry profile](https://agentmcpdirectory.com/hosts/github-mcp-registry/), [Official MCP Registry vs GitHub MCP Registry](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-github-mcp-registry/) ### Claude Connectors Directory Anthropic's reviewed directory of remote MCP connectors for Claude, submitted through a developer portal with required tool annotations and OAuth for user data. Difference on oauth with client registration: Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026); Official MCP Registry reads "not applicable" ([source](https://github.com/modelcontextprotocol/registry), 4 November 2026). Anthropic can hold your OAuth client. [Claude Connectors Directory profile](https://agentmcpdirectory.com/hosts/claude-connectors-directory/), [Official MCP Registry vs Claude Connectors Directory](https://agentmcpdirectory.com/compare/official-mcp-registry-vs-claude-connectors-directory/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/official-mcp-registry/alternatives/index.md) ## Sources - [Official MCP Registry home](https://registry.modelcontextprotocol.io/), read 4 November 2026 - [Smithery: smithery.ai](https://smithery.ai/), read 4 November 2026 - [Official MCP Registry: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [GitHub MCP Registry: api.mcp.github.com/v0/servers](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [Official MCP Registry: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Claude Connectors Directory: claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Portkey: rubric and evidence | Agent MCP Directory" description: "Portkey: An AI gateway with an MCP Gateway that checks the caller, injects upstream credentials. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/portkey site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Portkey: rubric and evidence | Agent MCP Directory > Portkey: An AI gateway with an MCP Gateway that checks the caller, injects upstream credentials. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/portkey Site: Agent MCP Directory Last reviewed: 2026-11-04 # Portkey Portkey (Portkey, now offered as Palo Alto Networks Prisma AIRS AI Gateway): An AI gateway with an MCP Gateway that checks the caller, injects upstream credentials, provisions tools per user and logs every tool call; now sold as Prisma AIRS AI Gateway. ## Fact sheet | Product | Portkey (Prisma AIRS AI Gateway) | | --- | --- | | Operator | Portkey, now offered as Palo Alto Networks Prisma AIRS AI Gateway | | Kind | AI gateway | | Home | portkey.ai | | Pricing | Developer free (10K logs a month), Production 49 USD a month (100K logs), Enterprise custom; read 2026-11-04. (source, read 4 November 2026) | | Vendor profile | Portkey | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Protocols fronted | model APIs and MCP | MCP Gateway and Registry. | portkey.ai, read 2026-11-04 | | Auth passthrough | credential injection | Caller checked, upstream credentials injected. | portkey.ai, read 2026-11-04 | | Caching | simple cache, 1-day TTL on Developer | Pricing page. | portkey.ai, read 2026-11-04 | | Pricing | free / 49 USD / custom | Dated 2026-11-04. | portkey.ai, read 2026-11-04 | | Observability | per tool call logs | User, parameters, response. | portkey.ai, read 2026-11-04 | ## What it does not do - The MCP Gateway page does not mention caching of tool results. - Does not publish an acquisition date on its home page. ## Dated facts - The Portkey home page says Portkey is now Prisma AIRS AI Gateway, generally available for enterprises. ([portkey.ai](https://portkey.ai/), read 4 November 2026) - The MCP Gateway checks the caller's Portkey API key or IdP token, then injects upstream credentials (OAuth, API keys or custom headers). ([portkey.ai](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026) - Tool Provisioning enables or disables specific tools for each user. ([portkey.ai](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026) - Every tool call is logged with user, parameters and response, filterable by server, user or time. ([portkey.ai](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026) - Developer is free with 10K recorded logs a month; Production is 49 USD a month with 100K logs and 9 USD per extra 100K. ([portkey.ai](https://portkey.ai/pricing), read 4 November 2026) - Requests past the log cap still go through; only the logs are not recorded. ([portkey.ai](https://portkey.ai/pricing), read 4 November 2026) ## Compare and alternatives - [Alternatives to Portkey](https://agentmcpdirectory.com/hosts/portkey/alternatives/) - [Portkey vs Kong AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway/) - [Portkey vs Cloudflare AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway/) - [Composio vs Portkey](https://agentmcpdirectory.com/compare/composio-vs-portkey/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/portkey/index.md) ## Sources - [Portkey home](https://portkey.ai/), read 4 November 2026 - [Portkey pricing](https://portkey.ai/pricing), read 4 November 2026 - [Portkey: portkey.ai/docs/product/mcp-gateway](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Portkey alternatives | Agent MCP Directory" description: "3 alternatives to Portkey for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/portkey/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Portkey alternatives | Agent MCP Directory > 3 alternatives to Portkey for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/portkey/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Portkey Portkey has 3 alternatives on this directory's rubric: Cloudflare AI Gateway, Vercel AI Gateway, Kong AI Gateway. Each entry below states one difference between it and Portkey, with the evidence and a source link. Portkey is operated by Portkey, now offered as Palo Alto Networks Prisma AIRS AI Gateway. ## The 3 alternatives ### Cloudflare AI Gateway A proxy in front of model providers with free caching, rate limiting and analytics, optional Unified Billing, and from 3 Nov 2026 required authentication on new gateways. Difference on protocols fronted: Cloudflare AI Gateway reads "model APIs; MCP goes through portals" ([source](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), 4 November 2026); Portkey reads "model APIs and MCP" ([source](https://portkey.ai/docs/product/mcp-gateway), 4 November 2026). MCP traffic is fronted by MCP server portals, a separate product. [Cloudflare AI Gateway profile](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/), [Portkey vs Cloudflare AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-cloudflare-ai-gateway/) ### Vercel AI Gateway A model gateway that bills at provider list price with no token markup, supports BYOK without a fee, and charges for add-ons such as custom reporting and team-wide ZDR. Difference on protocols fronted: Vercel AI Gateway reads "model APIs" ([source](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), 4 November 2026); Portkey reads "model APIs and MCP" ([source](https://portkey.ai/docs/product/mcp-gateway), 4 November 2026). MCP servers are hosted with mcp-handler, not fronted by the gateway. [Vercel AI Gateway profile](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/) ### Kong AI Gateway Kong's AI Gateway 2.x adds an AI MCP Server entity that turns existing APIs into MCP tools, OAuth2 auth strategies for tool calls, semantic caching and OpenTelemetry for MCP and A2A traffic. Difference on protocols fronted: Kong AI Gateway reads "model APIs, MCP, A2A" ([source](https://developer.konghq.com/ai-gateway/), 4 November 2026); Portkey reads "model APIs and MCP" ([source](https://portkey.ai/docs/product/mcp-gateway), 4 November 2026). OpenTelemetry covers all three. [Kong AI Gateway profile](https://agentmcpdirectory.com/hosts/kong-ai-gateway/), [Portkey vs Kong AI Gateway](https://agentmcpdirectory.com/compare/portkey-vs-kong-ai-gateway/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/portkey/alternatives/index.md) ## Sources - [Portkey home](https://portkey.ai/), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Portkey: portkey.ai/docs/product/mcp-gateway](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 - [Vercel AI Gateway: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [Kong AI Gateway: developer.konghq.com/ai-gateway](https://developer.konghq.com/ai-gateway/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Smithery: rubric and evidence | Agent MCP Directory" description: "Smithery: A public catalog and former hosting platform for MCP servers, acquired by Arcade in August 2026. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/smithery site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Smithery: rubric and evidence | Agent MCP Directory > Smithery: A public catalog and former hosting platform for MCP servers, acquired by Arcade in August 2026. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/smithery Site: Agent MCP Directory Last reviewed: 2026-11-04 # Smithery Smithery (Arcade (acquired Smithery, Aug 2026)): A public catalog and former hosting platform for MCP servers, acquired by Arcade in August 2026; its MCP Proxy and managed identity features shut down on 31 Oct 2026. Remote transport: Streamable HTTP (registry entries). ## Fact sheet | Product | Smithery | | --- | --- | | Operator | Arcade (acquired Smithery, Aug 2026) | | Kind | registry or directory | | Home | smithery.ai | | Pricing | No pricing page: smithery.ai/pricing returned 404 on 2026-11-04; the home page links to Arcade sign-up. (source, read 4 November 2026) | | Vendor profile | Arcade | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | Streamable HTTP (registry entries) | ai.smithery registry entries list streamable-http remotes on server.smithery.ai. | registry.modelcontextprotocol.io, read 2026-11-04 | | OAuth with client registration | managed identity retired | Managed identity shut down 31 Oct 2026. | smithery.ai, read 2026-11-04 | | Per-tool auth scoping | not documented | No current docs page found on 4 Nov 2026. | smithery.ai, read 2026-11-04 | | Hosting and scale limits | proxy retired | MCP Proxy shut down 31 Oct 2026. | smithery.ai, read 2026-11-04 | | Observability | not documented | No current docs page found. | smithery.ai, read 2026-11-04 | | Pricing | not published | Pricing URL returns 404. | smithery.ai, read 2026-11-04 | | Registry submission | unclear after acquisition | Listing URLs 404 and the search API errors. | smithery.ai, read 2026-11-04 | | Discoverability by agents | catalog browse only | The home page shows a browse list. | smithery.ai, read 2026-11-04 | | Own server in the registries | no own server found | No smithery.ai namespace entry for Smithery itself. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - No longer proxies MCP connections or manages identity (since 31 Oct 2026). - Does not publish a price list. ## Dated facts - Arcade announced on 5 Aug 2026 that it acquired Smithery, which it describes as a public registry and hosting platform for MCP. ([www.arcade.dev](https://www.arcade.dev/blog/smithery-joins-arcade), dated 5 August 2026, read 4 November 2026) - The smithery.ai home page on 4 Nov 2026 says Smithery is now part of Arcade and that the MCP Proxy and managed identity features shut down on October 31. ([smithery.ai](https://smithery.ai/), dated 31 October 2026, read 4 November 2026) - The official MCP Registry holds 213 active entries under the ai.smithery namespace whose remotes point at server.smithery.ai. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=ai.smithery), read 4 November 2026) - Former Smithery listing URLs such as smithery.ai/servers/eralabs-ai/ora returned 404 on 4 Nov 2026. ([smithery.ai](https://smithery.ai/), read 4 November 2026) - The Smithery registry search endpoint registry.smithery.ai/servers returned an error to an unauthenticated GET on 4 Nov 2026. ([smithery.ai](https://smithery.ai/), read 4 November 2026) ## Compare and alternatives - [Alternatives to Smithery](https://agentmcpdirectory.com/hosts/smithery/alternatives/) - [Smithery vs Glama](https://agentmcpdirectory.com/compare/smithery-vs-glama/) - [Smithery vs Official MCP Registry](https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/smithery/index.md) ## Sources - [Smithery home](https://smithery.ai/), read 4 November 2026 - [Smithery: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=ai.smithery), read 4 November 2026 - [Smithery: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [Smithery: www.arcade.dev/blog/smithery-joins-arcade](https://www.arcade.dev/blog/smithery-joins-arcade), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Smithery alternatives | Agent MCP Directory" description: "4 alternatives to Smithery for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/smithery/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Smithery alternatives | Agent MCP Directory > 4 alternatives to Smithery for listing MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/smithery/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Smithery Smithery has 4 alternatives on this directory's rubric: Glama, Official MCP Registry, GitHub MCP Registry, Claude Connectors Directory. Each entry below states one difference between it and Smithery, with the evidence and a source link. Smithery is operated by Arcade (acquired Smithery, Aug 2026). ## The 4 alternatives ### Glama An MCP directory listing open-source servers and remote connectors with letter grades for license, quality and maintenance, plus hosting and gateway products. Difference on oauth with client registration: Glama reads "filter only" ([source](https://glama.ai/mcp/connectors), 4 November 2026); Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026). Connectors can be filtered by OAuth 2.0; Glama does not document DCR itself. [Glama profile](https://agentmcpdirectory.com/hosts/glama/), [Smithery vs Glama](https://agentmcpdirectory.com/compare/smithery-vs-glama/) ### Official MCP Registry The community metaregistry of MCP servers under the modelcontextprotocol project, published to with the mcp-publisher CLI after namespace verification; the pack calls it the Anthropic MCP registry. Difference on oauth with client registration: Official MCP Registry reads "not applicable" ([source](https://github.com/modelcontextprotocol/registry), 4 November 2026); Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026). The registry records metadata, not auth. [Official MCP Registry profile](https://agentmcpdirectory.com/hosts/official-mcp-registry/), [Smithery vs Official MCP Registry](https://agentmcpdirectory.com/compare/smithery-vs-official-mcp-registry/) ### GitHub MCP Registry GitHub's curated MCP catalog with an install button per server, readable through an open API at api.mcp.github.com. Difference on oauth with client registration: GitHub MCP Registry reads "not applicable" ([source](https://github.com/mcp), 4 November 2026); Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026). Catalog only. [GitHub MCP Registry profile](https://agentmcpdirectory.com/hosts/github-mcp-registry/) ### Claude Connectors Directory Anthropic's reviewed directory of remote MCP connectors for Claude, submitted through a developer portal with required tool annotations and OAuth for user data. Difference on oauth with client registration: Claude Connectors Directory reads "OAuth 2.0 required for user data" ([source](https://claude.com/docs/connectors/building/submission), 4 November 2026); Smithery reads "managed identity retired" ([source](https://smithery.ai/), 4 November 2026). Anthropic can hold your OAuth client. [Claude Connectors Directory profile](https://agentmcpdirectory.com/hosts/claude-connectors-directory/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/smithery/alternatives/index.md) ## Sources - [Smithery home](https://smithery.ai/), read 4 November 2026 - [Glama: glama.ai/mcp/connectors](https://glama.ai/mcp/connectors), read 4 November 2026 - [Official MCP Registry: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 - [GitHub MCP Registry: github.com/mcp](https://github.com/mcp), read 4 November 2026 - [Claude Connectors Directory: claude.com/docs/connectors/building/submission](https://claude.com/docs/connectors/building/submission), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Vercel: rubric and evidence | Agent MCP Directory" description: "Vercel: Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/vercel site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Vercel: rubric and evidence | Agent MCP Directory > Vercel: Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/vercel Site: Agent MCP Directory Last reviewed: 2026-11-04 # Vercel Vercel: Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Remote transport: Streamable HTTP only. Price read 4 November 2026: Vercel MCP is available on all plans. ## Fact sheet | Product | Vercel (mcp-handler, Vercel MCP) | | --- | --- | | Operator | Vercel | | Kind | host | | Home | vercel.com | | Pricing | Vercel MCP is available on all plans; self-hosted servers bill as Vercel Functions on Fluid compute (read 2026-11-04). (source, read 4 November 2026) | | In this directory | Vercel: sign-in required, tools not seen, not counted | | Vendor profile | Vercel | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | Streamable HTTP only | mcp-handler v2 removed HTTP+SSE. | vercel.com, read 2026-11-04 | | OAuth with client registration | bring your own AS; CIMD on Vercel MCP | mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. | vercel.com, read 2026-11-04 | | Per-tool auth scoping | scopes per handler | requiredScopes on withMcpAuth; per-tool scoping is left to the server code. | vercel.com, read 2026-11-04 | | Hosting and scale limits | Vercel Functions limits | The guide points to Functions and Fluid compute; no MCP-specific limit stated. | vercel.com, read 2026-11-04 | | Observability | platform logs, rollbacks, rolling releases | The guide lists Instant Rollback, Deployment Protection, Firewall and Rolling Releases. | vercel.com, read 2026-11-04 | | Pricing | Functions pricing | No separate MCP charge stated. | vercel.com, read 2026-11-04 | | Registry submission | not a registry | Vercel hosts; listing happens elsewhere. | vercel.com, read 2026-11-04 | | Discoverability by agents | none built in | The guide links public lists on GitHub rather than a Vercel catalog. | vercel.com, read 2026-11-04 | | Own server in the registries | yes | com.vercel/vercel-mcp is active in the official registry. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - mcp-handler does not run an authorization server or issue tokens. - Does not offer a public MCP registry or directory. ## Dated facts - The deploy guide installs mcp-handler@2.1.1 with @modelcontextprotocol/server@2 and zod@4, and needs Node.js 20 or later. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - mcp-handler v2 removes the legacy HTTP+SSE transport and the Redis configuration; clients connect over Streamable HTTP at a framework route such as /api/mcp. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - withMcpAuth wraps a handler with token verification and returns 401 without a valid token and 403 when a scope is missing; the package does not issue tokens or run an authorization server. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - protectedResourceHandler serves /.well-known/oauth-protected-resource metadata pointing at an external authorization server. ([vercel.com](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026) - Vercel MCP is a remote server with OAuth at https://mcp.vercel.com, available on all plans. ([vercel.com](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026) - Since 2 Nov 2026 any MCP client can connect to Vercel MCP with a Client ID Metadata Document instead of a prior review; the consent screen shows the metadata hostname. ([vercel.com](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), dated 2 November 2026, read 4 November 2026) - The supported-clients list names 14 clients, including Claude Code, ChatGPT, Codex CLI, Cursor, VS Code with Copilot, Devin, Goose, Windsurf, Gemini CLI, OpenCode and Pi. ([vercel.com](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026) - Vercel publishes its server in the official registry as com.vercel/vercel-mcp at https://mcp.vercel.com. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=com.vercel%2Fvercel-mcp), read 4 November 2026) ## Compare and alternatives - [Alternatives to Vercel](https://agentmcpdirectory.com/hosts/vercel/alternatives/) - [Cloudflare vs Vercel](https://agentmcpdirectory.com/compare/cloudflare-vs-vercel/) - [Vercel vs Mintlify MCP](https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/vercel/index.md) ## Sources - [Vercel home](https://vercel.com/docs/mcp), read 4 November 2026 - [Vercel pricing](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 - [Vercel: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Vercel: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.vercel%2Fvercel-mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Vercel AI Gateway: rubric and evidence | Agent MCP Directory" description: "Vercel AI Gateway: A model gateway that bills at provider list price with no token markup, supports BYOK without a fee. Evidence and sources on every line." canonical: https://agentmcpdirectory.com/hosts/vercel-ai-gateway site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Vercel AI Gateway: rubric and evidence | Agent MCP Directory > Vercel AI Gateway: A model gateway that bills at provider list price with no token markup, supports BYOK without a fee. Evidence and sources on every line. Source: https://agentmcpdirectory.com/hosts/vercel-ai-gateway Site: Agent MCP Directory Last reviewed: 2026-11-04 # Vercel AI Gateway Vercel AI Gateway (Vercel): A model gateway that bills at provider list price with no token markup, supports BYOK without a fee, and charges for add-ons such as custom reporting and team-wide ZDR. Protocols fronted: model APIs. Price read 4 November 2026: Provider list price, no markup. ## Fact sheet | Product | Vercel AI Gateway | | --- | --- | | Operator | Vercel | | Kind | AI gateway | | Home | vercel.com | | Pricing | Provider list price, no markup; add-ons from 0.075 USD per 1,000 writes; read 2026-11-04. (source, read 4 November 2026) | | In this directory | Vercel: sign-in required, tools not seen, not counted | | Vendor profile | Vercel | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Protocols fronted | model APIs | MCP servers are hosted with mcp-handler, not fronted by the gateway. | vercel.com, read 2026-11-04 | | Auth passthrough | BYOK with system fallback | Fallback billed to credits. | vercel.com, read 2026-11-04 | | Caching | not on the pricing page | Not stated, as stated on the source page. | vercel.com, read 2026-11-04 | | Pricing | no markup, paid add-ons | Dated 2026-11-04. | vercel.com, read 2026-11-04 | | Observability | budgets, reporting, trace drains | Paid add-ons. | vercel.com, read 2026-11-04 | ## What it does not do - Does not proxy MCP tool calls. - BYOK spend is excluded from gateway budgets. ## Dated facts - AI Gateway charges no markup and no platform fee on tokens; BYOK carries no fee but needs purchased credits. ([vercel.com](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026) - The free tier covers a subset of models with lower per-model rate limits and returns 429 when exceeded. ([vercel.com](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026) - When a BYOK request fails, the gateway retries with system credentials and bills that fallback to the credits balance. ([vercel.com](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026) - Custom Reporting costs 0.075 USD per 1,000 tag writes and 5 USD per 1,000 queries. ([vercel.com](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026) - Team-wide zero data retention and the team-wide provider allowlist each cost 0.10 USD per 1,000 requests. ([vercel.com](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026) - Trace Drains bill 0.05 USD per 1,000 traces and 0.50 USD per GB of egress on Pro and Enterprise. ([vercel.com](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026) ## Compare and alternatives - [Alternatives to Vercel AI Gateway](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/alternatives/) - [Cloudflare AI Gateway vs Vercel AI Gateway](https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/index.md) ## Sources - [Vercel AI Gateway home](https://vercel.com/docs/ai-gateway), read 4 November 2026 - [Vercel AI Gateway pricing](https://vercel.com/docs/ai-gateway/pricing), read 4 November 2026 - [Vercel AI Gateway: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Vercel AI Gateway alternatives | Agent MCP Directory" description: "3 alternatives to Vercel AI Gateway for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/vercel-ai-gateway/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Vercel AI Gateway alternatives | Agent MCP Directory > 3 alternatives to Vercel AI Gateway for fronting agent traffic, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/vercel-ai-gateway/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Vercel AI Gateway Vercel AI Gateway has 3 alternatives on this directory's rubric: Cloudflare AI Gateway, Portkey, Kong AI Gateway. Each entry below states one difference between it and Vercel AI Gateway, with the evidence and a source link. Vercel AI Gateway is operated by Vercel. ## The 3 alternatives ### Cloudflare AI Gateway A proxy in front of model providers with free caching, rate limiting and analytics, optional Unified Billing, and from 3 Nov 2026 required authentication on new gateways. Difference on protocols fronted: Cloudflare AI Gateway reads "model APIs; MCP goes through portals" ([source](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), 4 November 2026); Vercel AI Gateway reads "model APIs" ([source](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), 4 November 2026). MCP traffic is fronted by MCP server portals, a separate product. [Cloudflare AI Gateway profile](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/), [Cloudflare AI Gateway vs Vercel AI Gateway](https://agentmcpdirectory.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway/) ### Portkey An AI gateway with an MCP Gateway that checks the caller, injects upstream credentials, provisions tools per user and logs every tool call; now sold as Prisma AIRS AI Gateway. Difference on protocols fronted: Portkey reads "model APIs and MCP" ([source](https://portkey.ai/docs/product/mcp-gateway), 4 November 2026); Vercel AI Gateway reads "model APIs" ([source](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), 4 November 2026). MCP Gateway and Registry. [Portkey profile](https://agentmcpdirectory.com/hosts/portkey/) ### Kong AI Gateway Kong's AI Gateway 2.x adds an AI MCP Server entity that turns existing APIs into MCP tools, OAuth2 auth strategies for tool calls, semantic caching and OpenTelemetry for MCP and A2A traffic. Difference on protocols fronted: Kong AI Gateway reads "model APIs, MCP, A2A" ([source](https://developer.konghq.com/ai-gateway/), 4 November 2026); Vercel AI Gateway reads "model APIs" ([source](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), 4 November 2026). OpenTelemetry covers all three. [Kong AI Gateway profile](https://agentmcpdirectory.com/hosts/kong-ai-gateway/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/alternatives/index.md) ## Sources - [Vercel AI Gateway home](https://vercel.com/docs/ai-gateway), read 4 November 2026 - [Cloudflare AI Gateway: developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals](https://developers.cloudflare.com/cloudflare-one/access-controls/ai-controls/mcp-portals/), read 4 November 2026 - [Vercel AI Gateway: vercel.com/docs/mcp/deploy-mcp-servers-to-vercel](https://vercel.com/docs/mcp/deploy-mcp-servers-to-vercel), read 4 November 2026 - [Portkey: portkey.ai/docs/product/mcp-gateway](https://portkey.ai/docs/product/mcp-gateway), read 4 November 2026 - [Kong AI Gateway: developer.konghq.com/ai-gateway](https://developer.konghq.com/ai-gateway/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Vercel alternatives | Agent MCP Directory" description: "6 alternatives to Vercel for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/vercel/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Vercel alternatives | Agent MCP Directory > 6 alternatives to Vercel for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/vercel/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Vercel Vercel has 6 alternatives on this directory's rubric: Cloudflare, Composio, Zapier MCP, Mintlify MCP, Apify MCP, Browserbase MCP. Each entry below states one difference between it and Vercel, with the evidence and a source link. Vercel is operated by Vercel. ## The 6 alternatives ### Cloudflare Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals. Difference on oauth with client registration: Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026); Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. [Cloudflare profile](https://agentmcpdirectory.com/hosts/cloudflare/), [Cloudflare vs Vercel](https://agentmcpdirectory.com/compare/cloudflare-vs-vercel/) ### Composio A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Difference on oauth with client registration: Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026); Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented. [Composio profile](https://agentmcpdirectory.com/hosts/composio/) ### Zapier MCP Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Difference on oauth with client registration: Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026); Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026). Most clients sign in with OAuth; DCR not stated. [Zapier MCP profile](https://agentmcpdirectory.com/hosts/zapier-mcp/) ### Mintlify MCP Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files. Difference on oauth with client registration: Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026); Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. [Mintlify MCP profile](https://agentmcpdirectory.com/hosts/mintlify-mcp/), [Vercel vs Mintlify MCP](https://agentmcpdirectory.com/compare/vercel-vs-mintlify-mcp/) ### Apify MCP Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only. Difference on oauth with client registration: Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026); Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026). Browser opens on first connection. [Apify MCP profile](https://agentmcpdirectory.com/hosts/apify-mcp/) ### Browserbase MCP A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string. Difference on oauth with client registration: Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026); Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026). Query parameter auth. [Browserbase MCP profile](https://agentmcpdirectory.com/hosts/browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/vercel/alternatives/index.md) ## Sources - [Vercel home](https://vercel.com/docs/mcp), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Mintlify MCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Apify MCP: docs.apify.com/platform/integrations/mcp](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Zapier MCP: rubric and evidence | Agent MCP Directory" description: "Zapier MCP: Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com. Scored on the published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/zapier-mcp site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Zapier MCP: rubric and evidence | Agent MCP Directory > Zapier MCP: Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com. Scored on the published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/zapier-mcp Site: Agent MCP Directory Last reviewed: 2026-11-04 # Zapier MCP Zapier MCP: Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Remote transport: Streamable HTTP only. Price read 4 November 2026: Included in every Zapier plan. ## Fact sheet | Product | Zapier MCP | | --- | --- | | Operator | Zapier | | Kind | tool gateway and host | | Home | zapier.com | | Pricing | Included in every Zapier plan; each tool call uses two tasks (read 2026-11-04). (source, read 4 November 2026) | | In this directory | Zapier: sign-in required, tools not seen, not counted | | Vendor profile | Zapier | ## Rubric | Dimension | Value | Evidence | Source | | --- | --- | --- | --- | | Remote transport | Streamable HTTP only | SSE not supported. | docs.zapier.com, read 2026-11-04 | | OAuth with client registration | OAuth for clients | Most clients sign in with OAuth; DCR not stated. | docs.zapier.com, read 2026-11-04 | | Per-tool auth scoping | yes, app and action level | Admins control access per app and action. | zapier.com, read 2026-11-04 | | Hosting and scale limits | task quota | Two tasks per call. | docs.zapier.com, read 2026-11-04 | | Observability | History log of every MCP action | Product page. | zapier.com, read 2026-11-04 | | Pricing | included, tasks per call | Two tasks per call. | zapier.com, read 2026-11-04 | | Registry submission | not a registry | Zapier exposes its own actions. | docs.zapier.com, read 2026-11-04 | | Discoverability by agents | agentic mode | The AI finds actions mid-conversation. | docs.zapier.com, read 2026-11-04 | | Own server in the registries | yes | com.zapier/mcp in the official registry. | registry.modelcontextprotocol.io, read 2026-11-04 | ## What it does not do - Does not host custom MCP server code. - Does not support SSE clients. - Sharing a server needs a Team or Enterprise plan. ## Dated facts - Zapier MCP connects clients such as Claude, ChatGPT, Cursor and VS Code to 9,000+ apps and over 40,000 actions. ([docs.zapier.com](https://docs.zapier.com/mcp/home), read 4 November 2026) - The product page cites 66,000+ triggers and actions while the developer FAQ cites 30,000+ actions, so Zapier's own action count is inconsistent. ([zapier.com](https://zapier.com/mcp), read 4 November 2026) - Each successful tool call uses two tasks from the plan quota; failed calls do not count. ([docs.zapier.com](https://docs.zapier.com/mcp/home), read 4 November 2026) - Clients must support Streamable HTTP; SSE is not supported. ([docs.zapier.com](https://docs.zapier.com/mcp/home), read 4 November 2026) - Authentication is OAuth or an API key or secret URL; most clients sign in with OAuth. ([docs.zapier.com](https://docs.zapier.com/mcp/home), read 4 November 2026) - Agentic mode lets the AI find and add actions during a conversation; managed mode fixes the action set. ([docs.zapier.com](https://docs.zapier.com/mcp/home), read 4 November 2026) - Next Gen Zaps are free during early access until billing starts on 1 Dec 2026. ([zapier.com](https://zapier.com/mcp), dated 1 December 2026, read 4 November 2026) - Zapier lists com.zapier/mcp in the official registry with remote https://mcp.zapier.com/api/v1/connect. ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=com.zapier%2Fmcp), read 4 November 2026) ## Compare and alternatives - [Alternatives to Zapier MCP](https://agentmcpdirectory.com/hosts/zapier-mcp/alternatives/) - [Composio vs Zapier MCP](https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp/) - [Zapier MCP vs Apify MCP](https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/zapier-mcp/index.md) ## Sources - [Zapier MCP home](https://zapier.com/mcp), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Zapier MCP: registry.modelcontextprotocol.io/v0/servers](https://registry.modelcontextprotocol.io/v0/servers?search=com.zapier%2Fmcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Zapier MCP alternatives | Agent MCP Directory" description: "6 alternatives to Zapier MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/zapier-mcp/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Zapier MCP alternatives | Agent MCP Directory > 6 alternatives to Zapier MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/zapier-mcp/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Zapier MCP Zapier MCP has 6 alternatives on this directory's rubric: Cloudflare, Vercel, Composio, Mintlify MCP, Apify MCP, Browserbase MCP. Each entry below states one difference between it and Zapier MCP, with the evidence and a source link. Zapier MCP is operated by Zapier. ## The 6 alternatives ### Cloudflare Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals. Difference on oauth with client registration: Cloudflare reads "yes, DCR and CIMD" ([source](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026); Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. [Cloudflare profile](https://agentmcpdirectory.com/hosts/cloudflare/) ### Vercel Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Difference on oauth with client registration: Vercel reads "bring your own AS; CIMD on Vercel MCP" ([source](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026); Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. [Vercel profile](https://agentmcpdirectory.com/hosts/vercel/) ### Composio A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Difference on oauth with client registration: Composio reads "Composio holds app OAuth" ([source](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026); Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented. [Composio profile](https://agentmcpdirectory.com/hosts/composio/), [Composio vs Zapier MCP](https://agentmcpdirectory.com/compare/composio-vs-zapier-mcp/) ### Mintlify MCP Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files. Difference on oauth with client registration: Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" ([source](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026); Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. [Mintlify MCP profile](https://agentmcpdirectory.com/hosts/mintlify-mcp/) ### Apify MCP Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only. Difference on oauth with client registration: Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026); Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026). Browser opens on first connection. [Apify MCP profile](https://agentmcpdirectory.com/hosts/apify-mcp/), [Zapier MCP vs Apify MCP](https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-mcp/) ### Browserbase MCP A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string. Difference on oauth with client registration: Browserbase MCP reads "no, API key in URL" ([source](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026); Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026). Query parameter auth. [Browserbase MCP profile](https://agentmcpdirectory.com/hosts/browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/zapier-mcp/alternatives/index.md) ## Sources - [Zapier MCP home](https://zapier.com/mcp), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Mintlify MCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Apify MCP: docs.apify.com/platform/integrations/mcp](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "The 28 checks Ora runs on an MCP server | Agent MCP Directory" description: "The 28 checks Ora runs on an MCP server, by layer, tier and points: 14 where a server is found, 4 for MCP Apps and 10 for every scan." canonical: https://agentmcpdirectory.com/mcp-checks site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Testing" --- # The 28 checks Ora runs on an MCP server | Agent MCP Directory > The 28 checks Ora runs on an MCP server, by layer, tier and points: 14 where a server is found, 4 for MCP Apps and 10 for every scan. Source: https://agentmcpdirectory.com/mcp-checks Site: Agent MCP Directory Last reviewed: 2026-11-05 # The 28 checks Ora runs on an MCP server Ora's public catalog lists 132 checks, and 28 apply to an MCP server URL: 14 only where Ora finds a server, 4 only to MCP Apps and 10 to every scan, by the catalog's applicability field. Read from GET /api/checks, contract 1.38.0, on 5 November 2026. The 28 checks that apply to an MCP server URL or an MCP App, by Ora layer, from GET /api/checks on 5 November 2026. 19 sit in Usability, the layer that asks whether an agent can use the product. | Layer | MCP checks | Of Ora's checks in the layer | | --- | --- | --- | | Discovery | 7 | 16 | | Access | 2 | 42 | | Usability | 19 | 68 | ## Checks for MCP servers only 14 checks apply only when Ora finds an MCP server, and 12 of them are bonus checks: they add credit when passed and drop out of the denominator when not. The catalog descriptions of tool descriptions, parameter schemas, tool listing and auth mechanism say a docs server and a product server are graded differently. | Check | Layer | Tier | Points | Counts as | Maturity | What it tests | | --- | --- | --- | --- | --- | --- | --- | | MCP tool descriptions mcp-tool-descriptions | Usability | Recommended | 3 | bonus | verified | Grades the description of every tool, with a different bar for product and docs servers. | | MCP parameter schemas mcp-param-schemas | Usability | Recommended | 2 | bonus | verified | Typed parameter schemas; product servers need required-field lists and docs servers at least a query. | | MCP server identity mcp-server-identity | Usability | Recommended | 1 | bonus | verified | The legacy handshake returns a name, a version and usage instructions. | | MCP tool listing mcp-tool-listing | Usability | Recommended | 3 | bonus | verified | tools/list returns tools; product servers earn on breadth and docs servers on focus. | | MCP tool naming mcp-tool-naming | Usability | Recommended | 2 | bonus | verified | Predictable tool names such as create_invoice or search_docs. | | MCP auth mechanism mcp-auth-mechanism | Usability | Recommended | 2 | bonus | verified | Docs servers should be public and product servers should require OAuth; the check compares the two. | | MCP OAuth metadata mcp-oauth-metadata | Usability | Recommended | 2 | bonus | verified | Standard OAuth metadata (RFC 8414) so an agent can find the sign-in flow by itself. | | MCP PKCE S256 support mcp-pkce-s256 | Usability | Recommended | 2 | bonus | verified | PKCE with the S256 method in the OAuth flow. | | MCP error handling mcp-error-handling | Usability | Recommended | 2 | bonus | verified | A bad request gets a structured error an agent can correct from. | | MCP modern transport mcp-transport-modern | Usability | Recommended | 1 | bonus | verified | The server speaks Streamable HTTP, not only the legacy transport. | | MCP tool annotations mcp-tool-annotations | Usability | Recommended | 2 | bonus | verified | readOnlyHint and destructiveHint labels that separate safe tools from ones that change data. | | MCP server-card.json mcp-server-card | Usability | Recommended | 2 | bonus | verified | A server card at the server URL plus /server-card, or listed in /.well-known/ai-catalog.json. | | MCP resources exposed mcp-resource-listing | Usability | Recommended | 3 | base | verified | A server that claims resources returns some from resources/list. | | MCP resource quality mcp-resource-quality | Usability | Recommended | 3 | base | verified | Declared resources read: a valid type and non-empty content. | ## Checks for MCP Apps only 4 checks apply only to an MCP App, a server that ships interactive UI into hosts such as ChatGPT and Claude. Ora marks the MCP Apps support check as not applicable for pure API and data services. | Check | Layer | Tier | Points | Counts as | Maturity | What it tests | | --- | --- | --- | --- | --- | --- | --- | | MCP Apps support mcp-app-registry | Usability | Recommended | 4 | base | verified | Whether the server exposes any MCP App, the interactive UI inside ChatGPT and Claude. | | MCP Apps UI quality mcp-apps-ui-quality | Usability | Recommended | 4 | bonus | verified | The App's UI uses the right MIME type, valid HTML, dark mode and no hardcoded secrets. | | MCP App view reachable mcp-view-domain | Usability | Recommended | 4 | base | verified | The App's view loads publicly and serves HTML with no auth wall. | | MCP App view CSP mcp-view-csp | Usability | Recommended | 4 | base | verified | The App's view declares a content security policy that names specific origins, or none. | ## Checks that apply to every scan 10 checks carry `all` in the catalog's `applicability` field, so they run on a domain scan and on an MCP server scan alike: the discovery catalogs, the registry listings and the check that an MCP server exists at all. Ora's other field, `appliesTo`, names domain, MCP and MCP App for all 28 checks on this page, so the field to read is `applicability`. | Check | Layer | Tier | Points | Counts as | Maturity | What it tests | | --- | --- | --- | --- | --- | --- | --- | | ARD discovery ard-catalog | Discovery | Required | 1 | base | verified | An Agentic Resource Discovery catalog at /.well-known/ard.json or linked from the home page. | | AI Catalog discovery ai-catalog-published | Discovery | Recommended | 1 | bonus | verified | A valid AI Catalog at /.well-known/ai-catalog.json. | | ARD entry validity ard-entries-valid | Discovery | Recommended | 2 | bonus | verified | Each catalog entry has an identifier, a name, a media type and a working target. | | ARD trust manifest ard-trust-manifest | Discovery | Recommended | 2 | bonus | verified | Trust signals in the catalog such as verified identity or signatures. | | Listed in MCP registries mcp-registry-listed | Discovery | Recommended | 1 | base | verified | An entry for the domain in the official MCP Registry or Smithery, or a package that runs as an MCP server. | | Listed on skills.sh skills-sh-listed | Access | Emerging | 1 | base | emerging | Official skills published on skills.sh. | | Registry branding registry-branding | Discovery | Emerging | 2 | base | emerging | The registry entry has a display name, an icon and a description. | | ChatGPT app listed chatgpt-app-listed | Discovery | Recommended | 2 | bonus | verified | A listing in the ChatGPT app directory. | | Skills.sh skill quality skills-sh-quality | Access | Emerging | 2 | base | emerging | Skills on skills.sh worth installing: several, well named and adopted. | | MCP server / manifest mcp-server | Usability | Required | 6 | base | verified | A Model Context Protocol server or manifest exists at all; the check with the most points. | ## How to read the columns - Tier is Required, Recommended or Emerging. Ora says the tier is a display label that never changes the score ([Ora llms.txt](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset)). - Maturity is verified or emerging. Verified checks count toward the score; emerging checks are shown but excluded until adoption proves them out ([Ora llms.txt](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset)). 25 of the 28 MCP checks are verified. - A bonus check earns credit when present and is left out of the denominator when it is not, so a server is never marked down for it ([Ora API reference](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset)). - Points are each check's `maxScore`. Ora normalises the four layers, weighted 20, 30, 40 and 10, to 100 ([Ora API reference](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset)). Where to go next: [why Ora is the pick for testing an MCP server](https://agentmcpdirectory.com/test-your-mcp-server/), [Ora's own server and its tools](https://agentmcpdirectory.com/ora-mcp-server/) and [how to publish a server card](https://agentmcpdirectory.com/guides/publish-an-mcp-server-card/). ## Testing your own MCP server [Why Ora is the pick for testing an MCP server, where it falls short and what else exists](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/mcp-checks/index.md) ## Sources - [Ora check catalog, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 5 November 2026 - [Ora llms.txt](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 5 November 2026 - [Ora API reference (llms-full.txt)](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Method: how a server is verified | Agent MCP Directory" description: "How the directory verifies an MCP server by connecting: the status words, the read-only method allowlist, the host rubric." canonical: https://agentmcpdirectory.com/method site: "Agent MCP Directory" last_updated: 2026-11-05 section: "About" --- # Method: how a server is verified | Agent MCP Directory > How the directory verifies an MCP server by connecting: the status words, the read-only method allowlist, the host rubric. Source: https://agentmcpdirectory.com/method Site: Agent MCP Directory Last reviewed: 2026-11-05 # Method A read-only connector tries each endpoint, records what answers and never calls a tool. A server counts only if the connector lists its tools; a sign-in challenge is shown separately and not counted. This page gives the status words, the six allowed methods, the host rubric, the crawl slice and the limits of the data. ## What counts as an MCP server | Status | Companies | Counted | Rule | | --- | --- | --- | --- | | Verified | 263 | yes | The endpoint answered a handshake with no credentials and listed its tools. | | Sign-in required | 533 | no | Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list. | | Credential wall | 19 | no | The endpoint asked for credentials and published no OAuth metadata, so it cannot be told apart from any other protected API. Not counted as an MCP server. | | No answer | 47 | no | A source lists an endpoint, but it did not answer an MCP handshake on the day. Not counted. | | No tools listed | 2 | no | The endpoint completed the handshake and listed no tools. Not counted. | | None found | 472 | no | No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to. | Only a server whose tools the connector listed counts as having an MCP server: 263 of 1,336. A sign-in challenge is its own state, "sign-in required, tools not seen, not counted" (533 rows), because the connector never signs in and so confirmed nothing behind it. A credential wall without OAuth metadata is not counted either, because the same answer comes from any protected API. 472 rows have no endpoint on record, so nothing was connected for them; the other 864 were tried and 852 answered at all (the rest failed before any HTTP answer). "With neither" in the count line means no counted MCP server and no CLI on record: 1,044 companies. Counting OpenAPI as well, 952 companies have none of the three. ## How the connector checks 1. Take the endpoint a source lists. For Developer Tools and Infrastructure rows with no listed endpoint whose `mcp.` subdomain resolved in DNS, the seed script added `mcp./mcp` as a guess; a row that listed tools is labelled "endpoint found by subdomain guess, verified by connecting", and a row that only answered with a sign-in challenge is labelled "endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified". No other row without an endpoint was guessed, and a row with no endpoint is not connected at all. 2. Open a Streamable HTTP session with protocol revision 2026-07-28, fall back to 2025-11-25, then to the legacy SSE transport. Time out after 15 seconds. 3. If the server answers 401 or 403, read the `WWW-Authenticate` header and the OAuth metadata at the protected resource and authorization server paths. Record the auth type: none, API key, OAuth with client registration, or OAuth without. Stop there. 4. If the server answers without credentials, list tools, resources and prompts. Record the counts and up to 40 tool names. 5. Write a log line for every connection with the time, the methods sent, the result and the duration. The entry page shows it. ## The allowlist of methods | Method | Why it is allowed | | --- | --- | | initialize | Opens the session on servers that still use the handshake of the 2025-11-25 revision. | | notifications/initialized | Tells the server the client is ready; a notification, it reads nothing. | | tools/list | Reads the tool names and counts. The names are recorded; no tool is called. | | resources/list | Reads the resource count. | | prompts/list | Reads the prompt count. | | ping | Checks the connection is alive. | The connector never sends `tools/call`, `resources/read`, `prompts/get` or any method that acts. A method outside the allowlist throws before any request leaves, and a test asserts the list. The 2026-07-28 revision replaces `initialize` with `server/discover`, which is also read-only; it joins the allowlist from the next run, and servers on the new revision were reached through the fallback in this edition. The connector's source and its test are in the repository. ## The host and registry rubric | Remote transport | Which remote transports the product serves or lists: Streamable HTTP, or the deprecated HTTP+SSE. | | --- | --- | | OAuth with client registration | Whether an agent can sign in without a human creating an app first: dynamic client registration or client ID metadata documents. | | Per-tool auth scoping | Whether access can be limited tool by tool, not only for the server as a whole. | | Hosting and scale limits | Limits the vendor publishes on servers, calls, size or concurrency. | | Observability | What logs, analytics or health checks the owner of a server gets. | | Pricing | The published price, with the date it was read. | | Registry submission | How a server gets listed and whether the listing is verified. | | Discoverability by agents | Whether an agent can find servers through the product, by a public catalog or an API. | | Own server in the registries | Whether the vendor's own MCP server is listed where agents look, checked against the official registry. | AI gateways are scored on five lines of their own: protocols fronted, auth passthrough, caching, pricing, observability. Every cell carries the evidence, a source link and the date read. A cell changes only with a source. [See the scores](https://agentmcpdirectory.com/hosts/). ## The crawl slice The census and the WebMCP, A2A and OpenAPI columns come from the shared crawl of 4 November 2026: 13,071 domains, last request 2026-11-04 20:16 UTC. 830 directory companies are in it. The slicing script, `scripts/slice-crawl.mjs`, and a test that recomputes a headline number are in the repository. [The census](https://agentmcpdirectory.com/census/) gives the rules for counting a file as found. ## Ora on this layer Ora's public check catalog (GET /api/checks, contract 1.38.0, read 5 November 2026) lists 132 checks in four layers: Discovery 16, Access 42, Usability 68 and Payments 6, weighted 20, 30, 40 and 10 points of 100. Usability is the layer closest to this directory: whether an agent can use what it finds, through an MCP server or a CLI, an API with OpenAPI, and sign-in an agent can finish. The Usability count was 62 when this directory first read Ora's methodology on 4 November 2026 and is 68 in the catalog read on 5 November 2026, a reminder that Ora's checks move. These are Ora's published figures, not this directory's. 28 of the 132 checks apply to an MCP server URL. Ora is the check this directory recommends for testing a server; [the reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/) are on their own page, and [the 28 checks](https://agentmcpdirectory.com/mcp-checks/) are listed. Ora's Journey runs a real agent against a domain with an intent such as finding pricing and records every step, stall and outcome, which is the check for whether the surfaces listed here work in practice. The Ora score column in the directory is Ora's own cached score for each company's domain, read on 5 November 2026: 323 through GET /api/score/{domain} and 610 from the same day's GET /api/leaderboard, with no scan triggered and a blank cell where Ora has none. Ora is also a row in the directory like every other company, verified the same way; [its MCP server and tools](https://agentmcpdirectory.com/ora-mcp-server/). To check your own site, run Ora's scan at [ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=method) or `npx ax audit yourdomain.com`, and see [the CLI guide](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/) for how that command is documented. ## Logos A logo appears next to a company only where an official one exists: a mark from the simple-icons package (CC0) whose own source page belongs to the company's domain, a mark for the company's other domain from a short reviewed table, a mark accepted after a recorded hand review of the company's name, site and the icon's source (data/logo-reviews.json), or the company's own published file fetched once. A mark that a review found to belong to another entity is rejected and the name stands alone. Each logo's source and basis are in the repository's data/logo-sources.json; the marks remain the property of their owners. ## The API, the MCP server and the ask endpoint The rows the pages show are also served to agents three ways, documented on [the API and MCP server page](https://agentmcpdirectory.com/developers/): an MCP server at `/mcp` (Streamable HTTP, five read-only tools over the directory rows and the census), a REST API under `/api/v1/` described by [openapi.json](https://agentmcpdirectory.com/openapi.json), and an NLWeb `/ask` endpoint that searches the rows and pages and returns schema.org objects with a source URL each. Every surface reads the published files in [/data](https://agentmcpdirectory.com/data/) when a request arrives and keeps each file for ten minutes per running instance, so an answer and the page it cites come from the same edition and follow the same counting rule: only a server whose tools the connector listed counts. The surfaces never call a company's server, nothing writes and nothing needs a credential; [auth.md](https://agentmcpdirectory.com/auth.md) says so. ## What this directory does not do - It does not call a tool, sign in, register a client or submit a form on any server. - It does not prove that a company has no server. A "none found" row means no source read for this edition names an endpoint. - The CLI column is a floor: a package is checked only where a source names one. - Categories follow Ora's leaderboard where the company is scored there, and a registry description elsewhere. The fact sheet on each entry says which. - Rows are discovered from the official MCP Registry, the GitHub MCP Registry, the awesome-remote-mcp-servers list, vendor documentation and Ora's leaderboard, so companies outside those lists are missing. Platform domains that host other people's sites are not listed as companies. - Markdown copies are reached through each page's `rel="alternate"` link and the `.md` path (`//index.md`). On the Lovable host, prerendered pages are served before any worker runs, so `Accept: text/markdown` negotiation is not available there; the Vercel preview negotiates it in a root middleware that serves the twin. - The site's own MCP server serves this directory read-only and is not a row in it, because the directory lists companies and not this publication. It cannot call a tool on a company's server, sign in or submit a form, and it adds no data that the pages do not show. See [the API and MCP server page](https://agentmcpdirectory.com/developers/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/method/index.md) ## Sources - [MCP authorization, 2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 - [MCP 2026-07-28 changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [Official MCP Registry API](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 - [GitHub MCP Registry API](https://api.mcp.github.com/v0/servers), read 4 November 2026 - [Ora scoring method (vendor-published)](https://ora.ai/methodology?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=method), read 4 November 2026 - [Ora check catalog (vendor-published)](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=method), read 5 November 2026 - [Ora leaderboard (vendor-published)](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=method), read 5 November 2026 - [Ora Journey (vendor-published)](https://journey.ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=method), read 4 November 2026 - [Ora CLI docs](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=method), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "News: MCP, registries, hosts and gateways | Agent MCP Directory" description: "17 dated items from primary sources on MCP, registries, hosts and gateways, 22 August 2026 to 3 November 2026. Each links to its source." canonical: https://agentmcpdirectory.com/news site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-11-03 section: "News" --- # News: MCP, registries, hosts and gateways | Agent MCP Directory > 17 dated items from primary sources on MCP, registries, hosts and gateways, 22 August 2026 to 3 November 2026. Each links to its source. Source: https://agentmcpdirectory.com/news Site: Agent MCP Directory Last reviewed: 2026-11-04 # News 17 dated items from the last three months, taken from primary sources: specification releases, registry and host changelogs, and vendor posts. Each one names what changed, links its source and shows where it touches a host, a registry or a guide on this site. | Date | Item | What changed | | --- | --- | --- | | 2026-11-03 | New Cloudflare AI Gateways require authentication | Cloudflare now requires authentication on newly created AI Gateways, closing open gateways by default. | | 2026-11-02 | Vercel MCP accepts Client ID Metadata Documents | Any MCP client can now connect to Vercel MCP without prior review by publishing a Client ID Metadata Document and using its HTTPS URL as the OAuth client_id. | | 2026-11-02 | Vercel MCP renders deployments as an interactive card | Vercel MCP now returns deployment status and build logs as an MCP Apps card in clients such as ChatGPT. | | 2026-10-31 | Smithery shuts down MCP Proxy and managed identity | The smithery.ai home page states that the MCP Proxy and managed identity features shut down on 31 October; Smithery joined Arcade in August. | | 2026-10-30 | Official Ruby SDK for MCP reaches Tier 1 | The MCP project moved the official Ruby SDK to Tier 1 under its SDK tiering system, three months after its 1.0 release. | | 2026-10-22 | Cloudflare MCP servers stop serving /sse | Cloudflare product MCP servers now serve only /mcp. | | 2026-10-22 | GitHub counts MCP servers in Copilot usage metrics | GitHub added custom skills, agents and MCP servers to the Copilot usage metrics API, so organisations can see which MCP servers their developers use. | | 2026-10-19 | Cloudflare API MCP server adds step-up authorization | The Cloudflare API MCP server now asks for additional scopes when an operation needs them, the step-up flow described in the MCP authorization spec. | | 2026-10-19 | Ora launches AgentReady.org with an act-layer MUST | Ora published AgentReady.org, an MIT-licensed standard whose act layer requires "an MCP server or a CLI, at least one". | | 2026-10-01 | Workers OAuth Provider reaches v1 | Cloudflare's OAuth library for MCP split into an authorization server Worker and resource server Workers that check tokens over a Service Binding. | | 2026-09-30 | Arcade rescans 90,000 MCP servers | Arcade's ToolBench rescan graded more than 90,000 open-source MCP servers and 630,000 tools: 260 servers (0.28 percent) earned an A, 5.8 percent handle requests statelessly, and nearly 17,000 ship a destructive tool while only 14 percent declare safety annotations. | | 2026-09-28 | Cloudflare Browser Run moves WebMCP to document.modelContext | Cloudflare added WebMCP to its Kitesurf agent browser and switched to the document.modelContext API name used in the current WebMCP draft. | | 2026-09-24 | Cloudflare MCP server portals reach general availability | Portals give one endpoint for approved MCP servers with Access logging of tool, prompt and resource activity. | | 2026-09-22 | Cloudflare portals add private MCP server support | MCP server portals can now front private MCP servers, not only public remote ones, ahead of general availability two days later. | | 2026-08-27 | A2A joins the Agentic AI Foundation | The A2A project was accepted as a Growth Stage project at the Linux Foundation-directed Agentic AI Foundation, next to MCP, goose and AGENTS.md. | | 2026-08-25 | Cloudflare MCP server portals support MCP 2026-07-28 | Cloudflare updated MCP server portals to accept clients on the stateless 2026-07-28 revision, a month after the spec shipped, while still serving earlier Streamable HTTP clients. | | 2026-08-22 | MCP maintainers publish the new roadmap | The roadmap names five priority areas: agentic messaging primitives, Streamable HTTP for local servers, agent identity and enterprise security (DPoP, workload identity), improved primitives including progressive tool discovery, and SDK developer experience. | The feed is at [feed.xml](https://agentmcpdirectory.com/feed.xml). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/index.md) ## Sources - [New Cloudflare AI Gateways require authentication](https://developers.cloudflare.com/changelog/post/2026-11-03-required-authentication/), read 4 November 2026 - [Vercel MCP accepts Client ID Metadata Documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Vercel MCP renders deployments as an interactive card](https://vercel.com/changelog/monitor-vercel-deployments-in-chatgpt), read 4 November 2026 - [Smithery shuts down MCP Proxy and managed identity](https://smithery.ai/), read 4 November 2026 - [Official Ruby SDK for MCP reaches Tier 1](https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/), read 4 November 2026 - [Cloudflare MCP servers stop serving /sse](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 - [GitHub counts MCP servers in Copilot usage metrics](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), read 4 November 2026 - [Cloudflare API MCP server adds step-up authorization](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), read 4 November 2026 - [Ora launches AgentReady.org with an act-layer MUST](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 4 November 2026 - [Workers OAuth Provider reaches v1](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Arcade rescans 90,000 MCP servers](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 4 November 2026 - [Cloudflare Browser Run moves WebMCP to document.modelContext](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 4 November 2026 - [Cloudflare MCP server portals reach general availability](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/), read 4 November 2026 - [Cloudflare portals add private MCP server support](https://developers.cloudflare.com/changelog/post/2026-09-22-private-mcp-servers/), read 4 November 2026 - [A2A joins the Agentic AI Foundation](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 - [Cloudflare MCP server portals support MCP 2026-07-28](https://developers.cloudflare.com/changelog/post/2026-08-25-mcp-portals-mcp-2026-07-28/), read 4 November 2026 - [MCP maintainers publish the new roadmap](https://blog.modelcontextprotocol.io/posts/mcp-roadmap/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "MCP maintainers publish the new roadmap | Agent MCP Directory" description: "MCP maintainers publish the new roadmap. The roadmap names five priority areas: agentic messaging primitives, Streamable HTTP for local servers." canonical: https://agentmcpdirectory.com/news/2026-08-22-mcp-maintainers-publish-the-new-roadmap site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-08-22 section: "News" --- # MCP maintainers publish the new roadmap | Agent MCP Directory > MCP maintainers publish the new roadmap. The roadmap names five priority areas: agentic messaging primitives, Streamable HTTP for local servers. Source: https://agentmcpdirectory.com/news/2026-08-22-mcp-maintainers-publish-the-new-roadmap Site: Agent MCP Directory Last reviewed: 2026-11-04 # MCP maintainers publish the new roadmap The roadmap names five priority areas: agentic messaging primitives, Streamable HTTP for local servers, agent identity and enterprise security (DPoP, workload identity), improved primitives including progressive tool discovery, and SDK developer experience. Server cards continue in a Working Group. Reported 22 August 2026 by blog.modelcontextprotocol.io, read 4 November 2026. ## What it changes in the data held here Of 817 reachable endpoints in the directory, 812 answered over Streamable HTTP and 5 over the legacy SSE transport. The 2026-07-28 specification classes SSE as deprecated, so the second figure is the count of servers that will need to move. The connector log shows which protocol revisions the directory's reachable servers answered with: 189 on 2025-11-25, 40 on 2025-06-18, 16 on 2026-07-28, 11 on 2025-03-26, 9 on 2024-11-05. Servers on 2025-11-25 still use the initialize handshake that 2026-07-28 removes. Source: [blog.modelcontextprotocol.io](https://blog.modelcontextprotocol.io/posts/mcp-roadmap/), a primary source, dated 22 August 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Build a remote MCP server on Cloudflare or Vercel](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) - [MCP, the standard](https://agentmcpdirectory.com/standards/mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-08-22-mcp-maintainers-publish-the-new-roadmap/index.md) ## Sources - [MCP maintainers publish the new roadmap](https://blog.modelcontextprotocol.io/posts/mcp-roadmap/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Cloudflare MCP server portals support MCP | Agent MCP Directory" description: "Cloudflare MCP server portals support MCP 2026-07-28. Cloudflare updated MCP server portals to accept clients on the stateless 2026-07-28 revision." canonical: https://agentmcpdirectory.com/news/2026-08-25-cloudflare-mcp-server-portals-support-mcp-2026-07-28 site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-08-25 section: "News" --- # Cloudflare MCP server portals support MCP | Agent MCP Directory > Cloudflare MCP server portals support MCP 2026-07-28. Cloudflare updated MCP server portals to accept clients on the stateless 2026-07-28 revision. Source: https://agentmcpdirectory.com/news/2026-08-25-cloudflare-mcp-server-portals-support-mcp-2026-07-28 Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare MCP server portals support MCP 2026-07-28 Cloudflare updated MCP server portals to accept clients on the stateless 2026-07-28 revision, a month after the spec shipped, while still serving earlier Streamable HTTP clients. Reported 25 August 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare. The full text of Cloudflare MCP server portals support MCP 2026-07-28 is at the source linked below. ## What it changes in the data held here Of 817 reachable endpoints in the directory, 812 answered over Streamable HTTP and 5 over the legacy SSE transport. The 2026-07-28 specification classes SSE as deprecated, so the second figure is the count of servers that will need to move. Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal. The connector log shows which protocol revisions the directory's reachable servers answered with: 189 on 2025-11-25, 40 on 2025-06-18, 16 on 2026-07-28, 11 on 2025-03-26, 9 on 2024-11-05. Servers on 2025-11-25 still use the initialize handshake that 2026-07-28 removes. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-08-25-mcp-portals-mcp-2026-07-28/), a primary source, dated 25 August 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/): rubric and evidence - [Build a remote MCP server on Cloudflare or Vercel](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) - [MCP, the standard](https://agentmcpdirectory.com/standards/mcp/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-08-25-cloudflare-mcp-server-portals-support-mcp-2026-07-28/index.md) ## Sources - [Cloudflare MCP server portals support MCP 2026-07-28](https://developers.cloudflare.com/changelog/post/2026-08-25-mcp-portals-mcp-2026-07-28/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "A2A joins the Agentic AI Foundation | Agent MCP Directory" description: "A2A joins the Agentic AI Foundation. The A2A project was accepted as a Growth Stage project at the Linux Foundation-directed Agentic AI Foundation." canonical: https://agentmcpdirectory.com/news/2026-08-27-a2a-joins-the-agentic-ai-foundation site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-08-27 section: "News" --- # A2A joins the Agentic AI Foundation | Agent MCP Directory > A2A joins the Agentic AI Foundation. The A2A project was accepted as a Growth Stage project at the Linux Foundation-directed Agentic AI Foundation. Source: https://agentmcpdirectory.com/news/2026-08-27-a2a-joins-the-agentic-ai-foundation Site: Agent MCP Directory Last reviewed: 2026-11-04 # A2A joins the Agentic AI Foundation The A2A project was accepted as a Growth Stage project at the Linux Foundation-directed Agentic AI Foundation, next to MCP, goose and AGENTS.md. The A2A spec is at 1.0.0 with JSON-RPC, gRPC and HTTP+JSON bindings. Reported 27 August 2026 by a2a-protocol.org, read 4 November 2026. ## What it changes in the data held here 10 of 7,470 probed top-10,000 domains publish an A2A agent card at /.well-known/agent-card.json, which is the discovery file the specification names. The connector log shows which protocol revisions the directory's reachable servers answered with: 189 on 2025-11-25, 40 on 2025-06-18, 16 on 2026-07-28, 11 on 2025-03-26, 9 on 2024-11-05. Servers on 2025-11-25 still use the initialize handshake that 2026-07-28 removes. Source: [a2a-protocol.org](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), a primary source, dated 27 August 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [A2A, the standard](https://agentmcpdirectory.com/standards/a2a/) - [MCP, the standard](https://agentmcpdirectory.com/standards/mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-08-27-a2a-joins-the-agentic-ai-foundation/index.md) ## Sources - [A2A joins the Agentic AI Foundation](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Cloudflare portals add private MCP server | Agent MCP Directory" description: "Cloudflare portals add private MCP server support. MCP server portals can now front private MCP servers, not only public remote ones." canonical: https://agentmcpdirectory.com/news/2026-09-22-cloudflare-portals-add-private-mcp-server-support site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-09-22 section: "News" --- # Cloudflare portals add private MCP server | Agent MCP Directory > Cloudflare portals add private MCP server support. MCP server portals can now front private MCP servers, not only public remote ones. Source: https://agentmcpdirectory.com/news/2026-09-22-cloudflare-portals-add-private-mcp-server-support Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare portals add private MCP server support MCP server portals can now front private MCP servers, not only public remote ones, ahead of general availability two days later. Reported 22 September 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare. The full text of Cloudflare portals add private MCP server support is at the source linked below. ## What it changes in the data held here Of 817 reachable endpoints in the directory, 812 answered over Streamable HTTP and 5 over the legacy SSE transport. The 2026-07-28 specification classes SSE as deprecated, so the second figure is the count of servers that will need to move. Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-09-22-private-mcp-servers/), a primary source, dated 22 September 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/): rubric and evidence - [Build a remote MCP server on Cloudflare or Vercel](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-09-22-cloudflare-portals-add-private-mcp-server-support/index.md) ## Sources - [Cloudflare portals add private MCP server support](https://developers.cloudflare.com/changelog/post/2026-09-22-private-mcp-servers/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Cloudflare MCP server portals reach general | Agent MCP Directory" description: "Cloudflare MCP server portals reach general availability. Portals give one endpoint for approved MCP servers with Access logging of tool." canonical: https://agentmcpdirectory.com/news/2026-09-24-cloudflare-mcp-server-portals-reach-general-availability site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-09-24 section: "News" --- # Cloudflare MCP server portals reach general | Agent MCP Directory > Cloudflare MCP server portals reach general availability. Portals give one endpoint for approved MCP servers with Access logging of tool. Source: https://agentmcpdirectory.com/news/2026-09-24-cloudflare-mcp-server-portals-reach-general-availability Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare MCP server portals reach general availability Portals give one endpoint for approved MCP servers with Access logging of tool, prompt and resource activity. Since beta they gained Gateway routing with DLP, Code Mode policies, static OAuth credentials, session management, service tokens and Logpush. Reported 24 September 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare. ## What it changes in the data held here Of 817 reachable endpoints in the directory, 812 answered over Streamable HTTP and 5 over the legacy SSE transport. The 2026-07-28 specification classes SSE as deprecated, so the second figure is the count of servers that will need to move. 517 endpoints in the directory offer dynamic client registration, 16 publish OAuth metadata without a registration endpoint, and 191 state client ID metadata document support. 533 endpoints stop at a sign-in challenge, so this directory sees their auth route but not their tools. Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/), a primary source, dated 24 September 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/): rubric and evidence - [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) - [Build a remote MCP server on Cloudflare or Vercel](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-09-24-cloudflare-mcp-server-portals-reach-general-availability/index.md) ## Sources - [Cloudflare MCP server portals reach general availability](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Cloudflare Browser Run moves WebMCP | Agent MCP Directory" description: "Cloudflare Browser Run moves WebMCP to document.modelContext. Cloudflare added WebMCP to its Kitesurf agent browser and switched to the document.modelContext." canonical: https://agentmcpdirectory.com/news/2026-09-28-cloudflare-browser-run-moves-webmcp-to-document-modelcontext site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-09-28 section: "News" --- # Cloudflare Browser Run moves WebMCP | Agent MCP Directory > Cloudflare Browser Run moves WebMCP to document.modelContext. Cloudflare added WebMCP to its Kitesurf agent browser and switched to the document.modelContext. Source: https://agentmcpdirectory.com/news/2026-09-28-cloudflare-browser-run-moves-webmcp-to-document-modelcontext Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare Browser Run moves WebMCP to document.modelContext Cloudflare added WebMCP to its Kitesurf agent browser and switched to the document.modelContext API name used in the current WebMCP draft. Reported 28 September 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare. The full text of Cloudflare Browser Run moves WebMCP to document.modelContext is at the source linked below. ## What it changes in the data held here The shared crawl found a WebMCP hint on 25 of 7,545 top-10,000 home pages, so the browser-side route is still rare next to the 263 open server endpoints counted here. Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), a primary source, dated 28 September 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/): rubric and evidence - [How to add WebMCP to a page](https://agentmcpdirectory.com/guides/add-webmcp-to-a-page/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-09-28-cloudflare-browser-run-moves-webmcp-to-document-modelcontext/index.md) ## Sources - [Cloudflare Browser Run moves WebMCP to document.modelContext](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Arcade rescans 90,000 MCP servers | Agent MCP Directory" description: "Arcade rescans 90,000 MCP servers. Arcade's ToolBench rescan graded more than 90,000 open-source MCP servers and 630,000 tools." canonical: https://agentmcpdirectory.com/news/2026-09-30-arcade-rescans-90-000-mcp-servers site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-09-30 section: "News" --- # Arcade rescans 90,000 MCP servers | Agent MCP Directory > Arcade rescans 90,000 MCP servers. Arcade's ToolBench rescan graded more than 90,000 open-source MCP servers and 630,000 tools. Source: https://agentmcpdirectory.com/news/2026-09-30-arcade-rescans-90-000-mcp-servers Site: Agent MCP Directory Last reviewed: 2026-11-04 # Arcade rescans 90,000 MCP servers Arcade's ToolBench rescan graded more than 90,000 open-source MCP servers and 630,000 tools: 260 servers (0.28 percent) earned an A, 5.8 percent handle requests statelessly, and nearly 17,000 ship a destructive tool while only 14 percent declare safety annotations. Vendor research. ## What it changes in the data held here Smithery on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP (registry entries); oauth with client registration: managed identity retired; per-tool auth scoping: not documented. Source: [www.arcade.dev](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), a vendor source, dated 30 September 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Smithery](https://agentmcpdirectory.com/hosts/smithery/): rubric and evidence Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-09-30-arcade-rescans-90-000-mcp-servers/index.md) ## Sources - [Arcade rescans 90,000 MCP servers](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 4 November 2026 (vendor source) Last reviewed 4 November 2026 --- --- title: "Workers OAuth Provider reaches v1 | Agent MCP Directory" description: "Workers OAuth Provider reaches v1. Cloudflare's OAuth library for MCP split into an authorization server Worker and resource server Workers that check." canonical: https://agentmcpdirectory.com/news/2026-10-01-workers-oauth-provider-reaches-v1 site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-10-01 section: "News" --- # Workers OAuth Provider reaches v1 | Agent MCP Directory > Workers OAuth Provider reaches v1. Cloudflare's OAuth library for MCP split into an authorization server Worker and resource server Workers that check. Source: https://agentmcpdirectory.com/news/2026-10-01-workers-oauth-provider-reaches-v1 Site: Agent MCP Directory Last reviewed: 2026-11-04 # Workers OAuth Provider reaches v1 Cloudflare's OAuth library for MCP split into an authorization server Worker and resource server Workers that check tokens over a Service Binding. v1 supports DCR and Client ID Metadata Documents per the 2026-07-28 authorization spec. Reported 1 October 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare. ## What it changes in the data held here 517 endpoints in the directory offer dynamic client registration, 16 publish OAuth metadata without a registration endpoint, and 191 state client ID metadata document support. 533 endpoints stop at a sign-in challenge, so this directory sees their auth route but not their tools. Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal. The connector log shows which protocol revisions the directory's reachable servers answered with: 189 on 2025-11-25, 40 on 2025-06-18, 16 on 2026-07-28, 11 on 2025-03-26, 9 on 2024-11-05. Servers on 2025-11-25 still use the initialize handshake that 2026-07-28 removes. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), a primary source, dated 1 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/): rubric and evidence - [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) - [MCP, the standard](https://agentmcpdirectory.com/standards/mcp/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-10-01-workers-oauth-provider-reaches-v1/index.md) ## Sources - [Workers OAuth Provider reaches v1](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Cloudflare API MCP server adds step-up | Agent MCP Directory" description: "Cloudflare API MCP server adds step-up authorization. The Cloudflare API MCP server now asks for additional scopes when an operation needs them." canonical: https://agentmcpdirectory.com/news/2026-10-19-cloudflare-api-mcp-server-adds-step-up-authorization site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-10-19 section: "News" --- # Cloudflare API MCP server adds step-up | Agent MCP Directory > Cloudflare API MCP server adds step-up authorization. The Cloudflare API MCP server now asks for additional scopes when an operation needs them. Source: https://agentmcpdirectory.com/news/2026-10-19-cloudflare-api-mcp-server-adds-step-up-authorization Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare API MCP server adds step-up authorization The Cloudflare API MCP server now asks for additional scopes when an operation needs them, the step-up flow described in the MCP authorization spec. Reported 19 October 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare. The full text of Cloudflare API MCP server adds step-up authorization is at the source linked below. ## What it changes in the data held here 517 endpoints in the directory offer dynamic client registration, 16 publish OAuth metadata without a registration endpoint, and 191 state client ID metadata document support. 533 endpoints stop at a sign-in challenge, so this directory sees their auth route but not their tools. Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal. The connector log shows which protocol revisions the directory's reachable servers answered with: 189 on 2025-11-25, 40 on 2025-06-18, 16 on 2026-07-28, 11 on 2025-03-26, 9 on 2024-11-05. Servers on 2025-11-25 still use the initialize handshake that 2026-07-28 removes. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), a primary source, dated 19 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/): rubric and evidence - [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) - [MCP, the standard](https://agentmcpdirectory.com/standards/mcp/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-10-19-cloudflare-api-mcp-server-adds-step-up-authorization/index.md) ## Sources - [Cloudflare API MCP server adds step-up authorization](https://developers.cloudflare.com/changelog/post/2026-10-19-cloudflare-mcp-step-up/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Ora launches AgentReady.org with an act-layer | Agent MCP Directory" description: "Ora launches AgentReady.org with an act-layer MUST. Ora published AgentReady.org, an MIT-licensed standard whose act layer requires \"an MCP server or a CLI." canonical: https://agentmcpdirectory.com/news/2026-10-19-ora-launches-agentready-org-with-an-act-layer-must site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-10-19 section: "News" --- # Ora launches AgentReady.org with an act-layer | Agent MCP Directory > Ora launches AgentReady.org with an act-layer MUST. Ora published AgentReady.org, an MIT-licensed standard whose act layer requires "an MCP server or a CLI. Source: https://agentmcpdirectory.com/news/2026-10-19-ora-launches-agentready-org-with-an-act-layer-must Site: Agent MCP Directory Last reviewed: 2026-11-04 # Ora launches AgentReady.org with an act-layer MUST Ora published AgentReady.org, an MIT-licensed standard whose act layer requires "an MCP server or a CLI, at least one". The launch post names a seven-member committee (Ora, Vercel, Mintlify, Auth0, Stripe, Tavily, Elementor) and cites more than 250,000 agent runs. Vendor-published figures. ## What it changes in the data held here Against the rule that an agent-ready product has an MCP server or a CLI, 263 directory companies have an MCP server with tools listed, 36 have a CLI on record and 1,044 have neither, out of 1,336. Vercel on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: bring your own AS; CIMD on Vercel MCP; per-tool auth scoping: scopes per handler. Mintlify MCP on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP; oauth with client registration: client credentials at /authed/mcp/oauth/token; per-tool auth scoping: public versus authed endpoints. Source: [ora.ai](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=news), a primary source, dated 19 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Vercel](https://agentmcpdirectory.com/hosts/vercel/): rubric and evidence - [Mintlify MCP](https://agentmcpdirectory.com/hosts/mintlify-mcp/): rubric and evidence - [Keep an MCP server agent ready in CI](https://agentmcpdirectory.com/guides/keep-mcp-agent-ready-in-ci/) - [Vercel in the directory](https://agentmcpdirectory.com/directory/vercel-com/): sign-in required, tools not seen, not counted Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-10-19-ora-launches-agentready-org-with-an-act-layer-must/index.md) ## Sources - [Ora launches AgentReady.org with an act-layer MUST](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=news), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Cloudflare MCP servers stop serving /sse | Agent MCP Directory" description: "Cloudflare MCP servers stop serving /sse. Cloudflare product MCP servers now serve only /mcp. Requests to /sse return 410 Gone with the /mcp URL." canonical: https://agentmcpdirectory.com/news/2026-10-22-cloudflare-mcp-servers-stop-serving-sse site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-10-22 section: "News" --- # Cloudflare MCP servers stop serving /sse | Agent MCP Directory > Cloudflare MCP servers stop serving /sse. Cloudflare product MCP servers now serve only /mcp. Requests to /sse return 410 Gone with the /mcp URL. Source: https://agentmcpdirectory.com/news/2026-10-22-cloudflare-mcp-servers-stop-serving-sse Site: Agent MCP Directory Last reviewed: 2026-11-04 # Cloudflare MCP servers stop serving /sse Cloudflare product MCP servers now serve only /mcp. Requests to /sse return 410 Gone with the /mcp URL, and clients that signed in through /sse must sign in again. Reported 22 October 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare. ## What it changes in the data held here Of 817 reachable endpoints in the directory, 812 answered over Streamable HTTP and 5 over the legacy SSE transport. The 2026-07-28 specification classes SSE as deprecated, so the second figure is the count of servers that will need to move. 517 endpoints in the directory offer dynamic client registration, 16 publish OAuth metadata without a registration endpoint, and 191 state client ID metadata document support. 533 endpoints stop at a sign-in challenge, so this directory sees their auth route but not their tools. Against the rule that an agent-ready product has an MCP server or a CLI, 263 directory companies have an MCP server with tools listed, 36 have a CLI on record and 1,044 have neither, out of 1,336. Cloudflare on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: yes, DCR and CIMD; per-tool auth scoping: yes, at the portal. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), a primary source, dated 22 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/): rubric and evidence - [Build a remote MCP server on Cloudflare or Vercel](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) - [Keep an MCP server agent ready in CI](https://agentmcpdirectory.com/guides/keep-mcp-agent-ready-in-ci/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-10-22-cloudflare-mcp-servers-stop-serving-sse/index.md) ## Sources - [Cloudflare MCP servers stop serving /sse](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "GitHub counts MCP servers in Copilot usage | Agent MCP Directory" description: "GitHub counts MCP servers in Copilot usage metrics. GitHub added custom skills, agents and MCP servers to the Copilot usage metrics API." canonical: https://agentmcpdirectory.com/news/2026-10-22-github-counts-mcp-servers-in-copilot-usage-metrics site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-10-22 section: "News" --- # GitHub counts MCP servers in Copilot usage | Agent MCP Directory > GitHub counts MCP servers in Copilot usage metrics. GitHub added custom skills, agents and MCP servers to the Copilot usage metrics API. Source: https://agentmcpdirectory.com/news/2026-10-22-github-counts-mcp-servers-in-copilot-usage-metrics Site: Agent MCP Directory Last reviewed: 2026-11-04 # GitHub counts MCP servers in Copilot usage metrics GitHub added custom skills, agents and MCP servers to the Copilot usage metrics API, so organisations can see which MCP servers their developers use. Reported 22 October 2026 by github.blog, read 4 November 2026; products involved: GitHub MCP Registry. The full text of GitHub counts MCP servers in Copilot usage metrics is at the source linked below. ## What it changes in the data held here Against the rule that an agent-ready product has an MCP server or a CLI, 263 directory companies have an MCP server with tools listed, 36 have a CLI on record and 1,044 have neither, out of 1,336. GitHub MCP Registry on this directory's rubric, as read on 4 November 2026: remote transport: records remotes; oauth with client registration: not applicable; per-tool auth scoping: not applicable. Source: [github.blog](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), a primary source, dated 22 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [GitHub MCP Registry](https://agentmcpdirectory.com/hosts/github-mcp-registry/): rubric and evidence - [GitHub in the directory](https://agentmcpdirectory.com/directory/github-com/): sign-in required, tools not seen, not counted Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-10-22-github-counts-mcp-servers-in-copilot-usage-metrics/index.md) ## Sources - [GitHub counts MCP servers in Copilot usage metrics](https://github.blog/changelog/2026-10-22-custom-skills-agents-and-mcp-servers-in-usage-metrics-api), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Official Ruby SDK for MCP reaches Tier 1 | Agent MCP Directory" description: "Official Ruby SDK for MCP reaches Tier 1. The MCP project moved the official Ruby SDK to Tier 1 under its SDK tiering system." canonical: https://agentmcpdirectory.com/news/2026-10-30-official-ruby-sdk-for-mcp-reaches-tier-1 site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-10-30 section: "News" --- # Official Ruby SDK for MCP reaches Tier 1 | Agent MCP Directory > Official Ruby SDK for MCP reaches Tier 1. The MCP project moved the official Ruby SDK to Tier 1 under its SDK tiering system. Source: https://agentmcpdirectory.com/news/2026-10-30-official-ruby-sdk-for-mcp-reaches-tier-1 Site: Agent MCP Directory Last reviewed: 2026-11-04 # Official Ruby SDK for MCP reaches Tier 1 The MCP project moved the official Ruby SDK to Tier 1 under its SDK tiering system, three months after its 1.0 release. Reported 30 October 2026 by blog.modelcontextprotocol.io, read 4 November 2026. The full text of Official Ruby SDK for MCP reaches Tier 1 is at the source linked below. ## What it changes in the data held here The connector log shows which protocol revisions the directory's reachable servers answered with: 189 on 2025-11-25, 40 on 2025-06-18, 16 on 2026-07-28, 11 on 2025-03-26, 9 on 2024-11-05. Servers on 2025-11-25 still use the initialize handshake that 2026-07-28 removes. Source: [blog.modelcontextprotocol.io](https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/), a primary source, dated 30 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [MCP, the standard](https://agentmcpdirectory.com/standards/mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-10-30-official-ruby-sdk-for-mcp-reaches-tier-1/index.md) ## Sources - [Official Ruby SDK for MCP reaches Tier 1](https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Smithery shuts down MCP Proxy and managed | Agent MCP Directory" description: "Smithery shuts down MCP Proxy and managed identity. The smithery.ai home page states that the MCP Proxy and managed identity features shut down on 31 October." canonical: https://agentmcpdirectory.com/news/2026-10-31-smithery-shuts-down-mcp-proxy-and-managed-identity site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-10-31 section: "News" --- # Smithery shuts down MCP Proxy and managed | Agent MCP Directory > Smithery shuts down MCP Proxy and managed identity. The smithery.ai home page states that the MCP Proxy and managed identity features shut down on 31 October. Source: https://agentmcpdirectory.com/news/2026-10-31-smithery-shuts-down-mcp-proxy-and-managed-identity Site: Agent MCP Directory Last reviewed: 2026-11-04 # Smithery shuts down MCP Proxy and managed identity The smithery.ai home page states that the MCP Proxy and managed identity features shut down on 31 October; Smithery joined Arcade in August. Older Smithery listing URLs returned 404 on 4 Nov 2026. Reported 31 October 2026 by smithery.ai, read 4 November 2026; products involved: Smithery. ## What it changes in the data held here In the directory, 493 companies are listed in the official MCP Registry, 504 in the GitHub MCP Registry and 117 in the awesome-remote-mcp-servers list. Smithery's listing pages were unavailable on 4 November 2026, so no Smithery listing is recorded for any row. Smithery on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP (registry entries); oauth with client registration: managed identity retired; per-tool auth scoping: not documented. Source: [smithery.ai](https://smithery.ai/), a primary source, dated 31 October 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Smithery](https://agentmcpdirectory.com/hosts/smithery/): rubric and evidence - [How to get listed in each registry](https://agentmcpdirectory.com/guides/get-listed-in-registries/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-10-31-smithery-shuts-down-mcp-proxy-and-managed-identity/index.md) ## Sources - [Smithery shuts down MCP Proxy and managed identity](https://smithery.ai/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Vercel MCP accepts Client ID Metadata Documents | Agent MCP Directory" description: "Vercel MCP accepts Client ID Metadata Documents. Any MCP client can now connect to Vercel MCP without prior review by publishing a Client ID Metadata Document." canonical: https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-accepts-client-id-metadata-documents site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-11-02 section: "News" --- # Vercel MCP accepts Client ID Metadata Documents | Agent MCP Directory > Vercel MCP accepts Client ID Metadata Documents. Any MCP client can now connect to Vercel MCP without prior review by publishing a Client ID Metadata Document. Source: https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-accepts-client-id-metadata-documents Site: Agent MCP Directory Last reviewed: 2026-11-04 # Vercel MCP accepts Client ID Metadata Documents Any MCP client can now connect to Vercel MCP without prior review by publishing a Client ID Metadata Document and using its HTTPS URL as the OAuth client\_id. Users still approve each connection. Reported 2 November 2026 by vercel.com, read 4 November 2026; products involved: Vercel. ## What it changes in the data held here 517 endpoints in the directory offer dynamic client registration, 16 publish OAuth metadata without a registration endpoint, and 191 state client ID metadata document support. 533 endpoints stop at a sign-in challenge, so this directory sees their auth route but not their tools. Vercel on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: bring your own AS; CIMD on Vercel MCP; per-tool auth scoping: scopes per handler. Source: [vercel.com](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), a primary source, dated 2 November 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Vercel](https://agentmcpdirectory.com/hosts/vercel/): rubric and evidence - [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) - [Vercel in the directory](https://agentmcpdirectory.com/directory/vercel-com/): sign-in required, tools not seen, not counted Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-accepts-client-id-metadata-documents/index.md) ## Sources - [Vercel MCP accepts Client ID Metadata Documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Vercel MCP renders deployments | Agent MCP Directory" description: "Vercel MCP renders deployments as an interactive card. Vercel MCP now returns deployment status and build logs as an MCP Apps card in clients such as ChatGPT." canonical: https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-renders-deployments-as-an-interactive-card site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-11-02 section: "News" --- # Vercel MCP renders deployments | Agent MCP Directory > Vercel MCP renders deployments as an interactive card. Vercel MCP now returns deployment status and build logs as an MCP Apps card in clients such as ChatGPT. Source: https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-renders-deployments-as-an-interactive-card Site: Agent MCP Directory Last reviewed: 2026-11-04 # Vercel MCP renders deployments as an interactive card Vercel MCP now returns deployment status and build logs as an MCP Apps card in clients such as ChatGPT. Reported 2 November 2026 by vercel.com, read 4 November 2026; products involved: Vercel. The full text of Vercel MCP renders deployments as an interactive card is at the source linked below. ## What it changes in the data held here Vercel on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: bring your own AS; CIMD on Vercel MCP; per-tool auth scoping: scopes per handler. Source: [vercel.com](https://vercel.com/changelog/monitor-vercel-deployments-in-chatgpt), a primary source, dated 2 November 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Vercel](https://agentmcpdirectory.com/hosts/vercel/): rubric and evidence - [Vercel in the directory](https://agentmcpdirectory.com/directory/vercel-com/): sign-in required, tools not seen, not counted Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-11-02-vercel-mcp-renders-deployments-as-an-interactive-card/index.md) ## Sources - [Vercel MCP renders deployments as an interactive card](https://vercel.com/changelog/monitor-vercel-deployments-in-chatgpt), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "New Cloudflare AI Gateways require | Agent MCP Directory" description: "New Cloudflare AI Gateways require authentication. Cloudflare now requires authentication on newly created AI Gateways, closing open gateways by default." canonical: https://agentmcpdirectory.com/news/2026-11-03-new-cloudflare-ai-gateways-require-authentication site: "Agent MCP Directory" last_updated: 2026-11-04 date: 2026-11-03 section: "News" --- # New Cloudflare AI Gateways require | Agent MCP Directory > New Cloudflare AI Gateways require authentication. Cloudflare now requires authentication on newly created AI Gateways, closing open gateways by default. Source: https://agentmcpdirectory.com/news/2026-11-03-new-cloudflare-ai-gateways-require-authentication Site: Agent MCP Directory Last reviewed: 2026-11-04 # New Cloudflare AI Gateways require authentication Cloudflare now requires authentication on newly created AI Gateways, closing open gateways by default. Reported 3 November 2026 by developers.cloudflare.com, read 4 November 2026; products involved: Cloudflare AI Gateway. The full text of New Cloudflare AI Gateways require authentication is at the source linked below. ## What it changes in the data held here Of 817 reachable endpoints in the directory, 812 answered over Streamable HTTP and 5 over the legacy SSE transport. The 2026-07-28 specification classes SSE as deprecated, so the second figure is the count of servers that will need to move. Cloudflare AI Gateway on this directory's rubric, as read on 4 November 2026: protocols fronted: model APIs; MCP goes through portals; auth passthrough: BYOK or Unified Billing. Source: [developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-11-03-required-authentication/), a primary source, dated 3 November 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026. ## Where it shows up here - [Cloudflare AI Gateway](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/): rubric and evidence - [Build a remote MCP server on Cloudflare or Vercel](https://agentmcpdirectory.com/guides/build-remote-mcp-server-cloudflare-vercel/) - [Cloudflare in the directory](https://agentmcpdirectory.com/directory/cloudflare-com/): has an open MCP server with tools listed Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/news/2026-11-03-new-cloudflare-ai-gateways-require-authentication/index.md) ## Sources - [New Cloudflare AI Gateways require authentication](https://developers.cloudflare.com/changelog/post/2026-11-03-required-authentication/), read 4 November 2026 (primary source) Last reviewed 4 November 2026 --- --- title: "Ora's MCP server: the 18 tools | Agent MCP Directory" description: "Ora's MCP server at ora.ai/api/mcp: 18 tools with their descriptions, how to connect, the read-only docs server and where it is not listed." canonical: https://agentmcpdirectory.com/ora-mcp-server site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Testing" --- # Ora's MCP server: the 18 tools | Agent MCP Directory > Ora's MCP server at ora.ai/api/mcp: 18 tools with their descriptions, how to connect, the read-only docs server and where it is not listed. Source: https://agentmcpdirectory.com/ora-mcp-server Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ora's MCP server: the 18 tools Ora runs an open MCP server at https://ora.ai/api/mcp with 18 tools and 7 resources, and the connector listed them with no credentials on 4 November 2026. Its server card declares the kind product. A second read-only server serves Ora's documentation. | Endpoint | https://ora.ai/api/mcp | | --- | --- | | Transport | streamable-http, protocol 2025-11-25 on the day the connector ran | | Server | ora 1.38.0 | | Authentication | none (the connector listed tools with no credentials) | | Tools, resources, prompts | 18, 7, 0 | | Connected | 4 November 2026, read-only methods only | | Kind in its server card | product (version 1.38.0; protocol versions 2025-11-25 and 2025-06-18) | | Cached Ora score | 95, grade A+, read 5 November 2026; the leaderboard read on 4 November 2026 showed 84, grade B | ## Connect to it Ora documents two ways to add the server, one for a coding agent and one for a client configured by hand. Both are Ora's own instructions, read on 5 November 2026. ```bash claude mcp add --transport http ora https://ora.ai/api/mcp ``` ```json { "mcpServers": { "ora": { "type": "streamable-http", "url": "https://www.ora.ai/api/mcp" } } } ``` ## The 18 tools The descriptions are the ones Ora's own manifest at `ora.ai/.well-known/mcp.json` gives an agent. The last column is this directory's reading of what each tool does on Ora's side; the connector never called any of them. | Tool | Description in the manifest | Required | What it does | | --- | --- | --- | --- | | scan_domain | Scan a domain for agent-readiness. Returns score, grade, and layer breakdown | url | Runs a scan | | get_score | Get the cached agent-readiness score for a domain | domain | Reads | | get_leaderboard | Get the ora leaderboard ranked by agent-readiness score | none | Reads | | discover_products | Find the most agent-ready products for a given need | intent | Reads | | search_capabilities | Find pay-per-call API endpoints payable with x402/MPP stablecoin payments - no API key or signup | query | Reads | | get_verification_challenge | Get a verification challenge to prove you are an AI agent before submitting feedback. Solve it and pass the answer to submit_feedback or submit_check_feedback | none | Reads a challenge | | submit_feedback | Submit agent feedback for a product. Agent-only - only available via MCP | domain, agent_id, task_description, outcome, content, recommendation | Writes feedback, verification needed | | send_feedback | Tell the ora team how ora's MCP and scanner worked for you: a bug, a wrong result, a confusing tool, a tool you needed but did not find, or something that worked well | summary, category, verification_token, verification_answer | Writes feedback, verification needed | | submit_check_feedback | Report an issue with a specific check result for a domain (false pass, false fail, wrong details, or outdated). Requires HATCHA verification | verification_token, verification_answer, domain, check_id, reason, message, agent_id | Writes feedback, verification needed | | get_feedback | Get agent feedback for a product. See what other agents experienced | domain | Reads | | list_skills | List the skills ora publishes for coding agents (e.g. agent-ready-website). Each skill is a self-contained instruction document; fetch one with get_skill and follow it | none | Reads | | get_skill | Fetch an ora skill by name and follow it step by step. Skills are served dynamically and updated as agent standards evolve; fetch a fresh copy at the start of each task | name | Reads | | list_checks | List the full catalog of checks behind ora's agent-readiness score: every check id with its layer, max score, applicability, tier, and maturity. Takes no inputs | none | Reads | | run_checks | Run a selected subset of checks against a URL and get per-check results back - the re-verify step after shipping a fix, with check ids from list_checks | url, checkIds | Runs checks | | ask | Search ora's published website content using NLWeb query, context, prefer, and meta. Returns relevant passages with source URLs and evidence provenance | query | Reads | | run_journey | Send a real AI agent at a site on a task and get ora's verdict, step count and insight. Pick a curated intent (no key needed) | domain | Runs an agent journey | | get_journey_run | Follow a journey started by run_journey until it finishes: waits up to 50s, then returns the verdict, step count and insight | run_id | Reads a journey | | generate_agent_files | Draft the discovery files agents look for on a site - /.well-known/ard.json, /.well-known/ai-catalog.json and /.well-known/poppy.json, plus on request llms.txt | domain | Reads | The manifest carries no annotations for any of the 18 tools, so a client cannot read from it which tools write. Ora's own check for `readOnlyHint` and `destructiveHint` is [one of the MCP checks](https://agentmcpdirectory.com/mcp-checks/). ## The docs server Ora runs a second, read-only server at `https://ora.ai/api/docs/mcp`. Its server card declares the kind docs, version 1.38.0 and the same two protocol versions. It has three tools. | Tool | What Ora says it does | Parameters | | --- | --- | --- | | search_docs | Search guides, MCP tools, REST endpoints, and schemas; returns matching sections with links | query (required), limit (optional, default 8, max 20) | | get_docs_page | Read one docs page as markdown | page (required, a docs page path such as /docs/partners) | | get_endpoint | One REST endpoint's OpenAPI operation with every schema it references | endpoint (required, "METHOD /path") | ## Where it is not listed The official MCP Registry returned no server for a search on Ora's publisher name or on ora.ai on 5 November 2026, so the server is reachable by URL and from Ora's own manifest but is not in that registry under its own name. [Why the registry matters](https://agentmcpdirectory.com/guides/get-listed-in-registries/). How Ora scores other servers is on [the pick page](https://agentmcpdirectory.com/test-your-mcp-server/) and in [the list of MCP checks](https://agentmcpdirectory.com/mcp-checks/). ## Testing your own MCP server [Why Ora is the pick for testing an MCP server, where it falls short and what else exists](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/ora-mcp-server/index.md) ## Sources - [Ora MCP manifest](https://ora.ai/.well-known/mcp.json?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [Ora main MCP server card](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [Ora docs MCP server card](https://ora.ai/api/docs/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [Ora API reference (llms-full.txt)](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [Ora MCP page](https://ora.ai/mcp?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [Official MCP Registry search for Ora's publisher name](https://registry.modelcontextprotocol.io/v0/servers?search=eralabs), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP servers with the highest Ora scores | Agent MCP Directory" description: "Which companies with an open MCP server score highest on Ora: the top 25, the grades and the leaders in each category, read 5 November 2026." canonical: https://agentmcpdirectory.com/ora-scores site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Ora scores" --- # MCP servers with the highest Ora scores | Agent MCP Directory > Which companies with an open MCP server score highest on Ora: the top 25, the grades and the leaders in each category, read 5 November 2026. Source: https://agentmcpdirectory.com/ora-scores Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP servers with the highest Ora scores Ora has a cached score for 933 of 1,336 companies in this directory; the 94 with an open MCP server have a median of 68. The highest is Telnyx at 99. Scores are Ora's, read on 5 November 2026. The MCP status is this directory's own. Ora scores a domain from 0 to 100 on four layers and gives it a grade. This page takes the 933 companies in the directory for which Ora has a cached score, read on 5 November 2026, and asks which of the 94 with an open MCP server score highest. The scores are Ora's; the MCP status is this directory's connector, run on 4 November 2026. ## Grades of companies with an open MCP server Companies with an open MCP server, by Ora grade. The table below carries the same counts and the grade bands as Ora publishes them. | Grade | Ora's band | Ora's label | With an open MCP server | All scored companies | | --- | --- | --- | --- | --- | | F | 0 to 27 | Unusable | 4 | 8 | | D | 28 to 47 | At Risk | 11 | 193 | | C | 48 to 69 | Needs Work | 36 | 433 | | B | 70 to 85 | Competitive | 25 | 239 | | A | 86 to 94 | Agent-Ready | 11 | 50 | | A+ | 95 to 100 | Leading | 7 | 10 | ## The twenty-five highest scores | Company | Category | Ora score | Tools | | --- | --- | --- | --- | | Telnyx telnyx.com | Infrastructure | 99 A+ | 6 | | Scholar Sidekick scholar-sidekick.com | Uncategorised | 98 A+ | 7 | | YouSpot youspot.com | CRM | 98 A+ | 171 | | Mailrith mailrith.com | Uncategorised | 97 A+ | 55 | | JobsPipe jobspipe.dev | Security | 96 A+ | 3 | | Primitive primitive.dev | Developer Tools | 96 A+ | 14 | | Ora ora.ai | Agent Tools | 95 A+ | 18 | | Agent Ready agent-ready.dev | Uncategorised | 94 A | 3 | | Channel3 trychannel3.com | E-commerce | 92 A | 6 | | Forter forter.com | Payments & Fintech | 92 A | 5 | | Xquik xquik.com | Developer Tools | 92 A | 4 | | Browser Use browser-use.com | Agent Tools | 91 A | 7 | | Exa exa.ai | Agent Tools | 91 A | 2 | | Upstash upstash.com | Infrastructure | 91 A | 2 | | Vaaya vaaya.ai | Developer Tools | 90 A | 14 | | Magic Hour magichour.ai | Gaming & Media | 89 A | 49 | | Easy itseasy.co | Payments & Fintech | 87 A | 3 | | Cerebrium cerebrium.ai | Infrastructure | 86 A | 3 | | emem emem.dev | Uncategorised | 85 B | 18 | | Hexclave hexclave.com | Developer Tools | 85 B | 2 | | Twilio twilio.com | Communication & Support | 85 B | 5 | | Cloudflare cloudflare.com | Infrastructure | 82 B | 2 | | Hugging Face huggingface.co | AI & ML | 82 B | 4 | | Kraken kraken.com | Uncategorised | 82 B | 3 | | Scento scento.com | Infrastructure | 82 B | 12 | ## Leaders by category Categories are the directory's; a category needs four scored companies with an open MCP server to appear. Scores are Ora's, and the figure after a name is that company's score. | Category | Scored | Median | Highest three | | --- | --- | --- | --- | | Developer Tools | 20 | 63.5 | Primitive 96, Xquik 92, Vaaya 90 | | Uncategorised | 16 | 67.5 | Scholar Sidekick 98, Mailrith 97, Agent Ready 94 | | Infrastructure | 13 | 71 | Telnyx 99, Upstash 91, Cerebrium 86 | | Agent Tools | 10 | 69.5 | Ora 95, Browser Use 91, Exa 91 | | E-commerce | 4 | 62 | Channel3 92, Zinc 81, App Store Tracker 43 | | AI & ML | 4 | 77.5 | Hugging Face 82, Clueso 78, Reka 77 | | Payments & Fintech | 4 | 79 | Forter 92, Easy 87, GuruHotel 71 | ## How this was read - Ora's cached score was read for 1,336 of the 1,336 directory companies on 5 November 2026: 323 through GET /api/score/{domain} and 610 from the same day's GET /api/leaderboard. 933 came back with a score and 403 with no cached score. - The reads are GET only, never a scan, never faster than one request a second (after the first minutes, one every 6.5 seconds) and each 429 was waited out for its Retry-After. Ora states 10 score reads a minute per IP. A per-domain read replaces the leaderboard figure where both exist. 168 of the 169 domains read both ways gave the same score; upstash.com had been scanned again in between, and the newer score is shown. - A cached score is the last scan Ora ran; its date is on each company's entry page. Companies Ora has never scanned have no score and a blank cell. - Ora's catalog changes over time, so a score read on another day can differ; [the checks that apply to an MCP server](https://agentmcpdirectory.com/mcp-checks/) are listed with their points. Next: [do companies with an MCP server score higher](https://agentmcpdirectory.com/ora-scores/mcp-servers-and-scores/), and [how to test your own server](https://agentmcpdirectory.com/test-your-mcp-server/). ## Testing your own MCP server [Why Ora is the pick for testing an MCP server, where it falls short and what else exists](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/ora-scores/index.md) ## Sources - [Ora leaderboard (GET /api/leaderboard)](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 5 November 2026 - [Ora API reference with the grade scale](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 5 November 2026 - [Official MCP Registry API, one of the sources of the directory](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Do MCP servers raise an Ora score? | Agent MCP Directory" description: "Do companies with an MCP server score higher on Ora? Median scores by MCP status and auth type for the directory, and how far to read the gap." canonical: https://agentmcpdirectory.com/ora-scores/mcp-servers-and-scores site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Ora scores" --- # Do MCP servers raise an Ora score? | Agent MCP Directory > Do companies with an MCP server score higher on Ora? Median scores by MCP status and auth type for the directory, and how far to read the gap. Source: https://agentmcpdirectory.com/ora-scores/mcp-servers-and-scores Site: Agent MCP Directory Last reviewed: 2026-11-05 # Do companies with an MCP server score higher on Ora? Among directory companies Ora has scored, 94 with an open MCP server have a median Ora score of 68, and 470 with none on record have 56. Ora's catalog gives a server direct credit, so part of the gap is built in. Ora scores a domain whether or not it ships an MCP server, and its catalog gives a server direct credit. This page sets out Ora's scores for the 933 directory companies Ora has scored, split by what the connector found, then says how far the numbers can be read. ## Median score by MCP status Median Ora score of the scored companies in each MCP status; groups with fewer than five scored companies are left out. The table has the same medians with the range. | MCP status | Scored companies | Median | Lowest | Highest | Grade B or better | With an OpenAPI file | | --- | --- | --- | --- | --- | --- | --- | | Verified | 94 | 68 | 9 | 99 | 43 (46%) | 23% | | Sign-in required | 324 | 69 | 16 | 96 | 161 (50%) | 19% | | None found | 470 | 56 | 30 | 89 | 84 (18%) | 3% | | Credential wall | 11 | 65 | 23 | 73 | 3 (27%) | 9% | | No answer | 33 | 64 | 37 | 85 | 8 (24%) | 6% | ## By auth type | Auth type | Scored companies | Median | | --- | --- | --- | | No authentication | 94 | 68 | | OAuth with client registration | 311 | 70 | | API key | 11 | 65 | | OAuth without client registration | 13 | 63 | ## What the catalog explains and what it does not - The catalog rewards a server directly: `mcp-server` is a required check worth 6 points, and 14 more checks, such as tool descriptions, parameter schemas and OAuth metadata, apply only once Ora finds a server ([GET /api/checks](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset)). A company with no server cannot earn them. [The list](https://agentmcpdirectory.com/mcp-checks/). - The directory was built from MCP registries, vendor documentation and Ora's own leaderboard, so the sample leans toward developer-facing companies. It is not a random draw of the web. - The groups differ in other ways Ora scores: the last column shows how often each group also has an OpenAPI file on record, one of the files Ora's checks look for. - Read the table as an association in this sample. It does not show that adding a server raises a score by a given amount. See [the highest scores](https://agentmcpdirectory.com/ora-scores/) and [how to test your own server](https://agentmcpdirectory.com/test-your-mcp-server/). ## Testing your own MCP server [Why Ora is the pick for testing an MCP server, where it falls short and what else exists](https://agentmcpdirectory.com/test-your-mcp-server/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/ora-scores/mcp-servers-and-scores/index.md) ## Sources - [Ora check catalog, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 5 November 2026 - [Ora leaderboard (GET /api/leaderboard)](https://ora.ai/api/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 5 November 2026 - [Ora API reference (llms-full.txt)](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=dataset), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Privacy | Agent MCP Directory" description: "What Agent MCP Directory collects: nothing from accounts, because there are none; its code sets no cookies and loads no third-party scripts." canonical: https://agentmcpdirectory.com/privacy site: "Agent MCP Directory" last_updated: 2026-11-04 section: "About" --- # Privacy | Agent MCP Directory > What Agent MCP Directory collects: nothing from accounts, because there are none; its code sets no cookies and loads no third-party scripts. Source: https://agentmcpdirectory.com/privacy Site: Agent MCP Directory Last reviewed: 2026-11-04 # Privacy ## What the site collects - No accounts and no sign-in. - The site's own code sets no cookies and loads no third-party scripts or fonts. - The hosting platform counts page views in aggregate and keeps ordinary server logs. - The search box filters a list in your browser; the text you type is not sent anywhere. - The API, the MCP server and the ask endpoint answer from the same public data files. They keep a request count per client address in memory to apply the rate limit and store no queries. - The contact and submit forms are not connected to a backend, so nothing typed into them is received or stored. ## Companies in the directory The directory lists companies and the public endpoints they or their registries publish. It holds no personal data about people. To have a row corrected or removed, use [corrections](https://agentmcpdirectory.com/corrections/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/privacy/index.md) Last reviewed 4 November 2026 --- --- title: "Sources read for this edition | Agent MCP Directory" description: "76 sources read for the 4 November 2026 edition, each marked primary or vendor with the date it was read. Specifications, changelogs and docs." canonical: https://agentmcpdirectory.com/sources site: "Agent MCP Directory" last_updated: 2026-11-05 section: "About" --- # Sources read for this edition | Agent MCP Directory > 76 sources read for the 4 November 2026 edition, each marked primary or vendor with the date it was read. Specifications, changelogs and docs. Source: https://agentmcpdirectory.com/sources Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sources read for this edition 76 sources were read for the 4 November 2026 edition: specifications, changelogs, registry APIs and vendor documentation. Each is marked primary when it comes from the maintainer of the thing described and vendor when a company describes its own product, which this directory labels as a claim. | Source | Kind | Read | | --- | --- | --- | | A2A joins the Agentic AI Foundation (27 Aug 2026) | primary | 2026-11-04 | | A2A specification | primary | 2026-11-04 | | agentskills.io | primary | 2026-11-04 | | Apify MCP server docs | vendor | 2026-11-04 | | Arcade blog index | vendor | 2026-11-04 | | Arcade: Smithery is now part of Arcade.dev (5 Aug 2026) | vendor | 2026-11-04 | | Arcade: ToolBench rescan, 90,000 MCP servers (30 Sep 2026) | vendor | 2026-11-04 | | Browserbase MCP introduction | vendor | 2026-11-04 | | Browserbase MCP setup | vendor | 2026-11-04 | | Claude connectors directory | primary | 2026-11-04 | | Claude: submit a connector to the directory | primary | 2026-11-04 | | Cloudflare AI Gateway pricing | primary | 2026-11-04 | | Cloudflare changelog: Agent Skills are files in the agent Workspace (29 Oct 2026) | primary | 2026-11-04 | | Cloudflare changelog: AI Gateway model aliases (4 Nov 2026) | primary | 2026-11-04 | | Cloudflare changelog: Browser Run adds WebMCP to Kitesurf, moves to document.modelContext (28 Sep 2026) | primary | 2026-11-04 | | Cloudflare changelog: Cloudflare API MCP server supports step-up authorization (19 Oct 2026) | primary | 2026-11-04 | | Cloudflare changelog: Cloudflare MCP servers no longer serve /sse (22 Oct 2026) | primary | 2026-11-04 | | Cloudflare changelog: MCP protocol detection and AI Security dashboard (12 Aug 2026) | primary | 2026-11-04 | | Cloudflare changelog: MCP server portals GA (24 Sep 2026) | primary | 2026-11-04 | | Cloudflare changelog: MCP server portals support MCP 2026-07-28 (25 Aug 2026) | primary | 2026-11-04 | | Cloudflare changelog: new AI Gateways require authentication (3 Nov 2026) | primary | 2026-11-04 | | Cloudflare changelog: private MCP server support for portals (22 Sep 2026) | primary | 2026-11-04 | | Cloudflare changelog: Workers OAuth Provider v1 (1 Oct 2026) | primary | 2026-11-04 | | Cloudflare developer changelog RSS | primary | 2026-11-04 | | Cloudflare MCP server portals docs | primary | 2026-11-04 | | Cloudflare: build a remote MCP server | primary | 2026-11-04 | | Composio MCP quickstart | vendor | 2026-11-04 | | Composio pricing | vendor | 2026-11-04 | | GitHub changelog: MCP servers in usage metrics API (22 Oct 2026) | primary | 2026-11-04 | | GitHub MCP Registry | primary | 2026-11-04 | | GitHub MCP Registry API, GET /v0/servers | primary | 2026-11-04 | | github/github-mcp-server | primary | 2026-11-04 | | Glama MCP API | vendor | 2026-11-04 | | Glama MCP connectors (remote servers) | vendor | 2026-11-04 | | Glama MCP servers directory | vendor | 2026-11-04 | | Glama pricing | vendor | 2026-11-04 | | Kong AI Gateway docs | vendor | 2026-11-04 | | MCP 2025-11-25 changelog | primary | 2026-11-04 | | MCP 2026-07-28 changelog | primary | 2026-11-04 | | MCP authorization, 2026-07-28 | primary | 2026-11-04 | | MCP blog index | primary | 2026-11-04 | | MCP deprecated features, 2026-07-28 | primary | 2026-11-05 | | MCP Registry: about | primary | 2026-11-05 | | MCP transports overview, 2026-07-28 | primary | 2026-11-04 | | Mintlify: Model Context Protocol | vendor | 2026-11-04 | | Model Context Protocol specification (latest, 2026-07-28) | primary | 2026-11-04 | | modelcontextprotocol/registry on GitHub | primary | 2026-11-04 | | Neon MCP server docs | vendor | 2026-11-04 | | nlweb-ai/NLWeb | primary | 2026-11-04 | | Official MCP Registry API, GET /v0/servers | primary | 2026-11-04 | | Official Ruby SDK for MCP reaches Tier 1 (30 Oct 2026) | primary | 2026-11-04 | | OpenAPI Specification (latest) | primary | 2026-11-05 | | Ora blog RSS | vendor | 2026-11-04 | | Ora blog: When a WebMCP tool returns an MCP App (30 Sep 2026) | vendor | 2026-11-04 | | Ora CLI docs | vendor | 2026-11-04 | | Ora leaderboard (crawl copy ora/crawl/2026-11-04/ora-leaderboard.json) | vendor | 2026-11-04 | | Ora: Introducing AgentReady.org (19 Oct 2026) | vendor | 2026-11-04 | | ora.ai/.well-known/mcp.json | vendor | 2026-11-04 | | Portkey home page | vendor | 2026-11-04 | | Portkey MCP Gateway docs | vendor | 2026-11-04 | | Portkey pricing | vendor | 2026-11-04 | | Shopify Storefront MCP docs | vendor | 2026-11-04 | | smithery.ai home page | vendor | 2026-11-04 | | Stripe MCP docs | vendor | 2026-11-04 | | Supabase MCP docs | vendor | 2026-11-04 | | The New MCP Roadmap (22 Aug 2026) | primary | 2026-11-04 | | Vercel AI Gateway pricing | primary | 2026-11-04 | | Vercel changelog: Vercel MCP renders deployments as an interactive card (2 Nov 2026) | primary | 2026-11-04 | | Vercel changelog: Vercel MCP supports Client ID Metadata Documents (2 Nov 2026) | primary | 2026-11-04 | | Vercel MCP docs | primary | 2026-11-04 | | Vercel: deploy MCP servers to Vercel | primary | 2026-11-04 | | webmachinelearning/webmcp | primary | 2026-11-04 | | webmcp.com (nekuda) | vendor | 2026-11-04 | | wild-card-ai/agents-json | primary | 2026-11-04 | | Zapier MCP docs | vendor | 2026-11-04 | | Zapier MCP product page | vendor | 2026-11-04 | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/sources/index.md) ## Sources - [A2A joins the Agentic AI Foundation (27 Aug 2026)](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 - [A2A specification](https://a2a-protocol.org/latest/specification/), read 4 November 2026 - [agentskills.io](https://agentskills.io/), read 4 November 2026 - [Apify MCP server docs](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Arcade blog index](https://www.arcade.dev/blog), read 4 November 2026 - [Arcade: Smithery is now part of Arcade.dev (5 Aug 2026)](https://www.arcade.dev/blog/smithery-joins-arcade), read 4 November 2026 - [Arcade: ToolBench rescan, 90,000 MCP servers (30 Sep 2026)](https://www.arcade.dev/blog/toolbench-rescan-90000-mcp-servers), read 4 November 2026 - [Browserbase MCP introduction](https://docs.browserbase.com/integrations/mcp/introduction), read 4 November 2026 - [Browserbase MCP setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 - [Claude connectors directory](https://claude.com/connectors), read 4 November 2026 - [Claude: submit a connector to the directory](https://claude.com/docs/connectors/building/submission), read 4 November 2026 - [Cloudflare AI Gateway pricing](https://developers.cloudflare.com/ai-gateway/reference/pricing/), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "Agent standards: MCP, WebMCP, A2A and more | Agent MCP Directory" description: "Eight agent-facing standards explained with sources: MCP, WebMCP, A2A, agents.json, NLWeb, Agent Skills, OpenAPI and CLIs as agent surfaces." canonical: https://agentmcpdirectory.com/standards site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # Agent standards: MCP, WebMCP, A2A and more | Agent MCP Directory > Eight agent-facing standards explained with sources: MCP, WebMCP, A2A, agents.json, NLWeb, Agent Skills, OpenAPI and CLIs as agent surfaces. Source: https://agentmcpdirectory.com/standards Site: Agent MCP Directory Last reviewed: 2026-11-04 # Standards for the act layer Eight reference entries for the standards an agent uses to act: MCP, WebMCP, A2A, agents.json, NLWeb, Agent Skills, OpenAPI and the command line. Each states what it is, who maintains it, its version and what it does not do, with dated sources. | Standard | Maintainer | Status and version | | --- | --- | --- | | Model Context Protocol | MCP maintainers under the Agentic AI Foundation | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | | WebMCP | W3C Web Machine Learning Community Group (editors from Microsoft and Google) | Draft specification; Chrome and Edge test it in an origin trial, Brave behind a flag, no Firefox or Safari implementation (nekuda FAQ, October 2026). | | Agent2Agent | A2A project, Growth Stage project at the Agentic AI Foundation (Linux Foundation-directed) | Specification 1.0.0 is the latest release; joined the Agentic AI Foundation on 27 Aug 2026. | | agents.json | Wildcard AI (started the project); maintainers listed in MAINTAINERS.md | Version 0.1.0, MIT licence; proposed location /.well-known/agents.json. | | NLWeb | Microsoft (repository nlweb-ai/NLWeb) | Active open-source project, MIT licence, about 6.3k stars; no tagged releases shown on 4 Nov 2026. | | Agent Skills | agentskills.io open standard (originated at Anthropic) | Open format with a published specification at agentskills.io; adopted across many agent clients. | | OpenAPI as an agent surface | OpenAPI Initiative (spec); each vendor for its own file | OpenAPI 3.x in wide use; agents.json and Kong's AI MCP Server build on it. | | CLIs as an agent surface | Each vendor | Common practice; AgentReady.org (launched 19 Oct 2026) lists "an MCP server or a CLI, at least one" as a MUST for the act layer. | These eight entries are reference pages. They are not scored, because a specification is not a product; the products that host and list MCP servers are scored on [the hosts page](https://agentmcpdirectory.com/hosts/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/index.md) ## Sources - [Model Context Protocol](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 - [WebMCP](https://github.com/webmachinelearning/webmcp), read 4 November 2026 - [Agent2Agent](https://a2a-protocol.org/latest/specification/), read 4 November 2026 - [agents.json](https://github.com/wild-card-ai/agents-json), read 4 November 2026 - [NLWeb](https://github.com/nlweb-ai/NLWeb), read 4 November 2026 - [Agent Skills](https://agentskills.io/), read 4 November 2026 - [CLIs as an agent surface](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Agent2Agent: what it is | Agent MCP Directory" description: "Agent2Agent: A protocol for agents to discover each other through an Agent Card and exchange tasks and messages. Read 4 November 2026 with sources." canonical: https://agentmcpdirectory.com/standards/a2a site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # Agent2Agent: what it is | Agent MCP Directory > Agent2Agent: A protocol for agents to discover each other through an Agent Card and exchange tasks and messages. Read 4 November 2026 with sources. Source: https://agentmcpdirectory.com/standards/a2a Site: Agent MCP Directory Last reviewed: 2026-11-04 # Agent2Agent Agent2Agent, maintained by A2A project, Growth Stage project at the Agentic AI Foundation (Linux Foundation-directed). A protocol for agents to discover each other through an Agent Card and exchange tasks and messages. Status: Specification 1.0.0 is the latest release; joined the Agentic AI Foundation on 27 Aug 2026. ## Fact sheet | Name | Agent2Agent (A2A) | | --- | --- | | Maintainer | A2A project, Growth Stage project at the Agentic AI Foundation (Linux Foundation-directed) | | What it is | A protocol for agents to discover each other through an Agent Card and exchange tasks and messages. | | Status and version | Specification 1.0.0 is the latest release; joined the Agentic AI Foundation on 27 Aug 2026. | | What it does not do | Does not define how an agent calls a plain API or a web page; it covers agent-to-agent tasks, not tool access. | ## Dated facts - A2A 1.0.0 defines three protocol bindings: JSON-RPC, gRPC and HTTP+JSON/REST, and allows custom bindings. ([a2a-protocol.org](https://a2a-protocol.org/latest/specification/), read 4 November 2026) - The Agent Card is served at /.well-known/agent-card.json and registered as a well-known URI in section 14.3. ([a2a-protocol.org](https://a2a-protocol.org/latest/specification/), read 4 November 2026) - A2A was accepted as a Growth Stage project at the Agentic AI Foundation on 27 Aug 2026, alongside MCP, goose and AGENTS.md. ([a2a-protocol.org](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), dated 27 August 2026, read 4 November 2026) - The spec page footer reads Copyright 2026 The Linux Foundation, Apache License 2.0. ([a2a-protocol.org](https://a2a-protocol.org/latest/specification/), read 4 November 2026) - Kong AI Gateway emits OpenTelemetry metrics for A2A traffic alongside MCP. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/agent-card.json | 10 of 7,470 (0.13%) | 48 of 3,368 (1.43%) | | /.well-known/agent.json | 6 of 7,461 (0.08%) | 14 of 3,366 (0.42%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). ## Compared with - [MCP vs A2A](https://agentmcpdirectory.com/compare/mcp-vs-a2a/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/a2a/index.md) ## Sources - [Agent2Agent specification or home](https://a2a-protocol.org/latest/specification/), read 4 November 2026 - [Agent2Agent: a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation](https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/), read 4 November 2026 - [Agent2Agent: developer.konghq.com/ai-gateway](https://developer.konghq.com/ai-gateway/), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Agent Skills: what it is | Agent MCP Directory" description: "Agent Skills: A folder with a SKILL.md file (name, description, instructions) plus optional scripts, references and assets that agents load on demand." canonical: https://agentmcpdirectory.com/standards/agent-skills site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # Agent Skills: what it is | Agent MCP Directory > Agent Skills: A folder with a SKILL.md file (name, description, instructions) plus optional scripts, references and assets that agents load on demand. Source: https://agentmcpdirectory.com/standards/agent-skills Site: Agent MCP Directory Last reviewed: 2026-11-04 # Agent Skills Agent Skills, maintained by agentskills.io open standard (originated at Anthropic). A folder with a SKILL.md file (name, description, instructions) plus optional scripts, references and assets that agents load on demand. Status: Open format with a published specification at agentskills.io; adopted across many agent clients. ## Fact sheet | Name | Agent Skills | | --- | --- | | Maintainer | agentskills.io open standard (originated at Anthropic) | | What it is | A folder with a SKILL.md file (name, description, instructions) plus optional scripts, references and assets that agents load on demand. | | Status and version | Open format with a published specification at agentskills.io; adopted across many agent clients. | | What it does not do | Does not execute anything by itself or expose remote tools; skills are instructions and files, often paired with an MCP server or CLI. | ## Dated facts - A skill is a folder containing SKILL.md with name and description at minimum. ([agentskills.io](https://agentskills.io/), read 4 November 2026) - Agents load skills by progressive disclosure: discovery (name and description), activation (full SKILL.md), execution. ([agentskills.io](https://agentskills.io/), read 4 November 2026) - The format was originally developed by Anthropic and released as an open standard. ([agentskills.io](https://agentskills.io/), read 4 November 2026) - Cloudflare's Agents SDK treats Agent Skills as files in the agent workspace (29 Oct 2026). ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-10-29-agent-skills-from-files/), dated 29 October 2026, read 4 November 2026) - Mintlify exposes skill.md files as MCP resources. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/agent-skills/index.json | 53 of 7,435 (0.71%) | 144 of 3,364 (4.28%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). ## Compared with - [Agent Skills vs MCP](https://agentmcpdirectory.com/compare/agent-skills-vs-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/agent-skills/index.md) ## Sources - [Agent Skills specification or home](https://agentskills.io/), read 4 November 2026 - [Agent Skills: developers.cloudflare.com/changelog/post/2026-10-29-agent-skills-from-files](https://developers.cloudflare.com/changelog/post/2026-10-29-agent-skills-from-files/), read 4 November 2026 - [Agent Skills: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "agents.json: what it is | Agent MCP Directory" description: "agents.json: An OpenAPI-based contract that describes flows (sequences of API calls) and links between actions so agents can call an API correctly." canonical: https://agentmcpdirectory.com/standards/agents-json site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # agents.json: what it is | Agent MCP Directory > agents.json: An OpenAPI-based contract that describes flows (sequences of API calls) and links between actions so agents can call an API correctly. Source: https://agentmcpdirectory.com/standards/agents-json Site: Agent MCP Directory Last reviewed: 2026-11-04 # agents.json agents.json, maintained by Wildcard AI (started the project); maintainers listed in MAINTAINERS.md. An OpenAPI-based contract that describes flows (sequences of API calls) and links between actions so agents can call an API correctly. Status: Version 0.1.0, MIT licence; proposed location /.well-known/agents.json. ## Fact sheet | Name | agents.json | | --- | --- | | Maintainer | Wildcard AI (started the project); maintainers listed in MAINTAINERS.md | | What it is | An OpenAPI-based contract that describes flows (sequences of API calls) and links between actions so agents can call an API correctly. | | Status and version | Version 0.1.0, MIT licence; proposed location /.well-known/agents.json. | | What it does not do | Does not define transport or auth beyond OpenAPI; not referenced by the MCP spec. | ## Dated facts - agents.json extends OpenAPI with descriptions and examples aimed at agent argument generation. ([github.com](https://github.com/wild-card-ai/agents-json), read 4 November 2026) - Flows are contracts of one or more API calls; links define how two actions connect. ([github.com](https://github.com/wild-card-ai/agents-json), read 4 November 2026) - The current version is 0.1.0 under the MIT licence. ([github.com](https://github.com/wild-card-ai/agents-json), read 4 November 2026) - The repository shows 75 commits on master. ([github.com](https://github.com/wild-card-ai/agents-json), read 4 November 2026) ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /agents.json | 0 of 7,485 (0%) | 0 of 3,366 (0%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). ## Compared with - [WebMCP vs agents.json](https://agentmcpdirectory.com/compare/webmcp-vs-agents-json/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/agents-json/index.md) ## Sources - [agents.json specification or home](https://github.com/wild-card-ai/agents-json), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "CLIs as an agent surface: what it is | Agent MCP Directory" description: "CLIs as an agent surface: A command-line tool, usually on npm, that an agent runs in a shell; the same questions apply to each: install path." canonical: https://agentmcpdirectory.com/standards/cli-as-agent-surface site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # CLIs as an agent surface: what it is | Agent MCP Directory > CLIs as an agent surface: A command-line tool, usually on npm, that an agent runs in a shell; the same questions apply to each: install path. Source: https://agentmcpdirectory.com/standards/cli-as-agent-surface Site: Agent MCP Directory Last reviewed: 2026-11-04 # CLIs as an agent surface CLIs as an agent surface, maintained by Each vendor. A command-line tool, usually on npm, that an agent runs in a shell; the same questions apply to each: install path, auth without a browser, machine-readable output, and whether it configures MCP. ## Fact sheet | Name | CLIs as an agent surface | | --- | --- | | Maintainer | Each vendor | | What it is | A command-line tool, usually on npm, that an agent runs in a shell; the same questions apply to each: install path, auth without a browser, machine-readable output, and whether it configures MCP. | | Status and version | Common practice; AgentReady.org (launched 19 Oct 2026) lists "an MCP server or a CLI, at least one" as a MUST for the act layer. | | What it does not do | Does not help agents that cannot run a shell, such as chat-only assistants; output formats differ by vendor. | ## Dated facts - Ora: npx ax audit needs no install and no account; --json gives a machine-readable report and --min-score fails CI when the score is below the threshold. ([ora.ai](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 4 November 2026) - Stripe: npm install -g @stripe/cli then stripe agent setup detects installed agents and configures the Stripe MCP server and skills; stripe docs reads docs in the terminal (v1.43.3+). ([docs.stripe.com](https://docs.stripe.com/mcp), read 4 November 2026) - Vercel: npx add-mcp https://mcp.vercel.com detects installed AI clients and configures Vercel MCP for each; -g installs globally. ([vercel.com](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026) - Supabase: the CLI serves a local MCP endpoint at http://localhost:54321/mcp. ([supabase.com](https://supabase.com/docs/guides/getting-started/mcp), read 4 November 2026) - Neon: npx neon@latest init sets up the MCP server, agent skills and a linked project; npx neon@latest mcp writes the MCP config. ([neon.com](https://neon.com/docs/ai/neon-mcp-server), read 4 November 2026) - Shopify: the Storefront MCP page does not mention the Shopify CLI; catalog and cart tools moved from /api/mcp to /api/ucp/mcp. ([shopify.dev](https://shopify.dev/docs/apps/build/storefront-mcp), read 4 November 2026) - GitHub: the GitHub MCP server ships as a Docker image ghcr.io/github/github-mcp-server and a remote at api.githubcopilot.com/mcp/, with a --read-only flag. ([github.com](https://github.com/github/github-mcp-server), read 4 November 2026) ## Seen in the directory 36 companies in the directory have a CLI package on record, out of 1,336. The figure is a floor: a package is checked only where a source names it. See [the CLI guide](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Compared with - [CLIs vs MCP](https://agentmcpdirectory.com/compare/cli-as-agent-surface-vs-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/cli-as-agent-surface/index.md) ## Sources - [CLIs as an agent surface specification or home](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 4 November 2026 - [CLIs as an agent surface: docs.stripe.com/mcp](https://docs.stripe.com/mcp), read 4 November 2026 - [CLIs as an agent surface: vercel.com/docs/agent-resources/vercel-mcp](https://vercel.com/docs/agent-resources/vercel-mcp), read 4 November 2026 - [CLIs as an agent surface: supabase.com/docs/guides/getting-started/mcp](https://supabase.com/docs/guides/getting-started/mcp), read 4 November 2026 - [CLIs as an agent surface: neon.com/docs/ai/neon-mcp-server](https://neon.com/docs/ai/neon-mcp-server), read 4 November 2026 - [CLIs as an agent surface: shopify.dev/docs/apps/build/storefront-mcp](https://shopify.dev/docs/apps/build/storefront-mcp), read 4 November 2026 - [CLIs as an agent surface: github.com/github/github-mcp-server](https://github.com/github/github-mcp-server), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Model Context Protocol: what it is | Agent MCP Directory" description: "Model Context Protocol: A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts." canonical: https://agentmcpdirectory.com/standards/mcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Standards" --- # Model Context Protocol: what it is | Agent MCP Directory > Model Context Protocol: A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts. Source: https://agentmcpdirectory.com/standards/mcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # Model Context Protocol Model Context Protocol, maintained by MCP maintainers under the Agentic AI Foundation. A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. Status: Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. ## Fact sheet | Name | Model Context Protocol (MCP) | | --- | --- | | Maintainer | MCP maintainers under the Agentic AI Foundation | | What it is | A JSON-RPC 2.0 protocol between hosts, clients and servers; servers offer tools, resources and prompts, and clients may offer elicitation. | | Status and version | Current revision 2026-07-28 (released 28 Jul 2026); prior revision 2025-11-25. Registry in preview with API v0.1 frozen since 24 Oct 2025. | | What it does not do | Does not grade servers, verify registry entries, or prescribe a .well-known discovery file in the 2026-07-28 core spec; server cards are still Working Group work. | ## Dated facts - The 2026-07-28 revision removes the initialize handshake and the Mcp-Session-Id header; every request carries protocol version and client capabilities in \_meta. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), dated 28 July 2026, read 4 November 2026) - Servers MUST implement server/discover to advertise supported versions, capabilities and identity. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - The standard transports are stdio and Streamable HTTP. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026) - HTTP+SSE is listed as a deprecated feature since 2025-03-26, with Streamable HTTP as its replacement. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/deprecated), dated 26 March 2025, read 5 November 2026) - The 2026-07-28 revision adds a feature lifecycle and deprecation policy with Active, Deprecated and Removed states and a minimum twelve-month deprecation window. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - MCP servers MUST implement OAuth 2.0 Protected Resource Metadata (RFC 9728); clients and authorization servers SHOULD support Client ID Metadata Documents. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - Dynamic Client Registration (RFC 7591) is deprecated as a registration mechanism and kept for backwards compatibility. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Clients MUST send the resource parameter (RFC 8707) in authorization and token requests and MUST validate a present iss parameter (RFC 9207). ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026) - tools/list, prompts/list and resources/list results now carry required ttlMs and cacheScope fields. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - Roots, Sampling and Logging are deprecated in 2026-07-28. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026) - The 2025-11-25 revision added Client ID Metadata Documents, URL mode elicitation, icons and experimental tasks. ([modelcontextprotocol.io](https://modelcontextprotocol.io/specification/2025-11-25/changelog), dated 25 November 2025, read 4 November 2026) - The registry namespaces servers with reverse DNS or io.github. and verifies them by GitHub OAuth or OIDC, DNS or HTTP. ([github.com](https://github.com/modelcontextprotocol/registry), read 4 November 2026) ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /.well-known/mcp.json | 19 of 7,470 (0.25%) | 66 of 3,366 (1.96%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). ## Compared with - [MCP vs A2A](https://agentmcpdirectory.com/compare/mcp-vs-a2a/) - [MCP vs WebMCP](https://agentmcpdirectory.com/compare/mcp-vs-webmcp/) - [NLWeb vs MCP](https://agentmcpdirectory.com/compare/nlweb-vs-mcp/) - [Agent Skills vs MCP](https://agentmcpdirectory.com/compare/agent-skills-vs-mcp/) - [CLIs vs MCP](https://agentmcpdirectory.com/compare/cli-as-agent-surface-vs-mcp/) - [OpenAPI vs MCP](https://agentmcpdirectory.com/compare/openapi-as-agent-surface-vs-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/mcp/index.md) ## Sources - [Model Context Protocol specification or home](https://modelcontextprotocol.io/specification/latest), read 4 November 2026 - [Model Context Protocol: modelcontextprotocol.io/specification/2026-07-28/changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog), read 4 November 2026 - [Model Context Protocol: modelcontextprotocol.io/specification/2026-07-28/basic/transports](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), read 4 November 2026 - [Model Context Protocol: modelcontextprotocol.io/specification/2026-07-28/deprecated](https://modelcontextprotocol.io/specification/2026-07-28/deprecated), read 5 November 2026 - [Model Context Protocol: modelcontextprotocol.io/specification/2026-07-28/basic/authorization](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization), read 4 November 2026 - [Model Context Protocol: modelcontextprotocol.io/specification/2025-11-25/changelog](https://modelcontextprotocol.io/specification/2025-11-25/changelog), read 4 November 2026 - [Model Context Protocol: github.com/modelcontextprotocol/registry](https://github.com/modelcontextprotocol/registry), read 4 November 2026 Last reviewed 5 November 2026 --- --- title: "NLWeb: what it is | Agent MCP Directory" description: "NLWeb: Open protocols and a Python reference implementation for conversational interfaces on websites, returning Schema.org JSON." canonical: https://agentmcpdirectory.com/standards/nlweb site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # NLWeb: what it is | Agent MCP Directory > NLWeb: Open protocols and a Python reference implementation for conversational interfaces on websites, returning Schema.org JSON. Source: https://agentmcpdirectory.com/standards/nlweb Site: Agent MCP Directory Last reviewed: 2026-11-04 # NLWeb NLWeb, maintained by Microsoft (repository nlweb-ai/NLWeb). Open protocols and a Python reference implementation for conversational interfaces on websites, returning Schema.org JSON; every instance is also an MCP server. Status: Active open-source project, MIT licence, about 6.3k stars; no tagged releases shown on 4 Nov 2026. ## Fact sheet | Name | NLWeb | | --- | --- | | Maintainer | Microsoft (repository nlweb-ai/NLWeb) | | What it is | Open protocols and a Python reference implementation for conversational interfaces on websites, returning Schema.org JSON; every instance is also an MCP server. | | Status and version | Active open-source project, MIT licence, about 6.3k stars; no tagged releases shown on 4 Nov 2026. | | What it does not do | Does not document fixed /ask or /mcp URL paths on the repository page; CI/CD pipelines are not included. | ## Dated facts - Every NLWeb instance acts as an MCP server and supports a core method called ask that takes a natural-language question. ([github.com](https://github.com/nlweb-ai/NLWeb), read 4 November 2026) - Responses are JSON using Schema.org vocabulary. ([github.com](https://github.com/nlweb-ai/NLWeb), read 4 November 2026) - The repository is MIT licensed with about 6.3k stars and 694 forks on 4 Nov 2026. ([github.com](https://github.com/nlweb-ai/NLWeb), read 4 November 2026) - Support contact is NLWebSup@microsoft.com and contributor links point to microsoft/nlweb. ([github.com](https://github.com/nlweb-ai/NLWeb), read 4 November 2026) ## Compared with - [NLWeb vs MCP](https://agentmcpdirectory.com/compare/nlweb-vs-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/nlweb/index.md) ## Sources - [NLWeb specification or home](https://github.com/nlweb-ai/NLWeb), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "OpenAPI as an agent surface: what it is | Agent MCP Directory" description: "OpenAPI as an agent surface: A machine-readable description of an HTTP API that agents and tool generators read to call endpoints without an MCP server." canonical: https://agentmcpdirectory.com/standards/openapi-as-agent-surface site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # OpenAPI as an agent surface: what it is | Agent MCP Directory > OpenAPI as an agent surface: A machine-readable description of an HTTP API that agents and tool generators read to call endpoints without an MCP server. Source: https://agentmcpdirectory.com/standards/openapi-as-agent-surface Site: Agent MCP Directory Last reviewed: 2026-11-04 # OpenAPI as an agent surface OpenAPI as an agent surface, maintained by OpenAPI Initiative (spec); each vendor for its own file. A machine-readable description of an HTTP API that agents and tool generators read to call endpoints without an MCP server. Status: OpenAPI 3.x in wide use; agents.json and Kong's AI MCP Server build on it. ## Fact sheet | Name | OpenAPI as an agent surface | | --- | --- | | Maintainer | OpenAPI Initiative (spec); each vendor for its own file | | What it is | A machine-readable description of an HTTP API that agents and tool generators read to call endpoints without an MCP server. | | Status and version | OpenAPI 3.x in wide use; agents.json and Kong's AI MCP Server build on it. | | What it does not do | Does not carry agent auth flows or tool descriptions written for models; agents must find the file, usually through a link. | ## Dated facts - Ora's lab found (AgentReady launch post, 19 Oct 2026) that agents reached openapi.json in 21 percent of traced runs on sites that ship one, and 97 percent of those fetches arrived through a link, not a guessed path. ([ora.ai](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), dated 19 October 2026, read 4 November 2026) - AgentReady.org lists a public API with OpenAPI as a SHOULD for the act layer, next to the MUST of an MCP server or a CLI. ([ora.ai](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), dated 19 October 2026, read 4 November 2026) - Kong's AI MCP Server entity turns existing APIs into MCP tools. ([developer.konghq.com](https://developer.konghq.com/ai-gateway/), read 4 November 2026) - agents.json is defined as an extension of OpenAPI. ([github.com](https://github.com/wild-card-ai/agents-json), read 4 November 2026) - Stripe's MCP server exposes API methods through stripe\_api\_read and stripe\_api\_write rather than one tool per endpoint. ([docs.stripe.com](https://docs.stripe.com/mcp), read 4 November 2026) ## Seen in the shared crawl | Path | Top 10,000 found | Ora leaderboard found | | --- | --- | --- | | /openapi.json | 21 of 7,472 (0.28%) | 78 of 3,369 (2.32%) | | /openapi.yaml | 10 of 7,503 (0.13%) | 22 of 3,378 (0.65%) | A path counts only when the answer is the right kind of document. Many sites answer these paths with an ordinary web page, which is not counted. See [the census](https://agentmcpdirectory.com/census/). ## Compared with - [OpenAPI vs MCP](https://agentmcpdirectory.com/compare/openapi-as-agent-surface-vs-mcp/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/openapi-as-agent-surface/index.md) ## Sources - [OpenAPI as an agent surface specification or home](https://github.com/wild-card-ai/agents-json), read 4 November 2026 - [OpenAPI as an agent surface: ora.ai/blog/agentready-launch](https://ora.ai/blog/agentready-launch?view=full&utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 4 November 2026 - [OpenAPI as an agent surface: developer.konghq.com/ai-gateway](https://developer.konghq.com/ai-gateway/), read 4 November 2026 - [OpenAPI as an agent surface: docs.stripe.com/mcp](https://docs.stripe.com/mcp), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "WebMCP: what it is | Agent MCP Directory" description: "WebMCP: A browser API that lets a page register JavaScript functions as tools, with descriptions and schemas, that an in-browser agent can call." canonical: https://agentmcpdirectory.com/standards/webmcp site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Standards" --- # WebMCP: what it is | Agent MCP Directory > WebMCP: A browser API that lets a page register JavaScript functions as tools, with descriptions and schemas, that an in-browser agent can call. Source: https://agentmcpdirectory.com/standards/webmcp Site: Agent MCP Directory Last reviewed: 2026-11-04 # WebMCP WebMCP, maintained by W3C Web Machine Learning Community Group (editors from Microsoft and Google). A browser API that lets a page register JavaScript functions as tools, with descriptions and schemas, that an in-browser agent can call. Status: Draft specification; Chrome and Edge test it in an origin trial, Brave behind a flag. ## Fact sheet | Name | WebMCP | | --- | --- | | Maintainer | W3C Web Machine Learning Community Group (editors from Microsoft and Google) | | What it is | A browser API that lets a page register JavaScript functions as tools, with descriptions and schemas, that an in-browser agent can call. | | Status and version | Draft specification; Chrome and Edge test it in an origin trial, Brave behind a flag, no Firefox or Safari implementation (nekuda FAQ, October 2026). | | What it does not do | Does not work without a browser agent that reads the page; does not replace a server-side MCP endpoint; the declarative form-based API is only being explored. | ## Dated facts - The draft documents document.modelContext with registerTool(), getTools(), executeTool() and a toolchange event. ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) - The imperative registerTool() API is in the spec; a declarative API built from HTML forms is being explored and is not in it. ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) - WebMCP is on by default in top-level windows and same-origin iframes; cross-origin iframes need the Permissions Policy allow="tools". ([github.com](https://github.com/webmachinelearning/webmcp), read 4 November 2026) - The explainer was first published on 13 Aug 2025; TypeScript definitions ship as the webmcp-types npm package. ([github.com](https://github.com/webmachinelearning/webmcp), dated 13 August 2025, read 4 November 2026) - webmcp.com, maintained by nekuda, reported 8,556 verified sites and 52,491 indexed tools. ([webmcp.com](https://webmcp.com/), read 4 November 2026) - nekuda reports that ChatGPT's desktop app began using WebMCP tools in its built-in browser on 25 Aug 2026. ([webmcp.com](https://webmcp.com/), dated 25 August 2026, read 4 November 2026) - Cloudflare Browser Run moved its WebMCP support to document.modelContext on 28 Sep 2026. ([developers.cloudflare.com](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), dated 28 September 2026, read 4 November 2026) - Mintlify ships WebMCP tools such as search\_docs and read\_page on Pro and Enterprise plans. ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026) ## Seen in the shared crawl The shared crawl looks for WebMCP in the initial HTML of each home page. It found a WebMCP hint on 25 of 7,545 home pages in the Tranco top 10,000 and on 59 of 3,393 on Ora's leaderboard. ## Compared with - [MCP vs WebMCP](https://agentmcpdirectory.com/compare/mcp-vs-webmcp/) - [WebMCP vs agents.json](https://agentmcpdirectory.com/compare/webmcp-vs-agents-json/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/standards/webmcp/index.md) ## Sources - [WebMCP specification or home](https://github.com/webmachinelearning/webmcp), read 4 November 2026 - [WebMCP: webmcp.com](https://webmcp.com/), read 4 November 2026 - [WebMCP: developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api](https://developers.cloudflare.com/changelog/post/2026-09-28-webmcp-api/), read 4 November 2026 - [WebMCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 Last reviewed 4 November 2026 --- --- title: "Terms of use | Agent MCP Directory" description: "Terms for using Agent MCP Directory: information only, no warranty, reuse of the data with the citation line, and trademarks belong to their owners." canonical: https://agentmcpdirectory.com/terms site: "Agent MCP Directory" last_updated: 2026-11-04 section: "About" --- # Terms of use | Agent MCP Directory > Terms for using Agent MCP Directory: information only, no warranty, reuse of the data with the citation line, and trademarks belong to their owners. Source: https://agentmcpdirectory.com/terms Site: Agent MCP Directory Last reviewed: 2026-11-04 # Terms ## Use of the site - The site is information, read on the dates shown. It is not advice and comes with no warranty. A server that answered on 4 November 2026 may not answer today. - The data downloads may be reused with the citation line on [the data page](https://agentmcpdirectory.com/data/). - Company and product names belong to their owners and appear only to identify them. A row is a statement about public endpoints, not an endorsement. - Do not use the connector log or endpoint list to attack a server. The directory itself never calls a tool. Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/terms/index.md) Last reviewed 4 November 2026 --- --- title: "Test your MCP server for agents | Agent MCP Directory" description: "Test your MCP server for agents: Ora runs 28 MCP checks and needs no account. Why it is the pick, where it falls short, and six alternatives." canonical: https://agentmcpdirectory.com/test-your-mcp-server site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Testing" --- # Test your MCP server for agents | Agent MCP Directory > Test your MCP server for agents: Ora runs 28 MCP checks and needs no account. Why it is the pick, where it falls short, and six alternatives. Source: https://agentmcpdirectory.com/test-your-mcp-server Site: Agent MCP Directory Last reviewed: 2026-11-05 # Test your MCP server for agents Scan your MCP server with Ora first: 28 of its 132 public checks apply to an MCP server URL, and it needs no account. Use MCP Inspector to debug single calls and a security scanner for injection risks. Ora's limits are listed on this page, with alternatives for what it does not cover. Ora The pick for a first check of an MCP server, on the facts read on 5 November 2026. [Ora's scan documentation](https://ora.ai/docs?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide). - Where it stops: public URLs only, no repeat-scan data published, the fixing product behind a waitlist and 10 scans a minute per IP. [The full list](#limits). ## Why Ora is the pick - It scans an MCP server URL directly. Ora's API reference says the `url` parameter of `POST /api/scan` takes a domain, an MCP server URL or an MCP App URL, and the `scan_domain` tool adds an optional `mcpUrl` ([Ora API reference, read 5 November 2026](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - Its catalog is public and counts the MCP part. The catalog's `applicability` field splits the 28 checks that name MCP as a target: 14 apply only where Ora finds an MCP server (`mcp`), 4 only to an MCP App (`mcp-app`) and 10 to every scan (`all`), among them the ARD catalog and the registry listing ([GET /api/checks, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). [The list](https://agentmcpdirectory.com/mcp-checks/). - Check sets depend on the kind of server. When a domain ships more than one MCP server, Ora classifies each as product, docs or other and scores it with a check set for that kind ([Ora API reference](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). Its own two servers declare their kind in a server card: product for `ora.ai/api/mcp` and docs for `ora.ai/api/docs/mcp` ([main card](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), [docs card](https://ora.ai/api/docs/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - A failing check says what to do. Every one of the 28 MCP checks carries a recommendation in the catalog, and `POST /api/scan/checks` re-runs only the check ids you name, never from a cache, so a fix can be confirmed without a full scan ([Ora API reference](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - It runs from outside, as an agent would. Ora fetches public URLs only; a local server needs a tunnel, and Ora's CLI can start one with `--tunnel-cmd` ([Ora MCP page](https://ora.ai/mcp?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), [Ora CLI docs](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - It costs nothing to start. Ora's pricing endpoint lists one Free plan at 0 USD with 10 scans per minute and unlimited score lookups ([pricing, read 5 November 2026](https://ora.ai/pricing?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - It is an open MCP server itself. The connector listed 18 tools on `https://ora.ai/api/mcp` on 4 November 2026 with no credentials, including `scan_domain`, `run_checks` and `list_checks`, so an agent can test a server on your behalf ([the row](https://agentmcpdirectory.com/directory/ora-ai/)). ## What Ora does not do - Public URLs only. Ora cannot scan private or internal sites or anything behind a login, and a scan of an MCP server that requires authentication returns `MCP_AUTH_REQUIRED` with no score or grade ([Ora llms.txt, read 5 November 2026](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). In this directory 533 companies answered with a sign-in challenge, and a server like those cannot be scored from outside. - It is not a security audit. Ora's documentation lists security audits among the uses it is not suited for ([Ora API reference](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)); the scanners below cover prompt injection and tool poisoning. - No repeat-scan data is published. Ora says the same scan run twice converges within a couple of points, in its Deep Scan post of 8 April 2026, and shows no repeat-scan measurements ([Ora blog](https://ora.ai/blog/introducing-deep-scan?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - The limit is 10 a minute. Ora's pricing lists unlimited score lookups, while its MCP page says 10 scans and 10 score reads a minute per IP ([pricing](https://ora.ai/pricing?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), [Ora MCP page](https://ora.ai/mcp?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). Ora's API reference says a 429 answer carries a Retry-After header to wait for ([Ora API reference](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - The score moves when the checks move. Ora's own FAQ answers a changed score with "the checks moved" and says rescanning scores you against the current set ([Ora MCP page](https://ora.ai/mcp?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). - The fixing product is behind a waitlist. Ora's home page says it fixes what it finds and is rolling access out slowly; the scan, the per-check recommendations and `generate_agent_files` need no waitlist ([Ora home page, read 5 November 2026](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide)). ## Other ways to test an MCP server Each row below says what the tool's own page says it does, labelled as the vendor's claim, and what it needs. Each tool answers its own question, and its scores or findings are not comparable with Ora's. | Tool | Use it for | What its own page says | What it needs | | --- | --- | --- | --- | | Ora | A first check of how agents find, read and use the server, with a fix for each failing check. | Ora runs 28 MCP checks and scores a docs server and a product server on different bars. | A public URL. No account. | | MCP Inspector | Debugging one server by hand, or a connect, list, call, assert loop in a shell or CI job. | The project describes it as a developer tool for inspecting MCP servers, shipped as one package with a web UI, a scriptable CLI, a terminal UI and an experimental connection CLI. It keeps OAuth tokens in the operating system's keychain where there is one. | Node: npx @modelcontextprotocol/inspector. The README describes inspecting servers, not scoring them. | | Manufact (mcp-use) | Debugging in the browser and a quality score, if the server is hosted with Manufact. | Manufact says it offers an MCP Quality Score, a server tunnel for local MCP servers and an mcp-use Inspector for debugging in the browser. Its catalog ranks servers by its own quality score. | Manufact Cloud for the hosted features; the mcp-use SDK is open source. | | Snyk Agent Scan | Checking MCP servers, tools, prompts, resources and skills for prompt injection and other risks. | Snyk calls it a security scanner for AI agents, MCP servers and agent skills. It is open source under Apache-2.0 and accepts a path to OAuth tokens for remote servers behind sign-in. | A Snyk API token before any scan; component details go to the Agent Scan API. Installed with uvx, not npm. | | Cisco MCP Scanner | Checking an MCP server's tools, prompts and resources for malicious content, offline if you accept YARA rules alone. | Cisco combines YARA rules, an LLM judge and the Cisco AI Defense inspect API; the analyzers can run one at a time, and the README shows a YARA-only CI example that needs no API keys. | Python. The API analyzer needs Cisco AI Defense access and the LLM analyzer a model provider. | | Enkrypt AI MCP Scanner | A commercial inventory of MCP servers and tools with risk findings and a remediation plan. | Enkrypt AI says the scanner discovers tools, analyzes capabilities and permissions, checks for direct and indirect prompt injection and flags over-privilege. | A commercial relationship; the pages read publish no scanner price. | | Akto MCP Security | Finding MCP servers in a company's networks and red-teaming them for prompt injection and tool poisoning. | Akto says its module discovers MCP servers and their agentic components, runs targeted red teaming and monitors them. Its recon scans only the IP ranges an admin enters. | Akto Argus, its platform; the pages read publish no price. | - To see whether agents can find, read and use the server: Ora, then fix what it names. - To debug a single call or script a smoke test: MCP Inspector. - To look for prompt injection, tool poisoning and over-privilege: Snyk Agent Scan or Cisco MCP Scanner when open source and a local run matter, Enkrypt AI or Akto when a commercial product and a report matter. ## Run the check 1. Put the server at a public URL. For a local server, Ora's CLI audits localhost through a tunnel you start with `--tunnel-cmd`. 2. Scan the server URL with Ora, from the web page, from `POST /api/scan` or with the `scan_domain` tool. 3. Poll `GET /api/score/{domain}` until `analysisStatus` is `complete`; deep checks finish after the first answer. 4. Fix the failing checks in order of points, then re-run only those ids with `POST /api/scan/checks`. 5. Gate releases with `npx ax@0.10 audit --min-score `, which exits non-zero below the threshold. ```bash curl -s -X POST https://ora.ai/api/scan -H 'content-type: application/json' -d '{"url":"https://your-server.example/mcp"}' ``` The call above is the documented request, shown for reference; this directory has never sent it. ## What the directory shows Ora has a cached score for 933 of the 1,336 companies in this directory, read on 5 November 2026. Of the 263 companies with an open MCP server, 94 have a cached score, with a median of 68. [The scores by category](https://agentmcpdirectory.com/ora-scores/) and [what moves them](https://agentmcpdirectory.com/ora-scores/mcp-servers-and-scores/). Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/test-your-mcp-server/index.md) ## Sources - [Ora API reference (llms-full.txt)](https://ora.ai/llms-full.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora llms.txt](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora check catalog, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora main MCP server card](https://ora.ai/api/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora docs MCP server card](https://ora.ai/api/docs/mcp/server-card?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora MCP page and FAQ](https://ora.ai/mcp?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora CLI documentation](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora pricing](https://ora.ai/pricing?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora: Introducing Deep Scan](https://ora.ai/blog/introducing-deep-scan?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [Ora home page](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=guide), read 5 November 2026 - [MCP Inspector repository README](https://github.com/modelcontextprotocol/inspector), read 5 November 2026 - [Manufact home page](https://manufact.com/), read 5 November 2026 - [Snyk Agent Scan repository](https://github.com/snyk/agent-scan), read 5 November 2026 - [Cisco MCP Scanner repository](https://github.com/cisco-ai-defense/mcp-scanner), read 5 November 2026 - [Enkrypt AI MCP Scanner page](https://www.enkryptai.com/product/mcp-scanner), read 5 November 2026 - [Akto MCP Security page](https://www.akto.io/mcp-security), read 5 November 2026 - [Akto MCP Recon documentation](https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/others/mcp-recon.md), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP infrastructure vendors by type | Agent MCP Directory" description: "64 vendors in seven layers around MCP servers: hosts, registries, gateways, auth, scanners, SDKs and connectors, each profile dated and sourced." canonical: https://agentmcpdirectory.com/vendors site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP infrastructure vendors by type | Agent MCP Directory > 64 vendors in seven layers around MCP servers: hosts, registries, gateways, auth, scanners, SDKs and connectors, each profile dated and sourced. Source: https://agentmcpdirectory.com/vendors Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP infrastructure vendors 64 vendors from seven layers around MCP servers, read on 5 November 2026: 10 hosts and runtimes, 8 registries and directories, 13 gateways and proxies, 9 auth providers, 6 security scanners, 8 SDKs and frameworks and 10 connector platforms. Two agent-readiness checks sit beside each vendor's domain. ## How the list was built The list is one row per company. A company that sells more than one layer is typed by its main one, and the others show on its profile as secondary layers and in the second table below. Each profile rests on 468 dated facts in all, drawn from 155 pages read on 5 November 2026. No vendor's server was connected to for this section, so every statement is as documented by the vendor, with the page it came from. A vendor is listed only when its own site states what it does. The 16 products profiled on the hosts page are all here, folded into one row per company, and the separate directory of 1,336 companies is not repeated. The names came from: - The products already profiled on the hosts page, one row per company: Cloudflare AI Gateway and Vercel AI Gateway sit inside the Cloudflare and Vercel rows, and Smithery sits inside the Arcade row. - The MCP project's own pages: the SDK page, which lists the official SDKs (one row), and the registry page, which names the registry's backers. - Partner, comparison and integration pages on vendors' own sites, such as the guides of an authorization provider that name the hosts and frameworks they work with. - Search roundups and comparison posts, read as leads only. Each name found there was read again on its own site, and no fact in a profile comes from a roundup. - Companies that were already known to sell in this layer, checked on their own documentation and pricing pages. Prices are shown only where a page gave one, with the date it was read. Merge, StackOne, Mintive, Obot, Glama, Akto and Enkrypt AI are shown as "no published price", because the pages read gave none; where nothing was recorded either way the cell says "price not read". ## The seven layers | Layer | What it is | Vendors | Also cover it | | --- | --- | --- | --- | | Hosts and runtimes | Vendors that run a remote MCP server for you: hosting platforms, runtimes and deploy tools. | 10 | 7 | | Registries and directories | Vendors that list MCP servers so that a client or an agent can find them. | 8 | 6 | | Gateways and proxies | Vendors of gateways, proxies and control planes that sit between MCP clients and servers. | 13 | 11 | | Auth providers | Vendors that sign agents and users in and issue the tokens a remote MCP server checks. | 9 | 5 | | Security scanners | Vendors that check MCP servers, tools and tool descriptions for risk. | 6 | 0 | | SDKs and frameworks | Vendors of libraries and frameworks for building MCP servers and clients. | 8 | 5 | | Connector platforms | Vendors that give agents ready-made, authenticated access to many apps through MCP. | 10 | 2 | ## Hosts and runtimes | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Alpic | host or runtime also SDK or framework | Alpic is a cloud platform that deploys MCP servers and ChatGPT or Claude apps with no configuration, adds AI-specific analytics and session replay, and maintains Skybridge, an open-source MCP Apps framework. | none recorded | per request as of 2026-11-05 | 86 (A) scanned 2026-10-23 | 47 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Apify | host or runtime also connector platform | Apify runs a hosted MCP server that lets agents search, call and pay for Apify Actors, the scrapers and automations on its platform, with tool sets chosen through URL parameters. | none recorded | usage of Actors as of 2026-11-05 | 96 (A+) scanned 2026-11-04 | 73 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | AWS | host or runtime also gateway or proxy, auth provider | Amazon Bedrock AgentCore runs MCP servers as containers in AgentCore Runtime and offers AgentCore Gateway, a managed entry point that turns APIs and Lambda functions into tools for agents, priced per call. | 1 supported MCP | per vCPU-hour and GB-hour; per 1,000 invocations as of 2026-11-05 | 60 (C) scanned 2026-10-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Browserbase | host or runtime | Browserbase runs cloud browsers for agents and an MCP server, built on Stagehand, that gives any MCP client a browser it can drive with natural-language commands and persistent sessions. | none recorded | per plan as of 2026-11-05 | 84 (B) scanned 2026-11-03 | 31 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Cloudflare | host or runtime also gateway or proxy, auth provider | Cloudflare hosts remote MCP servers on Workers through the Agents SDK, ships the Workers OAuth Provider for both sides of MCP authorization, and fronts servers with MCP server portals and AI Gateway. | 4 supported MCP | Workers Paid minimum as of 2026-11-05 | 82 (B) scanned 2026-11-05 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Google Cloud Run | host or runtime | Google Cloud Run hosts remote MCP servers built with the official SDKs or FastMCP as streamable-HTTP services, with access controlled by IAM and a local proxy command for developer clients. | 1 supported MCP | price not read | 51 (C) scanned 2026-10-28 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Manufact | host or runtime also SDK or framework | Manufact pairs mcp-use, an open-source TypeScript and Python SDK for MCP servers and apps, with Manufact Cloud, which deploys MCP servers from GitHub and tests them across ChatGPT, Claude and coding agents. | none recorded | open source; credits plus usage as of 2026-11-05 | 83 (B) scanned 2026-11-04 | 60 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Mintlify | host or runtime | Mintlify generates and hosts a search MCP server for every docs site it builds, exposes skill files as MCP resources, registers WebMCP tools on Pro plans, and scores docs sites for agent readability. | 1 supported, 1 partial WebMCP, Agent Skills | included from Starter; Pro and Enterprise as of 2026-11-05 | 74 (B) scanned 2026-11-05 | 47 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Netlify | host or runtime | Netlify hosts stateless MCP servers as serverless functions answering at /mcp, publishes a deploy-button template, and runs its own remote Netlify MCP server for coding agents. | 1 supported MCP | price not read | 90 (A) scanned 2026-11-04 | 67 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Vercel | host or runtime also SDK or framework, gateway or proxy | Vercel hosts MCP servers built with mcp-handler as Vercel Functions, runs its own remote Vercel MCP server, and ships an MCP client in the AI SDK alongside the AI Gateway for model traffic. | 1 supported MCP | per plan plus usage as of 2026-11-05 | 91 (A) scanned 2026-11-05 | 60 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | ## Registries and directories | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Anthropic | registry or directory also SDK or framework | Anthropic runs the Claude Connectors Directory of reviewed remote MCP servers and an MCP connector in the Claude Messages API that calls remote MCP tools without the developer writing an MCP client. | 1 supported, 1 partial MCP | price not read | 62 (C) scanned 2026-10-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | GitHub | registry or directory also host or runtime | GitHub runs a curated MCP Registry for partner and community servers, hosts its own remote GitHub MCP server, and lets Copilot surfaces use MCP servers under an organisation policy that is off by default. | none recorded | price not read | 65 (C) scanned 2026-11-01 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Glama | registry or directory also host or runtime, gateway or proxy | Glama runs a public MCP server directory that counted 116,152 servers on 5 Nov 2026, and also hosts MCP servers on dedicated machines behind its own MCP gateway, with per-tool access control and full call logs. | 1 supported MCP | no published price | 80 (B) scanned 2026-10-19 | 47 L2 Bot-Aware, 2026-11-05 | 2026-11-05 | | MCP Market | registry or directory | MCP Market is a public directory of MCP servers, agent skills and MCP clients, sorted by category, with a section for official servers and a marketplace for selling skills. | 1 supported Agent Skills | price not read | 60 (C) scanned 2026-10-19 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Official MCP Registry | registry or directory | The official MCP Registry is the protocol project's central metadata store for public MCP servers, meant to be read by downstream marketplaces and private registries rather than directly by host applications. | 1 supported MCP | free as of 2026-11-05 | no cached score | 0 L0 Not Ready, 2026-11-05 | 2026-11-05 | | OpenAI | registry or directory also SDK or framework | OpenAI's developer docs, formerly the Apps SDK, cover plugins that bundle MCP servers, skills and optional UI for ChatGPT and Codex, and a public directory that reviews remote MCP servers before listing. | 3 supported MCP, Agent Skills | price not read | 58 (C) scanned 2026-11-05 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Ora | registry or directory | Ora scores domains, MCP server URLs and MCP Apps for agent readiness, lists scored products in a searchable directory, and exposes the same scan through a public MCP server and the ax CLI. | 8 supported, 1 partial MCP, WebMCP, CLIs, A2A, NLWeb, Agent Skills, OpenAPI | free, rate-limited by IP as of 2026-11-05 | 95 (A+) scanned 2026-11-05 | 75 L5 Agent-Native, 2026-11-05T14:39:47Z | 2026-11-05 | | PulseMCP | registry or directory | PulseMCP is an independent MCP directory of servers, clients and MCP Apps with The Agentic Loop newsletter, and offers partners an enriched registry API built on the official MCP Registry. | 1 supported MCP | price not read | 11 (F) scanned 2026-05-27 | 27 L2 Bot-Aware, 2026-11-05 | 2026-11-05 | ## Gateways and proxies | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Agent Router | gateway or proxy | Agent Router, the renamed Envoy AI Gateway, is an open-source Envoy-based router that gives agents one OpenAI-compatible API for models and an MCPRoute gateway that aggregates and filters MCP servers. | 1 supported, 1 partial MCP | open source, Apache-2.0 as of 2026-11-05 | no cached score | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | agentgateway | gateway or proxy | agentgateway is an open-source Rust proxy, hosted as a Linux Foundation project, that routes and secures MCP, A2A, LLM and ordinary HTTP or gRPC traffic in one data plane. | 2 supported MCP, A2A | open source, Apache-2.0 as of 2026-11-05 | 50 (C) scanned 2026-11-01 | 13 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Docker | gateway or proxy also registry or directory, host or runtime | Docker packages MCP servers as container images in its MCP Catalog and runs them through the open-source MCP Gateway, which starts each server in an isolated container and injects credentials per call. | none recorded | open source, MIT as of 2026-11-05 | 69 (C) scanned 2026-10-11 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | IBM ContextForge | gateway or proxy also registry or directory | ContextForge is IBM's open-source registry and proxy that federates MCP servers, A2A agents and REST or gRPC APIs behind one MCP endpoint with guardrails, plugins and observability. | 2 supported MCP, A2A | open source, Apache-2.0 as of 2026-11-05 | no product domain | no scan | 2026-11-05 | | Kong | gateway or proxy also registry or directory | Kong turns APIs behind Kong Gateway or published in its Dev Portal into MCP servers, proxies MCP traffic with the AI MCP Proxy plugin, and lists an AI Registry product, on-premises or in Konnect. | 1 supported OpenAPI | AI Gateway Enterprise as of 2026-11-05 | 71 (B) scanned 2026-11-01 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | LiteLLM | gateway or proxy | LiteLLM is an open-source, self-hosted AI gateway whose proxy includes an MCP Gateway: one fixed endpoint for MCP tools, access controlled by API key and team, usable with any model LiteLLM routes. | 1 supported, 1 partial MCP | price not read | 73 (B) scanned 2026-11-01 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Microsoft Azure | gateway or proxy also host or runtime | Microsoft Azure exposes REST APIs as remote MCP servers through API Management's AI gateway, hosts MCP tool functions with the Azure Functions MCP extension, and publishes an open-source MCP Gateway for Kubernetes. | 1 partial MCP | open source, MIT as of 2026-11-05 | 24 (F) scanned 2026-10-15 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Mintive | gateway or proxy also host or runtime | Mintive, formerly MintMCP, sells a managed MCP gateway that hosts approved MCP servers, groups them into role-based bundles, gives agents their own credentials and logs every call. | none recorded | no published price | no cached score | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Obot | gateway or proxy also host or runtime, registry or directory | Obot is an open-source platform that hosts MCP servers, exposes them through a governed MCP gateway as virtual MCP servers, and keeps MCP and Agent Skills catalogs behind the MCP Registry API. | 2 supported MCP, Agent Skills | no published price | 67 (C) scanned 2026-10-09 | 33 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Pomerium | gateway or proxy also auth provider | Pomerium is an identity-aware proxy that puts internal or third-party MCP servers behind one gateway, runs downstream OAuth 2.1 and upstream OAuth for them, and limits tool calls by policy. | 2 supported MCP | per user per month as of 2026-11-05 | 59 (C) scanned 2026-08-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Portkey | gateway or proxy | Portkey, now presented as Palo Alto Networks Prisma AIRS AI Gateway, runs an MCP Gateway with a central registry of servers and tools, identity-provider sign-in and per-user tool policy, self-hosted or managed. | 1 supported MCP | open source, MIT as of 2026-11-05 | 69 (C) scanned 2026-10-20 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Speakeasy | gateway or proxy also registry or directory | Speakeasy now sells an AI control plane centred on an MCP gateway that discovers the MCP servers employees use, promotes approved ones into an internal registry and provisions them by IdP role. | 1 supported MCP | usage, no platform fee as of 2026-11-05 | 92 (A) scanned 2026-10-30 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Teleport | gateway or proxy | Teleport enrolls MCP servers as resources in a Teleport cluster, so engineers and AI clients reach them through Teleport with role-based permissions, audit and short-lived identity. | 1 supported MCP | price not read | 59 (C) scanned 2026-08-25 | 27 L2 Bot-Aware, 2026-11-05 | 2026-11-05 | ## Auth providers | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Auth0 | auth provider | Auth0's Auth for MCP acts as the OAuth 2.1 authorization server for remote MCP servers, with CIMD and DCR client registration, on-behalf-of token exchange and Token Vault for third-party APIs. | 3 supported, 1 partial MCP | per monthly active user, AI Agents add-on as of 2026-11-05 | 74 (B) scanned 2026-11-05 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Better Auth | auth provider | Better Auth is an open-source TypeScript authentication framework whose MCP plugin turns the app into an OAuth authorization server and protected resource for MCP clients, including the 2026-07-28 profile with CIMD. | 3 supported MCP | open source as of 2026-11-05 | 66 (C) scanned 2026-09-16 | 7 L0 Not Ready, 2026-11-05 | 2026-11-05 | | Clerk | auth provider | Clerk runs an OAuth server inside the customer's app that MCP servers built on Next.js or Express can use, with CIMD, DCR fallback and consent screens, and ships its own MCP server, CLI and agent skills. | 4 supported MCP, Agent Skills, CLIs | per retained user as of 2026-11-05 | 90 (A) scanned 2026-11-05 | 87 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Descope | auth provider | Descope acts as the authorization server for MCP servers: it publishes discovery metadata, registers clients by CIMD or DCR, runs login and consent, issues tokens and stores downstream credentials in a Connections vault. | 3 supported MCP | monthly base plus usage as of 2026-11-05 | 74 (B) scanned 2026-10-20 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Keycard | auth provider also gateway or proxy | Keycard gives each agent its own identity and issues scoped, just-in-time credentials at runtime, and puts MCP servers behind a unified access gateway with per-tool policy and an audit log. | 2 supported MCP, A2A | per transaction as of 2026-11-05 | 65 (C) scanned 2026-08-23 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Logto | auth provider | Logto is an open-source identity platform whose MCP guide makes Logto the authorization server for an MCP server through the mcp-auth library and MCP SDK v2, with the server registered as an API resource. | 1 supported MCP | monthly plus token usage as of 2026-11-05 | no cached score | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Scalekit | auth provider also gateway or proxy, connector platform | Scalekit is an OAuth 2.1 authorization server for MCP servers with DCR and CIMD, and also sells AgentKit, an MCP gateway with 600+ connectors and virtual MCP servers scoped by agent role. | 3 supported MCP | per tool call as of 2026-11-05 | 74 (B) scanned 2026-10-10 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Stytch | auth provider | Stytch Connected Apps turns an app into the OAuth authorization server for its remote MCP server, treating each MCP client as a Connected App that asks for consent through the authorization code grant. | 2 supported MCP | free tier then usage as of 2026-11-05 | 63 (C) scanned 2026-08-31 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | WorkOS | auth provider | WorkOS AuthKit is a spec-compatible OAuth authorization server for MCP servers, built on WorkOS Connect, with CIMD and optional DCR client registration and resource indicators. | 4 supported MCP | per MAU above 1 million, per connection as of 2026-11-05 | 86 (A) scanned 2026-11-04 | 40 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | ## Security scanners | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Akto | security scanner also gateway or proxy | Akto's MCP Security module finds MCP servers in a company's networks, probes them for prompt injection, tool poisoning and excessive permissions, and can route MCP tool calls through an inspecting agent-proxy. | none recorded | no published price | 62 (C) scanned 2026-09-05 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Cisco MCP Scanner | security scanner | Cisco's open-source MCP Scanner checks MCP servers, tools, prompts and resources for malicious content by combining YARA rules, an LLM judge and the Cisco AI Defense inspect API. | none recorded | open source, Apache-2.0 as of 2026-11-05 | 33 (D) scanned 2026-10-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Enkrypt AI | security scanner also gateway or proxy | Enkrypt AI sells an MCP Scanner that inventories MCP servers and tools and flags injection and over-privilege risks, and publishes an open-source inline MCP Gateway that approves, modifies or blocks tool calls. | none recorded | no published price | no cached score | 13 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Lasso Security | security scanner also gateway or proxy | Lasso Security publishes an open-source, plugin-based MCP gateway that masks secrets and personal data in traffic and scans MCP servers by reputation and tool descriptions before loading them. | none recorded | open source, MIT; no published price for its other products as of 2026-11-05 | 51 (C) scanned 2026-08-31 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Snyk Agent Scan | security scanner | Snyk Agent Scan, the former Invariant Labs mcp-scan, discovers agent configurations on a machine and scans their MCP servers, tools, prompts, resources and skills for prompt injection and other risks. | 1 supported Agent Skills | price not read | 79 (B) scanned 2026-11-05 | 40 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Trail of Bits mcp-context-protector | security scanner | mcp-context-protector from Trail of Bits wraps MCP servers to pin their configuration on first use, quarantine tool responses flagged by guardrails and strip ANSI control characters. | none recorded | open source, Apache-2.0 as of 2026-11-05 | 47 (D) scanned 2026-08-25 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | ## SDKs and frameworks | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | FastMCP and FastMCP Gateway | SDK or framework also host or runtime, gateway or proxy | FastMCP is Prefect's open-source Python framework for MCP servers, clients and apps, and FastMCP Gateway is Prefect's commercial service that hosts and governs FastMCP servers from a git push. | 1 supported MCP | open source, Apache-2.0; free start, paid plans as of 2026-11-05 | 63 (C) scanned 2026-09-07 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | LangChain | SDK or framework | LangChain connects its agents to MCP servers through MCPAdapter, built on FastMCP, which discovers a server's tools and adapts them into LangChain tools; the older langchain-mcp-adapters package remains on GitHub. | none recorded | open source as of 2026-11-05 | 74 (B) scanned 2026-10-17 | 7 L0 Not Ready, 2026-11-05 | 2026-11-05 | | Mastra | SDK or framework | Mastra is an open-source TypeScript agent framework whose @mastra/mcp package provides an MCP client for agents and an MCPServer that exposes Mastra tools and agents to external MCP clients. | none recorded | open source; monthly plus usage as of 2026-11-05 | 78 (B) scanned 2026-11-01 | 33 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | MCP official SDKs | SDK or framework | The Model Context Protocol project publishes ten official SDKs, ranked in three tiers by feature completeness, protocol support and maintenance commitment, for building MCP servers and clients. | 1 supported MCP | open source as of 2026-11-05 | 69 (C) scanned 2026-10-16 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Pydantic AI | SDK or framework | Pydantic AI is a Python agent framework that connects agents to MCP servers through an MCP capability, runs servers locally by default with an opt-in for model providers' native MCP, and can serve agents as MCP servers. | none recorded | open source as of 2026-11-05 | 90 (A) scanned 2026-11-04 | 60 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Spring AI | SDK or framework | Spring AI builds on the MCP Java SDK with Spring Boot starters for MCP clients and servers, annotation-based tool handling, and the Spring WebFlux and WebMVC transports. | 1 supported MCP | open source as of 2026-11-05 | 58 (C) scanned 2026-04-24 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Stainless | SDK or framework | Stainless generates an MCP server from an OpenAPI spec as a subpackage of a generated TypeScript SDK, exposing a code execution tool and a docs search tool instead of one tool per endpoint. | 1 supported OpenAPI | per generator as of 2026-11-05 | 58 (C) scanned 2026-09-10 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | xmcp | SDK or framework | xmcp is a TypeScript framework from basement.studio that registers MCP tools, prompts and resources from project files and ships adapters for Next.js and Express plus auth and payment integrations. | none recorded | open source as of 2026-11-05 | 57 (C) scanned 2026-09-16 | 47 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | ## Connector platforms | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Activepieces | connector platform | Activepieces exposes its automation platform as one MCP server per project, so Claude, Cursor or another client can use 770+ connected apps as tools and build flows, free on every plan, cloud or self-hosted. | none recorded | included in every plan as of 2026-11-05 | 74 (B) scanned 2026-10-26 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Arcade | connector platform also auth provider, registry or directory | Arcade is an actions runtime that handles OAuth and user tokens and enforces policy on every agent tool call across 7,500+ tools; it acquired Smithery, the public MCP registry and hosting service, in August 2026. | none recorded | platform fee plus per tool call; no published price for its other products as of 2026-11-05 | 89 (A) scanned 2026-11-01 | 67 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Composio | connector platform | Composio gives agents per-user, authenticated access to 1000+ apps through a shared MCP server with seven meta-tools, per-session MCP endpoints, single-toolkit servers and agent plugins. | 1 supported CLIs | price not read | 83 (B) scanned 2026-10-26 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Make | connector platform | Make runs a hosted, stateless Streamable HTTP MCP server that lets Claude, ChatGPT and other clients run Make scenarios and manage scenarios, connections, webhooks and teams, scoped at connect time. | 2 supported MCP, Agent Skills | price not read | 78 (B) scanned 2026-11-02 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Merge | connector platform | Merge Agent Handler gives AI agents per-end-user access to 190+ MCP-ready third-party connectors through Tool Packs, with a Security Gateway that scans every tool call against data-loss rules. | none recorded | no published price | 65 (C) scanned 2026-10-26 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | n8n | connector platform | n8n includes a built-in MCP server per instance that lets MCP clients search workflows, run the ones marked available to MCP, and create or edit workflows and data tables, on n8n Cloud or self-hosted. | none recorded | price not read | 71 (B) scanned 2026-10-09 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Nango | connector platform also auth provider | Nango is an integration layer whose MCP Auth lets an app authorise each end user against external MCP servers such as Notion, Linear or HubSpot, store the tokens and call those servers through Nango's proxy. | 2 supported MCP | free tier, then credits as of 2026-11-05 | 65 (C) scanned 2026-10-26 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Pipedream | connector platform | Pipedream Connect runs a remote MCP server that gives agents per-user access to 3,000+ apps and 10,000+ prebuilt tools, with Pipedream managing OAuth and storing each user's credentials. | none recorded | free to build, paid in production as of 2026-11-05 | no cached score | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | StackOne | connector platform also gateway or proxy | StackOne runs a hosted MCP server and an enterprise Tool Gateway MCP that give agents 43,000+ actions across 630+ connectors, with per-account tool catalogs and StackOne handling provider authentication. | 1 supported A2A | no published price | 87 (A) scanned 2026-10-15 | 73 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Zapier | connector platform | Zapier MCP lets MCP clients run actions across Zapier's app catalogue, with each programmatic call drawn from the same monthly task allowance that powers Zap workflows. | none recorded | tasks from the plan allowance as of 2026-11-05 | 84 (B) scanned 2026-11-04 | 73 L5 Agent-Native, 2026-11-05 | 2026-11-05 | ## Vendors that cover a second layer | Layer | Typed elsewhere, also covering it | | --- | --- | | Hosts and runtimes | Docker, FastMCP and FastMCP Gateway, GitHub, Glama, Microsoft Azure, Mintive, Obot | | Registries and directories | Arcade, Docker, IBM ContextForge, Kong, Obot, Speakeasy | | Gateways and proxies | Akto, AWS, Cloudflare, Enkrypt AI, FastMCP and FastMCP Gateway, Glama, Keycard, Lasso Security, Scalekit, StackOne, Vercel | | Auth providers | Arcade, AWS, Cloudflare, Nango, Pomerium | | Security scanners | none | | SDKs and frameworks | Alpic, Anthropic, Manufact, OpenAI, Vercel | | Connector platforms | Apify, Scalekit | ## How the two checks were taken Each vendor's own domain carries two agent-readiness checks, both read on 5 November 2026. The Ora score is Ora's cached result for the domain, fetched with one GET and no scan triggered, so its scan date can be months old: 57 of the 63 domains had a cached score and the rest returned 404. The Cloudflare scan was run through the public scanner on its default All Checks profile, one request every three seconds, on 63 domains; the score is checks passed over checks counted, and the band is the scanner's own level. For hyperscalers the domain is the host of the page that documents the MCP product. IBM ContextForge has no product domain of its own, so it carries no check. The two numbers come from different scanners, are not combined and are not used to order any table. ## What is left out These names were read or considered in this pass and are not profiled: - Smithery as its own row: smithery.ai disallowed the crawl user agent in robots.txt on 5 November 2026, so no new facts could be read there. The Arcade row carries what Arcade's own announcement says about it, and the hosts page keeps the profile read on 4 November. - Aembit: The pages read were marketing copy without product specifics, and the pricing page showed no prices, so fewer than six specific claims were available. - Golf and Operant AI: Home and product pages carried general claims, and no documentation was found in this pass. - TrueFoundry MCP Gateway: The page read listed claims such as role-based access and air-gapped deployment, with no specifics or prices. - Traefik Hub MCP Gateway: The page text came back as navigation only in a plain fetch. - Bifrost: The page read was a latency comparison against LiteLLM, so it is left for a read of its documentation. - Klavis AI: Its home page now describes reinforcement-learning environments and evaluation, and its documentation site disallowed the crawl user agent in robots.txt. - Paragon ActionKit: Only one specific claim was read. - Workato Enterprise MCP: A plain fetch returned navigation only. - mcp.so: The listing page showed featured servers and stated no counts, sources or method. - Postman MCP: The documentation URL tried returned 404 and no other page was found in this pass. - Blaxel: The page was fetched but no profile was written in this pass. - Zenity, Noma, Pillar and Prompt Security: Not read in this pass. Companies that run their own MCP server, such as payment, commerce and database vendors, belong to [the directory](https://agentmcpdirectory.com/directory/), not to this list. ## Downloads and citation - [vendors.csv](https://agentmcpdirectory.com/vendors/vendors.csv) one row per vendor, with prices, standards counts and both checks - [vendors.json](https://agentmcpdirectory.com/vendors/vendors.json) every vendor with its facts, products, standards, checks and sources Agent MCP Directory, "MCP infrastructure vendors", 5 November 2026 edition, https://agentmcpdirectory.com/vendors Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/index.md) ## Sources - [MCP SDKs, the project's own page](https://modelcontextprotocol.io/docs/sdk), read 5 November 2026 - [The MCP Registry, the project's own page](https://modelcontextprotocol.io/registry/about), read 5 November 2026 - [Auth0 home](https://auth0.com/ai/docs/mcp/overview), read 5 November 2026 - [MCP plugin - Better Auth docs](https://www.better-auth.com/docs/plugins/mcp), read 5 November 2026 - [Clerk home](https://clerk.com/), read 5 November 2026 - [MCP Authorization - Descope Documentation](https://docs.descope.com/mcp), read 5 November 2026 - [Keycard home](https://www.keycard.ai/), read 5 November 2026 - [Logto home](https://logto.io/), read 5 November 2026 - [Auth for MCP Servers: Drop-in OAuth 2.1 | Scalekit](https://www.scalekit.com/mcp-auth), read 5 November 2026 - [Stytch - A better way to build auth](https://stytch.com/), read 5 November 2026 - [Secure auth for MCP servers - WorkOS](https://workos.com/mcp), read 5 November 2026 - [MCP servers - 770+ apps for your AI | Activepieces](https://www.activepieces.com/mcp), read 5 November 2026 - [Arcade: The Actions Runtime for Enterprise AI Agents](https://www.arcade.dev/), read 5 November 2026 - [Composio home](https://composio.dev/), read 5 November 2026 - [Make MCP Server - Make Developer Hub](https://developers.make.com/mcp-server), read 5 November 2026 - [Merge home](https://www.merge.dev/agent-handler), read 5 November 2026 - [Connect to n8n MCP server - n8n Docs](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/), read 5 November 2026 - [Nango home](https://www.nango.dev/), read 5 November 2026 - [MCP Servers - Pipedream](https://pipedream.com/docs/connect/mcp), read 5 November 2026 - [AI Agent Integration Infrastructure | StackOne](https://www.stackone.com/), read 5 November 2026 - [Zapier home](https://zapier.com/mcp), read 5 November 2026 - [Agent Router](https://aigateway.envoyproxy.io/), read 5 November 2026 - [agentgateway | Agent Connectivity Solved](https://agentgateway.dev/), read 5 November 2026 - [Docker MCP Catalog and Toolkit - Docker docs](https://docs.docker.com/ai/mcp-catalog-and-toolkit/), read 5 November 2026 - [GitHub - IBM/mcp-context-forge (ContextForge)](https://github.com/IBM/mcp-context-forge), read 5 November 2026 - [developer.konghq.com/mcp/](https://developer.konghq.com/mcp/), read 5 November 2026 - [LiteLLM - Open-Source AI Gateway & LLM Proxy](https://www.litellm.ai/), read 5 November 2026 - [Expose REST API as MCP server - Azure API Management | Microsoft Learn](https://learn.microsoft.com/en-us/azure/api-management/export-rest-mcp-server), read 5 November 2026 - [Mintive home](https://www.mintive.com/), read 5 November 2026 - [Obot home](https://obot.ai/), read 5 November 2026 - [Model Context Protocol (MCP) Support | Pomerium](https://www.pomerium.com/docs/capabilities/mcp), read 5 November 2026 - [Portkey home](https://portkey.ai/), read 5 November 2026 - [Speakeasy home](https://www.speakeasy.com/product/mcp-gateway), read 5 November 2026 - [goteleport.com/docs/enroll-resources/mcp-access/](https://goteleport.com/docs/enroll-resources/mcp-access/), read 5 November 2026 - [Alpic: build, deploy, monitor and distribute your ChatGPT Apps and MCP servers](https://alpic.ai/), read 5 November 2026 - [Apify MCP server - Apify docs](https://docs.apify.com/platform/integrations/mcp), read 5 November 2026 - [AWS home](https://aws.amazon.com/bedrock/agentcore/), read 5 November 2026 - [Browserbase MCP server - Browserbase Documentation](https://docs.browserbase.com/integrations/mcp/introduction), read 5 November 2026 - [Model Context Protocol (MCP) · Cloudflare Agents docs](https://developers.cloudflare.com/agents/model-context-protocol/), read 5 November 2026 - [Host MCP servers on Cloud Run  |  Google Cloud Documentation](https://cloud.google.com/run/docs/host-mcp-servers), read 5 November 2026 - [manufact.com/](https://manufact.com/), read 5 November 2026 - [Mintlify home](https://www.mintlify.com/docs/ai/model-context-protocol), read 5 November 2026 - [Building MCPs with Netlify - Netlify Developers](https://developers.netlify.com/guides/write-mcps-on-netlify/), read 5 November 2026 - [Model Context Protocol](https://vercel.com/docs/mcp), read 5 November 2026 - [Anthropic home](https://claude.com/connectors), read 5 November 2026 - [GitHub home](https://github.com/mcp), read 5 November 2026 - [Glama MCP servers directory](https://glama.ai/mcp/servers), read 5 November 2026 - [MCP Market | Discover Top MCP Servers & Agent Skills](https://mcpmarket.com/), read 5 November 2026 - [Official MCP Registry home](https://registry.modelcontextprotocol.io/), read 5 November 2026 - [developers.openai.com/apps-sdk](https://developers.openai.com/apps-sdk), read 5 November 2026 - [Ora | Make your site work for agents](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 5 November 2026 - [PulseMCP | Keep up-to-date with MCP](https://www.pulsemcp.com/), read 5 November 2026 - [FastMCP: The Framework for MCP - FastMCP](https://gofastmcp.com/), read 5 November 2026 - [Model Context Protocol (MCP) - Docs by LangChain](https://docs.langchain.com/oss/python/langchain/mcp), read 5 November 2026 - [Mastra home](https://mastra.ai/), read 5 November 2026 - [Model Context Protocol (MCP) | Pydantic Docs](https://ai.pydantic.dev/mcp/), read 5 November 2026 - [Model Context Protocol (MCP) :: Spring AI Reference](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html), read 5 November 2026 - [Stainless - MCP Portal](https://www.stainless.com/mcp), read 5 November 2026 - [xmcp.dev/](https://xmcp.dev/), read 5 November 2026 - [Akto MCP Security Solution | MCP Vendor Security](https://www.akto.io/mcp-security), read 5 November 2026 - [GitHub - cisco-ai-defense/mcp-scanner](https://github.com/cisco-ai-defense/mcp-scanner), read 5 November 2026 - [Enkrypt AI MCP Scanner: Advanced AI Threat Detection & Security](https://www.enkryptai.com/product/mcp-scanner), read 5 November 2026 - [Secure AI Adoption at Enterprise Scale | Lasso](https://www.lasso.security/), read 5 November 2026 - [GitHub - snyk/agent-scan (formerly invariantlabs-ai/mcp-scan)](https://github.com/snyk/agent-scan), read 5 November 2026 - [GitHub - trailofbits/mcp-context-protector](https://github.com/trailofbits/mcp-context-protector), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Activepieces: MCP vendor profile | Agent MCP Directory" description: "Activepieces: connector platform. Products: Activepieces MCP server. 5 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/activepieces site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Activepieces: MCP vendor profile | Agent MCP Directory > Activepieces: connector platform. Products: Activepieces MCP server. 5 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/activepieces Site: Agent MCP Directory Last reviewed: 2026-11-05 # Activepieces: MCP vendor profile Activepieces exposes its automation platform as one MCP server per project, so Claude, Cursor or another client can use 770+ connected apps as tools and build flows, free on every plan, cloud or self-hosted, as documented by the vendor and not verified by connecting. ## At a glance | Type | Connector platforms | | --- | --- | | Home | www.activepieces.com | | Price | included in every plan | | Read | 5 November 2026 | ## What it does for this layer The Activepieces MCP page listed 775 apps on 5 Nov 2026, with Artificial Intelligence (126), Productivity (110) and Marketing (105) as the largest categories ([www.activepieces.com](https://www.activepieces.com/mcp), observed 5 November 2026). The Activepieces page offers one-click installs for Claude and Cursor and setup for Claude Code, VS Code with Copilot, ChatGPT, Codex CLI, Cline and OpenCode ([www.activepieces.com](https://www.activepieces.com/mcp)). Activepieces offers "One MCP server for all of Activepieces" that a client such as Claude, Cursor or Codex uses to drive the platform ([www.activepieces.com](https://www.activepieces.com/mcp)). Activepieces gives each project one server URL, and every connected app shows up in the client as a tool ([www.activepieces.com](https://www.activepieces.com/mcp)). Through the MCP server, a client can also build Activepieces flows, not only call app actions ([www.activepieces.com](https://www.activepieces.com/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Activepieces MCP server | Per-project MCP server exposing connected apps and flow building. | included in every plan; from 0 USD (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | activepieces.com | 74 of 100, grade B | 26 October 2026 | how it was taken | | Cloudflare agent-readiness scan | activepieces.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Activepieces does not host arbitrary MCP server code; its server exposes Activepieces pieces. ## Related on this site Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/activepieces/index.md) ## Sources - [MCP servers - 770+ apps for your AI | Activepieces](https://www.activepieces.com/mcp), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Agent Router: MCP vendor profile | Agent MCP Directory" description: "Agent Router: gateway or proxy. Products: Agent Router. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/agent-router site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Agent Router: MCP vendor profile | Agent MCP Directory > Agent Router: gateway or proxy. Products: Agent Router. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/agent-router Site: Agent MCP Directory Last reviewed: 2026-11-05 # Agent Router: MCP vendor profile Agent Router, the renamed Envoy AI Gateway, is an open-source Envoy-based router that gives agents one OpenAI-compatible API for models and an MCPRoute gateway that aggregates and filters MCP servers, as documented by the vendor. The Agent Router repository says nothing deployed is renamed by the move to the Agentic AI Foundation, with the same release cadence (github.com). ## At a glance | Listed as | Agent Router (formerly Envoy AI Gateway) | | --- | --- | | Type | Gateways and proxies | | Operator | Agentic AI Foundation project | | Home | aigateway.envoyproxy.io | | Price | open source, Apache-2.0 | | Read | 5 November 2026 | ## What it does for this layer The github.com/envoyproxy/ai-gateway URL redirected to github.com/theagentrouter/agent-router on 5 Nov 2026; the repository keeps the Apache 2.0 license and had about 2.4k stars ([github.com](https://github.com/envoyproxy/ai-gateway), observed 5 November 2026). Agent Router configures MCP routing through an MCPRoute resource (apiVersion aigateway.envoyproxy.io/v1beta1), with a worked example that proxies the GitHub MCP server ([aigateway.envoyproxy.io](https://aigateway.envoyproxy.io/docs/capabilities/mcp/)). Agent Router states "Complete June 2025 MCP spec compliance", including tool calls, notifications, prompts, resources and server-to-client requests ([aigateway.envoyproxy.io](https://aigateway.envoyproxy.io/docs/capabilities/mcp/)). Agent Router supports Streamable HTTP for MCP and enforces OAuth authentication flows natively, per its MCP capability page ([aigateway.envoyproxy.io](https://aigateway.envoyproxy.io/docs/capabilities/mcp/)). The Agent Router docs were at version 1.2 on 5 Nov 2026, with an Agent Router CLI listed in the docs ([aigateway.envoyproxy.io](https://aigateway.envoyproxy.io/docs/capabilities/mcp/)). The Agent Router site says it was "Formerly Envoy AI Gateway" and is "now an Agentic AI Foundation project", with the same code and maintainers ([aigateway.envoyproxy.io](https://aigateway.envoyproxy.io/)). The Agent Router MCP gateway aggregates several MCP servers into one endpoint, filters which tools clients see, and injects upstream API keys ([aigateway.envoyproxy.io](https://aigateway.envoyproxy.io/docs/capabilities/mcp/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Agent Router | Envoy-based open-source gateway for LLM and MCP traffic on Kubernetes. | open source, Apache-2.0; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | spec revision | Partial | States compliance with the June 2025 MCP spec; no statement on 2025-11-25 or 2026-07-28. | aigateway.envoyproxy.io | | MCP | streamable HTTP | Supports | Full support for Streamable HTTP transport. | aigateway.envoyproxy.io | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | aigateway.envoyproxy.io | no cached score GET /api/score returned HTTP 404 (no cached score) | not scanned | how it was taken | | Cloudflare agent-readiness scan | aigateway.envoyproxy.io | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Agent Router does not host MCP server code; it routes to backends that run elsewhere. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/agent-router/index.md) ## Sources - [Agent Router](https://aigateway.envoyproxy.io/), read 5 November 2026 - [GitHub - envoyproxy/ai-gateway (redirects to theagentrouter/agent-router)](https://github.com/envoyproxy/ai-gateway), read 5 November 2026 - [Model Context Protocol (MCP) Gateway | Agent Router](https://aigateway.envoyproxy.io/docs/capabilities/mcp/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "agentgateway: MCP vendor profile | Agent MCP Directory" description: "agentgateway: gateway or proxy. Products: agentgateway. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/agentgateway site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # agentgateway: MCP vendor profile | Agent MCP Directory > agentgateway: gateway or proxy. Products: agentgateway. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/agentgateway Site: Agent MCP Directory Last reviewed: 2026-11-05 # agentgateway: MCP vendor profile agentgateway is an open-source Rust proxy, hosted as a Linux Foundation project, that routes and secures MCP, A2A, LLM and ordinary HTTP or gRPC traffic in one data plane, as documented by the vendor. The agentgateway MCP Gateway is described as treating MCP servers like microservices: discover them, sign and scope every tool call, and keep an audit trail (agentgateway.dev). ## At a glance | Type | Gateways and proxies | | --- | --- | | Operator | Linux Foundation project | | Home | agentgateway.dev | | Price | open source, Apache-2.0 | | Read | 5 November 2026 | ## What it does for this layer GitHub showed about 6.0k stars for agentgateway on 5 Nov 2026, under the Apache-2.0 license ([github.com](https://github.com/agentgateway/agentgateway), observed 5 November 2026). agentgateway's MCP Auth authenticates callers into MCP servers and scopes which tools each identity may invoke ([agentgateway.dev](https://agentgateway.dev/)). agentgateway deploys as a standalone binary or Docker container, or on Kubernetes with a built-in control plane and the Gateway API ([agentgateway.dev](https://agentgateway.dev/docs/)). The agentgateway home page lists AAIF, Solo.io, Microsoft, Alibaba, Adobe, AWS, Cisco, Salesforce, Huawei, Amdocs and iFlytek as contributing companies ([agentgateway.dev](https://agentgateway.dev/)). agentgateway docs offer markdown versions of every page by appending .md to the URL, and an llms.txt index ([agentgateway.dev](https://agentgateway.dev/docs/)). The agentgateway repository states "Agentgateway is a Linux Foundation project." ([github.com](https://github.com/agentgateway/agentgateway)). The agentgateway repository describes it as "an open source proxy built on AI-native protocols (MCP & A2A)" for agent-to-LLM, agent-to-tool and agent-to-agent traffic ([github.com](https://github.com/agentgateway/agentgateway)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | agentgateway | Open-source proxy for MCP, A2A, LLM and service traffic, standalone or on Kubernetes. | open source, Apache-2.0; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | MCP gateway and auth | Supports | MCP Gateway and MCP Auth features on the home page. | agentgateway.dev | | A2A | A2A gateway | Supports | A2A Gateway listed with RBAC and CEL network authz. | agentgateway.dev | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | agentgateway.dev | 50 of 100, grade C | 1 November 2026 | how it was taken | | Cloudflare agent-readiness scan | agentgateway.dev | 13 of 100, L1 Basic Web Presence; 2 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - agentgateway does not host MCP server code; it proxies servers that run elsewhere. - agentgateway is not a registry of public MCP servers. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [A2A](https://agentmcpdirectory.com/standards/a2a/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/agentgateway/index.md) ## Sources - [agentgateway | Agent Connectivity Solved](https://agentgateway.dev/), read 5 November 2026 - [GitHub - agentgateway/agentgateway](https://github.com/agentgateway/agentgateway), read 5 November 2026 - [agentgateway.dev/docs/](https://agentgateway.dev/docs/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Akto: MCP vendor profile | Agent MCP Directory" description: "Akto: security scanner. Products: MCP Security module, Agent-proxy gateway. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/akto site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Akto: MCP vendor profile | Agent MCP Directory > Akto: security scanner. Products: MCP Security module, Agent-proxy gateway. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/akto Site: Agent MCP Directory Last reviewed: 2026-11-05 # Akto: MCP vendor profile Akto's MCP Security module finds MCP servers in a company's networks, probes them for prompt injection, tool poisoning and excessive permissions, and can route MCP tool calls through an inspecting agent-proxy, as documented by the vendor. Akto MCP Recon discovers MCP-compatible servers by scanning IP ranges given in CIDR or range form and registers what it finds in Akto (ai-security-docs.akto.io). ## At a glance | Listed as | Akto (MCP Security) | | --- | --- | | Type | Security scanners | | Also covers | gateway or proxy | | Home | www.akto.io | | Price | no published price | | Read | 5 November 2026 | ## What it does for this layer Akto says its MCP Security module "automatically identifies MCP servers, discovers associated Agentic components, runs targeted red teaming, and continuously monitors" for misconfigurations, threats and data leaks ([ai-security-docs.akto.io](https://ai-security-docs.akto.io/readme/mcp-security.md)). Akto's agent-proxy gateway URL is built by dropping https:// from the target MCP server URL and appending it to the agent-proxy base, so every tool call passes through Akto ([ai-security-docs.akto.io](https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/ai-agent-security/microsoft-copilot-studio/proxy-mcp-via-akto.md)). Akto's MCP discovery works across cloud, hybrid and on-premises environments, per its docs ([ai-security-docs.akto.io](https://ai-security-docs.akto.io/readme/mcp-security.md)). Akto's MCP security page says it keeps only sanctioned servers in place by discovering servers and the agents invoking them and enforcing guardrails ([www.akto.io](https://www.akto.io/mcp-security)). Akto's probe library for MCP covers prompt injection, tool poisoning, excessive permissions and unauthorized endpoint access ([ai-security-docs.akto.io](https://ai-security-docs.akto.io/readme/mcp-security.md)). Akto documents routing Microsoft Copilot Studio agents' MCP tool calls through its agent-proxy, which inspects requests and responses and applies policies while staying transparent to the server ([ai-security-docs.akto.io](https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/ai-agent-security/microsoft-copilot-studio/proxy-mcp-via-akto.md)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Security module | Discovery, red teaming and monitoring of MCP servers in Akto Argus. | no published price | | Agent-proxy gateway | Inline proxy that inspects MCP tool calls. | no published price | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | akto.io | 62 of 100, grade C | 5 September 2026 | how it was taken | | Cloudflare agent-readiness scan | akto.io | 27 of 100, L1 Basic Web Presence; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Akto does not publish prices on the MCP pages read. ## Related on this site Type - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/akto/index.md) ## Sources - [Akto MCP Security Solution | MCP Vendor Security](https://www.akto.io/mcp-security), read 5 November 2026 - [ai-security-docs.akto.io/readme/mcp-security.md](https://ai-security-docs.akto.io/readme/mcp-security.md), read 5 November 2026 - [ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/others/mcp-recon.md](https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/others/mcp-recon.md), read 5 November 2026 - [ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/ai-agent-security/microsoft-copilot-](https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/ai-agent-security/microsoft-copilot-studio/proxy-mcp-via-akto.md), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Alpic: MCP vendor profile | Agent MCP Directory" description: "Alpic: host or runtime. Products: Alpic Cloud, Skybridge. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/alpic site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Alpic: MCP vendor profile | Agent MCP Directory > Alpic: host or runtime. Products: Alpic Cloud, Skybridge. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/alpic Site: Agent MCP Directory Last reviewed: 2026-11-05 # Alpic: MCP vendor profile Alpic is a cloud platform that deploys MCP servers and ChatGPT or Claude apps with no configuration, adds AI-specific analytics and session replay, and maintains Skybridge, an open-source MCP Apps framework, as documented by the vendor. Alpic detects TypeScript and Python MCP SDKs, xmcp and FastMCP automatically when deploying (docs.alpic.ai). ## At a glance | Type | Hosts and runtimes | | --- | --- | | Also covers | SDK or framework | | Home | alpic.ai | | Price | per request | | Read | 5 November 2026 | ## What it does for this layer Alpic deploys from GitHub Actions, GitLab CI or any pipeline through the Alpic CLI ([docs.alpic.ai](https://docs.alpic.ai/)). Alpic can protect a deployed app with authentication, IP allowlisting and fixed outbound IPs ([docs.alpic.ai](https://docs.alpic.ai/)). Alpic's Free plan includes 10,000 requests a month; a 50 USD a month plan includes 200,000 requests, with additional requests at 150 USD per million ([alpic.ai](https://alpic.ai/pricing)). Alpic offers an Alpic MCP App and CLI so Claude Code, Codex or Cursor can deploy and manage an app ([docs.alpic.ai](https://docs.alpic.ai/)). Alpic calls itself "the cloud platform for MCP-based AI apps" ([alpic.ai](https://alpic.ai/)). Skybridge is Alpic's open-source, fullstack TypeScript framework for MCP Apps that render inside ChatGPT and Claude ([docs.alpic.ai](https://docs.alpic.ai/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Alpic Cloud | Hosting, analytics and session replay for MCP servers and ChatGPT apps. | per request; from 0 USD; Free 10,000 requests a month; 50 USD a month for 200,000 (source, as of 5 November 2026) | | Skybridge | Open-source TypeScript framework for MCP Apps. | price not read | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | alpic.ai | 86 of 100, grade A | 23 October 2026 | how it was taken | | Cloudflare agent-readiness scan | alpic.ai | 47 of 100, L1 Basic Web Presence; 7 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Alpic does not publish a public directory of MCP servers on the pages read. ## Related on this site Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/alpic/index.md) ## Sources - [Alpic: build, deploy, monitor and distribute your ChatGPT Apps and MCP servers](https://alpic.ai/), read 5 November 2026 - [Alpic Docs](https://docs.alpic.ai/), read 5 November 2026 - [Alpic MCP cloud platform pricing](https://alpic.ai/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Anthropic: MCP vendor profile | Agent MCP Directory" description: "Anthropic: registry or directory. 2 products, 6 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/anthropic site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Anthropic: MCP vendor profile | Agent MCP Directory > Anthropic: registry or directory. 2 products, 6 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/anthropic Site: Agent MCP Directory Last reviewed: 2026-11-05 # Anthropic: MCP vendor profile Anthropic runs the Claude Connectors Directory of reviewed remote MCP servers and an MCP connector in the Claude Messages API that calls remote MCP tools without the developer writing an MCP client, as documented by the vendor. The Claude API accepts mcp-client-2026-09-15 or mcp-client-2025-11-20 beta headers, while Claude Platform on AWS and Claude models on Google Cloud take mcp-client-2025-11-20 (platform.claude.com). ## At a glance | Listed as | Anthropic (Claude Connectors Directory, MCP connector) | | --- | --- | | Type | Registries and directories | | Also covers | SDK or framework | | Home | claude.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer MCP servers used through the Claude API connector must be publicly exposed over HTTP, Streamable HTTP or SSE; local stdio servers cannot be connected directly ([platform.claude.com](https://platform.claude.com/docs/en/agents-and-tools/mcp-connector)). The Claude API MCP connector supports OAuth Bearer tokens for authenticated servers, several servers in one request, and allowlists or denylists of tools ([platform.claude.com](https://platform.claude.com/docs/en/agents-and-tools/mcp-connector)). The mcp-client-2026-09-15 beta header records each server's tool list in an mcp\_tool\_listing block and lets the developer pin it so tools do not change mid-conversation ([platform.claude.com](https://platform.claude.com/docs/en/agents-and-tools/mcp-connector)). Anthropic's MCP connector lets developers connect to MCP servers from the Messages API "without implementing an MCP client" ([platform.claude.com](https://platform.claude.com/docs/en/agents-and-tools/mcp-connector)). The older mcp-client-2025-04-04 version of the connector is documented as deprecated ([platform.claude.com](https://platform.claude.com/docs/en/agents-and-tools/mcp-connector)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Claude Connectors Directory | Directory of reviewed remote MCP connectors and plugins for Claude. | price not read | | MCP connector (Messages API) | Server-side MCP client for remote tools in Claude API requests. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | streamable HTTP | Supports | Connector reaches servers over Streamable HTTP or SSE. | platform.claude.com | | MCP | tools only | Partial | Only tool calls from the MCP feature set are supported by the API connector. | platform.claude.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | claude.com | 62 of 100, grade C | 30 October 2026 | how it was taken | | Cloudflare agent-readiness scan | claude.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - The Claude API MCP connector does not use MCP resources or prompts directly; client-side helpers cover those ([platform.claude.com](https://platform.claude.com/docs/en/agents-and-tools/mcp-connector)). ## Related on this site Hosts page - [Claude Connectors Directory](https://agentmcpdirectory.com/hosts/claude-connectors-directory/) Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/anthropic/index.md) ## Sources - [Anthropic home](https://claude.com/connectors), read 5 November 2026 - [platform.claude.com/docs/en/agents-and-tools/mcp-connector](https://platform.claude.com/docs/en/agents-and-tools/mcp-connector), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Apify: MCP vendor profile | Agent MCP Directory" description: "Apify: host or runtime. Products: Apify MCP server. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/apify site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Apify: MCP vendor profile | Agent MCP Directory > Apify: host or runtime. Products: Apify MCP server. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/apify Site: Agent MCP Directory Last reviewed: 2026-11-05 # Apify: MCP vendor profile Apify runs a hosted MCP server that lets agents search, call and pay for Apify Actors, the scrapers and automations on its platform, with tool sets chosen through URL parameters, as documented by the vendor. Apify says its MCP telemetry does not collect conversations, tool arguments, API tokens or personal data (docs.apify.com). ## At a glance | Type | Hosts and runtimes | | --- | --- | | Also covers | connector platform | | Home | docs.apify.com | | Price | usage of Actors | | Read | 5 November 2026 | ## What it does for this layer By default the Apify MCP server loads the actors and docs tool categories, the apify/rag-web-browser and apify/web-fetch Actors, and report-problem ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp)). Telemetry is enabled by default for all Apify MCP tool calls; the local server opts out with --telemetry-enabled=false or TELEMETRY\_ENABLED=false ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp)). Apify's Free plan includes 5 USD a month to spend in Apify Store or on one's own Actors, at 0.2 USD per compute unit ([apify.com](https://apify.com/pricing)). Apify's Starter plan is 19 USD a month at 0.2 USD per compute unit, Scale is 199 USD a month at 0.16 USD, and Business is 999 USD a month at 0.13 USD ([apify.com](https://apify.com/pricing)). Apify selects tools through server URL parameters, for example https://mcp.apify.com?tools=actors,docs,apify/rag-web-browser ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp)). Apify says agents can pay for Actor runs without an Apify account through per-request payments ([docs.apify.com](https://docs.apify.com/platform/integrations/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Apify MCP server | Hosted and local MCP server for Apify Actors and docs. | usage of Actors; from 0 USD; Free plan 5 USD of usage a month (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | apify.com | 96 of 100, grade A+ | 4 November 2026 | how it was taken | | Cloudflare agent-readiness scan | apify.com | 73 of 100, L5 Agent-Native; 11 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Apify does not host arbitrary MCP servers; its server exposes Apify Actors. ## Related on this site Hosts page - [Apify MCP](https://agentmcpdirectory.com/hosts/apify-mcp/) Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/apify/index.md) ## Sources - [Apify MCP server - Apify docs](https://docs.apify.com/platform/integrations/mcp), read 5 November 2026 - [Apify pricing - flexible plan + pay as you go · Apify](https://apify.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Arcade: MCP vendor profile | Agent MCP Directory" description: "Arcade: connector platform. Products: Arcade runtime, Arcade MCP framework, Smithery. 9 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/arcade site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Arcade: MCP vendor profile | Agent MCP Directory > Arcade: connector platform. Products: Arcade runtime, Arcade MCP framework, Smithery. 9 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/arcade Site: Agent MCP Directory Last reviewed: 2026-11-05 # Arcade: MCP vendor profile Arcade is an actions runtime that handles OAuth and user tokens and enforces policy on every agent tool call across 7,500+ tools; it acquired Smithery, the public MCP registry and hosting service, in August 2026, as documented by the vendor. ## At a glance | Listed as | Arcade (and Smithery) | | --- | --- | | Type | Connector platforms | | Also covers | auth provider, registry or directory | | Home | www.arcade.dev | | Price | platform fee plus per tool call; no published price for its other products | | Read | 5 November 2026 | ## What it does for this layer Arcade.dev announced on 5 Aug 2026 that it acquired Smithery and that Smithery co-founder Anirudh Kamath joined Arcade ([www.arcade.dev](https://www.arcade.dev/blog/smithery-joins-arcade)). Arcade calls itself "the actions runtime between your agents and every system they reach", one control point to enforce, execute and govern actions ([www.arcade.dev](https://www.arcade.dev/)). Arcade publishes a remote MCP server at https://api.arcade.dev/mcp/arcade for clients that support remote HTTP MCP and browser sign-in; that route includes tools only, without skills or commands ([www.arcade.dev](https://www.arcade.dev/)). Arcade installs as a plugin in Claude Code, Codex and Copilot CLI from the ArcadeAI/arcade-plugin marketplace repository ([www.arcade.dev](https://www.arcade.dev/)). Arcade's Free plan has no platform fee and 2,000 tool calls a month; Team is 25 USD a month plus 0.01 USD per tool call ([www.arcade.dev](https://www.arcade.dev/pricing)). Arcade Enterprise offers deployment on Arcade Cloud, in the customer's VPC or fully air-gapped ([www.arcade.dev](https://www.arcade.dev/pricing)). Arcade's docs cover server-level versus tool-level authorization and an Arcade MCP framework for building MCP servers ([docs.arcade.dev](https://docs.arcade.dev/)). Arcade's announcement describes Smithery as "a leading public registry and hosting platform for MCP" ([www.arcade.dev](https://www.arcade.dev/blog/smithery-joins-arcade), vendor's own claim). Arcade's docs say it handles OAuth, manages user tokens, enforces security policies and executes across "7,500+ agent-optimized tools" ([docs.arcade.dev](https://docs.arcade.dev/), vendor's own claim). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Arcade runtime | Tool execution, OAuth and policy for agents across Arcade's tool catalog. | platform fee plus per tool call; from 25 USD; Free: 2,000 tool calls a month (source, as of 5 November 2026) | | Arcade MCP framework | Framework and quickstart for building MCP servers. | price not read | | Smithery | Public MCP registry and hosting, acquired 5 Aug 2026. | price not read | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | arcade.dev | 89 of 100, grade A | 1 November 2026 | how it was taken | | Cloudflare agent-readiness scan | arcade.dev | 67 of 100, L5 Agent-Native; 10 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Arcade does not publish a separate price for Smithery on the pages read. ## Related on this site Hosts page - [Smithery](https://agentmcpdirectory.com/hosts/smithery/) Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/arcade/index.md) ## Sources - [Arcade: The Actions Runtime for Enterprise AI Agents](https://www.arcade.dev/), read 5 November 2026 - [Smithery Is Now Part of Arcade.dev](https://www.arcade.dev/blog/smithery-joins-arcade), read 5 November 2026 - [Arcade Docs](https://docs.arcade.dev/), read 5 November 2026 - [Pricing | Arcade](https://www.arcade.dev/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Auth0: MCP vendor profile | Agent MCP Directory" description: "Auth0: auth provider. Products: Auth for MCP. 10 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/auth0 site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Auth0: MCP vendor profile | Agent MCP Directory > Auth0: auth provider. Products: Auth for MCP. 10 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/auth0 Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth0: MCP vendor profile Auth0's Auth for MCP acts as the OAuth 2.1 authorization server for remote MCP servers, with CIMD and DCR client registration, on-behalf-of token exchange and Token Vault for third-party APIs, as documented by the vendor. Auth0 can put enterprise SSO in front of MCP servers through Okta, Entra ID, Ping and Google Workspace connections (auth0.com). ## At a glance | Listed as | Auth0 (Auth for MCP) | | --- | --- | | Type | Auth providers | | Operator | Okta | | Home | auth0.com | | Price | per monthly active user, AI Agents add-on | | Read | 5 November 2026 | ## What it does for this layer Auth0 announced general availability of Auth for MCP on 6 May 2026 ([auth0.com](https://auth0.com/blog/auth0-auth-for-mcp-servers-generally-available/)). In Auth0, a tenant admin registers an MCP client by giving its Client ID Metadata Document URL; Auth0 fetches and validates the metadata and shows it to the admin before creating the client ([auth0.com](https://auth0.com/blog/auth0-auth-for-mcp-servers-generally-available/)). An Auth0 tenant serves an OAuth 2.0 Authorization Server Metadata document at /.well-known/oauth-authorization-server, and Auth0 lists Dynamic Client Registration as a step that can follow the metadata response ([auth0.com](https://auth0.com/ai/docs/mcp/why-auth-for-mcp.md)). Auth0 Token Vault manages issuance, storage, rotation and revocation of tokens for third-party APIs such as Google, Microsoft, Jira and Notion that an MCP server calls ([auth0.com](https://auth0.com/ai/docs/mcp/overview.md)). The Auth for MCP guides include a Resource Parameter Compatibility Profile, an MCP Inspector test guide and a Cloudflare MCP guide ([auth0.com](https://auth0.com/ai/docs/mcp/overview.md)). Auth0 pricing lists a Free plan at 0 USD up to 25,000 monthly active users, Essentials from 35 USD a month (B2C) or 150 USD (B2B), and Professional from 240 USD (B2C) or 800 USD (B2B) ([auth0.com](https://auth0.com/pricing)). Auth0 for AI Agents is sold as a paid add-on priced by monthly active users; the B2C add-on includes unlimited Token Vault ([auth0.com](https://auth0.com/pricing)). Auth0 describes Auth for MCP as implementing "the authorization parts of the MCP spec with OAuth 2.1 and OpenID Connect" ([auth0.com](https://auth0.com/ai/docs/mcp/overview.md)). Auth0 supports On-Behalf-Of token exchange so an MCP server can trade the user's token for a short-lived token scoped to an internal API ([auth0.com](https://auth0.com/ai/docs/mcp/overview.md)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Auth for MCP | Authorization server, client registration, token exchange and Token Vault for MCP servers. | per monthly active user, AI Agents add-on; from 0 USD; Free plan up to 25,000 MAUs; AI Agents add-on priced by MAU tier (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | authorization server metadata | Supports | Tenant serves /.well-known/oauth-authorization-server for MCP clients. | auth0.com | | MCP | client ID metadata documents | Supports | GA release adds admin-confirmed CIMD client registration. | auth0.com | | MCP | dynamic client registration | Supports | DCR can follow the metadata response. | auth0.com | | MCP | resource parameter | Partial | Auth0 publishes a Resource Parameter Compatibility Profile guide rather than a plain statement of RFC 8707 support. | auth0.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | auth0.com | 74 of 100, grade B | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan | auth0.com | 27 of 100, L1 Basic Web Presence; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Auth0 does not host the MCP server; the server validates Auth0 tokens itself. ## Relation to Ora Auth0 sits on the AgentReady.org committee for auth, which Ora's launch post of 19 October 2026 describes as how agents sign in and act on a user's behalf ([ora.ai](https://ora.ai/blog/agentready-launch?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026). ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/auth0/index.md) ## Sources - [Auth0 home](https://auth0.com/ai/docs/mcp/overview), read 5 November 2026 - [Auth0 Auth for MCP Is Now Generally Available](https://auth0.com/blog/auth0-auth-for-mcp-servers-generally-available/), read 5 November 2026 - [Auth for MCP - Auth0 docs (markdown)](https://auth0.com/ai/docs/mcp/overview.md), read 5 November 2026 - [Why use Auth for MCP - Auth0 docs (markdown)](https://auth0.com/ai/docs/mcp/why-auth-for-mcp.md), read 5 November 2026 - [Auth0 pricing](https://auth0.com/pricing), read 5 November 2026 - [Introducing AgentReady.org: the first open standard for AX | Ora](https://ora.ai/blog/agentready-launch?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "AWS: MCP vendor profile | Agent MCP Directory" description: "AWS: host or runtime. Products: AgentCore Runtime, plus 2 more. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/aws-agentcore site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # AWS: MCP vendor profile | Agent MCP Directory > AWS: host or runtime. Products: AgentCore Runtime, plus 2 more. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/aws-agentcore Site: Agent MCP Directory Last reviewed: 2026-11-05 # AWS: MCP vendor profile Amazon Bedrock AgentCore runs MCP servers as containers in AgentCore Runtime and offers AgentCore Gateway, a managed entry point that turns APIs and Lambda functions into tools for agents, priced per call, as documented by the vendor. AgentCore Runtime adds an Mcp-Session-Id header to any MCP request that lacks one, so clients keep continuity with the same runtime session (docs.aws.amazon.com). ## At a glance | Listed as | AWS (Amazon Bedrock AgentCore) | | --- | --- | | Type | Hosts and runtimes | | Also covers | gateway or proxy, auth provider | | Operator | Amazon Web Services | | Home | aws.amazon.com | | Price | per vCPU-hour and GB-hour; per 1,000 invocations | | Read | 5 November 2026 | ## What it does for this layer AgentCore Runtime expects an MCP server container to listen at 0.0.0.0:8000/mcp, which AWS calls the default path of most official MCP server SDKs ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html)). AgentCore Runtime supports stateless and stateful streamable-HTTP MCP servers; stateless mode (stateless\_http=True) is recommended for basic servers, and stateful mode keeps session state for elicitation, sampling and progress notifications ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html)). AgentCore Gateway includes semantic search so agents can find tools by task context as the tool collection grows ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html)). AgentCore Gateway pricing is 0.005 USD per 1,000 API invocations such as ListTools, InvokeTool and Ping, 0.025 USD per 1,000 search calls, and 0.02 USD per 100 tools indexed a month ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)). AgentCore Identity carries no extra charge when used through AgentCore Runtime or AgentCore Gateway ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)). AgentCore Runtime v1 bills 0.0895 USD per vCPU-hour and 0.00945 USD per GB-hour of memory ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)). AgentCore Gateway can apply Policy checks to each tool call, billed per authorization request ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)). AWS describes AgentCore Gateway as "a fully managed AI gateway" that gives agents a single entry point to tools, other agents and LLMs, not only an MCP tool gateway ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | AgentCore Runtime | Serverless runtime for agents and MCP servers in containers. | per vCPU-hour and GB-hour; from 0.09 USD; v1 CPU per vCPU-hour (source, as of 5 November 2026) | | AgentCore Gateway | Managed gateway that exposes APIs, Lambda functions, agents and models as tools. | per 1,000 invocations; from 0.005 USD (source, as of 5 November 2026) | | AgentCore Identity | Agent identity and credential access for AWS and third-party services. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | streamable HTTP | Supports | Runtime runs stateless and stateful streamable-HTTP MCP servers. | docs.aws.amazon.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | aws.amazon.com | 60 of 100, grade C | 30 October 2026 | how it was taken | | Cloudflare agent-readiness scan | aws.amazon.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - AgentCore is not a public registry of third-party MCP servers. ## Related on this site Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/aws-agentcore/index.md) ## Sources - [AWS home](https://aws.amazon.com/bedrock/agentcore/), read 5 November 2026 - [Deploy MCP servers in AgentCore Runtime - AWS docs](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html), read 5 November 2026 - [Amazon Bedrock AgentCore Gateway - AWS docs](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html), read 5 November 2026 - [Amazon Bedrock AgentCore Pricing - AWS](https://aws.amazon.com/bedrock/agentcore/pricing/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Better Auth: MCP vendor profile | Agent MCP Directory" description: "Better Auth: auth provider. Products: @better-auth/mcp. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/better-auth site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Better Auth: MCP vendor profile | Agent MCP Directory > Better Auth: auth provider. Products: @better-auth/mcp. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/better-auth Site: Agent MCP Directory Last reviewed: 2026-11-05 # Better Auth: MCP vendor profile Better Auth is an open-source TypeScript authentication framework whose MCP plugin turns the app into an OAuth authorization server and protected resource for MCP clients, including the 2026-07-28 profile with CIMD, as documented by the vendor. mcp() configures MCP resource binding and serves RFC 9728 protected resource metadata (www.better-auth.com). ## At a glance | Listed as | Better Auth (MCP plugin) | | --- | --- | | Type | Auth providers | | Home | www.better-auth.com | | Price | open source | | Read | 5 November 2026 | ## What it does for this layer The Better Auth MCP plugin requires the JWT plugin, which provides the signing key for ID and access tokens and exposes a /jwks endpoint ([www.better-auth.com](https://www.better-auth.com/docs/plugins/mcp)). Better Auth's MCP plugin lets an app "act as an OAuth authorization server and protected resource" for MCP clients, built on its OAuth 2.1 Provider plugin ([www.better-auth.com](https://www.better-auth.com/docs/plugins/mcp)). For the MCP 2026-07-28 profile, Better Auth composes the MCP plugin with Client ID Metadata Documents through the @better-auth/cimd companion package ([www.better-auth.com](https://www.better-auth.com/docs/plugins/mcp)). Better Auth's MCP install uses @better-auth/mcp, @better-auth/cimd and version 2 of the official MCP TypeScript SDK (@modelcontextprotocol/server) ([www.better-auth.com](https://www.better-auth.com/docs/plugins/mcp)). Better Auth calls itself "The most comprehensive authentication framework for TypeScript" ([www.better-auth.com](https://www.better-auth.com/), vendor's own claim). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | @better-auth/mcp | Open-source plugin that makes a Better Auth app an MCP authorization server. | open source; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | spec revision | Supports | Documents a 2026-07-28 profile composed with CIMD. | www.better-auth.com | | MCP | protected resource metadata | Supports | Serves RFC 9728 protected resource metadata. | www.better-auth.com | | MCP | client ID metadata documents | Supports | @better-auth/cimd companion package. | www.better-auth.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | better-auth.com | 66 of 100, grade C | 16 September 2026 | how it was taken | | Cloudflare agent-readiness scan | better-auth.com | 7 of 100, L0 Not Ready; 1 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Better Auth is a library the developer runs; it is not a hosted identity service on the pages read. ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/better-auth/index.md) ## Sources - [MCP plugin - Better Auth docs](https://www.better-auth.com/docs/plugins/mcp), read 5 November 2026 - [Better Auth](https://www.better-auth.com/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Browserbase: MCP vendor profile | Agent MCP Directory" description: "Browserbase: host or runtime. Products: Browserbase MCP server. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/browserbase site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Browserbase: MCP vendor profile | Agent MCP Directory > Browserbase: host or runtime. Products: Browserbase MCP server. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/browserbase Site: Agent MCP Directory Last reviewed: 2026-11-05 # Browserbase: MCP vendor profile Browserbase runs cloud browsers for agents and an MCP server, built on Stagehand, that gives any MCP client a browser it can drive with natural-language commands and persistent sessions, as documented by the vendor. Browserbase's Free plan is 0 USD a month with 3 concurrent browsers, 1 browser hour, 15-minute sessions and 5 USD in model tokens (www.browserbase.com). ## At a glance | Type | Hosts and runtimes | | --- | --- | | Home | docs.browserbase.com | | Price | per plan | | Read | 5 November 2026 | ## What it does for this layer Browserbase MCP sessions can keep authentication state and cookies across multiple interactions ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/introduction)). Browserbase records detailed session replays and debugging information for MCP sessions ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/introduction)). Browserbase says every plan scales past its included usage with no caps or throttling, billed at the plan's rate ([www.browserbase.com](https://www.browserbase.com/pricing)). Browserbase says its MCP server "gives any MCP client a browser" and lets agents use the web with natural-language commands ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/introduction)). The Browserbase MCP server exposes explicit tools to create, reuse and close browser sessions ([docs.browserbase.com](https://docs.browserbase.com/integrations/mcp/introduction)). The Browserbase Developer plan is 20 USD a month with 25 concurrent browsers ([www.browserbase.com](https://www.browserbase.com/pricing)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Browserbase MCP server | Hosted MCP server that drives Browserbase browsers through Stagehand. | per plan; from 0 USD; Free: 1 browser hour; Developer 20 USD a month (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | browserbase.com | 84 of 100, grade B | 3 November 2026 | how it was taken | | Cloudflare agent-readiness scan | browserbase.com | 31 of 100, L1 Basic Web Presence; 5 of 16 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Browserbase does not host other MCP servers; its server exposes browser control. ## Related on this site Hosts page - [Browserbase MCP](https://agentmcpdirectory.com/hosts/browserbase/) Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/browserbase/index.md) ## Sources - [Browserbase MCP server - Browserbase Documentation](https://docs.browserbase.com/integrations/mcp/introduction), read 5 November 2026 - [Browserbase Pricing: Free, $20, $99, or Custom | Browserbase](https://www.browserbase.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP auth providers: vendor list | Agent MCP Directory" description: "Auth providers: 9 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain." canonical: https://agentmcpdirectory.com/vendors/by-type/auth-provider site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP auth providers: vendor list | Agent MCP Directory > Auth providers: 9 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain. Source: https://agentmcpdirectory.com/vendors/by-type/auth-provider Site: Agent MCP Directory Last reviewed: 2026-11-05 # Auth providers Vendors that sign agents and users in and issue the tokens a remote MCP server checks. 9 vendors typed here by main layer, each read on its own pages on 5 November 2026 and listed A to Z: Auth0, Better Auth, Clerk, Descope, Keycard, Logto, Scalekit, Stytch and WorkOS. Of these, 9 state at least one standard on the pages read, and 9 publish a price for at least one product. Other layers they also cover: gateway or proxy (2) and connector platform (1). ## Auth providers | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Auth0 | auth provider | Auth0's Auth for MCP acts as the OAuth 2.1 authorization server for remote MCP servers, with CIMD and DCR client registration, on-behalf-of token exchange and Token Vault for third-party APIs. | 3 supported, 1 partial MCP | per monthly active user, AI Agents add-on as of 2026-11-05 | 74 (B) scanned 2026-11-05 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Better Auth | auth provider | Better Auth is an open-source TypeScript authentication framework whose MCP plugin turns the app into an OAuth authorization server and protected resource for MCP clients, including the 2026-07-28 profile with CIMD. | 3 supported MCP | open source as of 2026-11-05 | 66 (C) scanned 2026-09-16 | 7 L0 Not Ready, 2026-11-05 | 2026-11-05 | | Clerk | auth provider | Clerk runs an OAuth server inside the customer's app that MCP servers built on Next.js or Express can use, with CIMD, DCR fallback and consent screens, and ships its own MCP server, CLI and agent skills. | 4 supported MCP, Agent Skills, CLIs | per retained user as of 2026-11-05 | 90 (A) scanned 2026-11-05 | 87 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Descope | auth provider | Descope acts as the authorization server for MCP servers: it publishes discovery metadata, registers clients by CIMD or DCR, runs login and consent, issues tokens and stores downstream credentials in a Connections vault. | 3 supported MCP | monthly base plus usage as of 2026-11-05 | 74 (B) scanned 2026-10-20 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Keycard | auth provider also gateway or proxy | Keycard gives each agent its own identity and issues scoped, just-in-time credentials at runtime, and puts MCP servers behind a unified access gateway with per-tool policy and an audit log. | 2 supported MCP, A2A | per transaction as of 2026-11-05 | 65 (C) scanned 2026-08-23 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Logto | auth provider | Logto is an open-source identity platform whose MCP guide makes Logto the authorization server for an MCP server through the mcp-auth library and MCP SDK v2, with the server registered as an API resource. | 1 supported MCP | monthly plus token usage as of 2026-11-05 | no cached score | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Scalekit | auth provider also gateway or proxy, connector platform | Scalekit is an OAuth 2.1 authorization server for MCP servers with DCR and CIMD, and also sells AgentKit, an MCP gateway with 600+ connectors and virtual MCP servers scoped by agent role. | 3 supported MCP | per tool call as of 2026-11-05 | 74 (B) scanned 2026-10-10 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Stytch | auth provider | Stytch Connected Apps turns an app into the OAuth authorization server for its remote MCP server, treating each MCP client as a Connected App that asks for consent through the authorization code grant. | 2 supported MCP | free tier then usage as of 2026-11-05 | 63 (C) scanned 2026-08-31 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | WorkOS | auth provider | WorkOS AuthKit is a spec-compatible OAuth authorization server for MCP servers, built on WorkOS Connect, with CIMD and optional DCR client registration and resource indicators. | 4 supported MCP | per MAU above 1 million, per connection as of 2026-11-05 | 86 (A) scanned 2026-11-04 | 40 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | ## Typed elsewhere, also covering this layer Auth providers - [Arcade](https://agentmcpdirectory.com/vendors/arcade/) - [AWS](https://agentmcpdirectory.com/vendors/aws-agentcore/) - [Cloudflare](https://agentmcpdirectory.com/vendors/cloudflare/) - [Nango](https://agentmcpdirectory.com/vendors/nango/) - [Pomerium](https://agentmcpdirectory.com/vendors/pomerium/) ## The other layers Layers - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) 10 - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) 8 - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) 13 - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) 9 - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) 6 - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) 8 - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) 10 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/by-type/auth-provider/index.md) ## Sources - [Auth0 home](https://auth0.com/ai/docs/mcp/overview), read 5 November 2026 - [MCP plugin - Better Auth docs](https://www.better-auth.com/docs/plugins/mcp), read 5 November 2026 - [Clerk home](https://clerk.com/), read 5 November 2026 - [MCP Authorization - Descope Documentation](https://docs.descope.com/mcp), read 5 November 2026 - [Keycard home](https://www.keycard.ai/), read 5 November 2026 - [Logto home](https://logto.io/), read 5 November 2026 - [Auth for MCP Servers: Drop-in OAuth 2.1 | Scalekit](https://www.scalekit.com/mcp-auth), read 5 November 2026 - [Stytch - A better way to build auth](https://stytch.com/), read 5 November 2026 - [Secure auth for MCP servers - WorkOS](https://workos.com/mcp), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP connector platforms: vendor list | Agent MCP Directory" description: "Connector platforms: 10 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain." canonical: https://agentmcpdirectory.com/vendors/by-type/connector-platform site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP connector platforms: vendor list | Agent MCP Directory > Connector platforms: 10 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain. Source: https://agentmcpdirectory.com/vendors/by-type/connector-platform Site: Agent MCP Directory Last reviewed: 2026-11-05 # Connector platforms Vendors that give agents ready-made, authenticated access to many apps through MCP. 10 vendors typed here by main layer, each read on its own pages on 5 November 2026 and listed A to Z: Activepieces, Arcade, Composio, Make, Merge, n8n, Nango, Pipedream, StackOne and Zapier. Of these, 4 state at least one standard on the pages read, and 5 publish a price for at least one product. Other layers they also cover: registry or directory (1), gateway or proxy (1) and auth provider (2). Merge and StackOne publish no price on the pages read. ## Connector platforms | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Activepieces | connector platform | Activepieces exposes its automation platform as one MCP server per project, so Claude, Cursor or another client can use 770+ connected apps as tools and build flows, free on every plan, cloud or self-hosted. | none recorded | included in every plan as of 2026-11-05 | 74 (B) scanned 2026-10-26 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Arcade | connector platform also auth provider, registry or directory | Arcade is an actions runtime that handles OAuth and user tokens and enforces policy on every agent tool call across 7,500+ tools; it acquired Smithery, the public MCP registry and hosting service, in August 2026. | none recorded | platform fee plus per tool call; no published price for its other products as of 2026-11-05 | 89 (A) scanned 2026-11-01 | 67 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Composio | connector platform | Composio gives agents per-user, authenticated access to 1000+ apps through a shared MCP server with seven meta-tools, per-session MCP endpoints, single-toolkit servers and agent plugins. | 1 supported CLIs | price not read | 83 (B) scanned 2026-10-26 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Make | connector platform | Make runs a hosted, stateless Streamable HTTP MCP server that lets Claude, ChatGPT and other clients run Make scenarios and manage scenarios, connections, webhooks and teams, scoped at connect time. | 2 supported MCP, Agent Skills | price not read | 78 (B) scanned 2026-11-02 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Merge | connector platform | Merge Agent Handler gives AI agents per-end-user access to 190+ MCP-ready third-party connectors through Tool Packs, with a Security Gateway that scans every tool call against data-loss rules. | none recorded | no published price | 65 (C) scanned 2026-10-26 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | n8n | connector platform | n8n includes a built-in MCP server per instance that lets MCP clients search workflows, run the ones marked available to MCP, and create or edit workflows and data tables, on n8n Cloud or self-hosted. | none recorded | price not read | 71 (B) scanned 2026-10-09 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Nango | connector platform also auth provider | Nango is an integration layer whose MCP Auth lets an app authorise each end user against external MCP servers such as Notion, Linear or HubSpot, store the tokens and call those servers through Nango's proxy. | 2 supported MCP | free tier, then credits as of 2026-11-05 | 65 (C) scanned 2026-10-26 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Pipedream | connector platform | Pipedream Connect runs a remote MCP server that gives agents per-user access to 3,000+ apps and 10,000+ prebuilt tools, with Pipedream managing OAuth and storing each user's credentials. | none recorded | free to build, paid in production as of 2026-11-05 | no cached score | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | StackOne | connector platform also gateway or proxy | StackOne runs a hosted MCP server and an enterprise Tool Gateway MCP that give agents 43,000+ actions across 630+ connectors, with per-account tool catalogs and StackOne handling provider authentication. | 1 supported A2A | no published price | 87 (A) scanned 2026-10-15 | 73 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Zapier | connector platform | Zapier MCP lets MCP clients run actions across Zapier's app catalogue, with each programmatic call drawn from the same monthly task allowance that powers Zap workflows. | none recorded | tasks from the plan allowance as of 2026-11-05 | 84 (B) scanned 2026-11-04 | 73 L5 Agent-Native, 2026-11-05 | 2026-11-05 | ## Typed elsewhere, also covering this layer Connector platforms - [Apify](https://agentmcpdirectory.com/vendors/apify/) - [Scalekit](https://agentmcpdirectory.com/vendors/scalekit/) ## The other layers Layers - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) 10 - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) 8 - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) 13 - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) 9 - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) 6 - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) 8 - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) 10 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/by-type/connector-platform/index.md) ## Sources - [MCP servers - 770+ apps for your AI | Activepieces](https://www.activepieces.com/mcp), read 5 November 2026 - [Arcade: The Actions Runtime for Enterprise AI Agents](https://www.arcade.dev/), read 5 November 2026 - [Composio home](https://composio.dev/), read 5 November 2026 - [Make MCP Server - Make Developer Hub](https://developers.make.com/mcp-server), read 5 November 2026 - [Merge home](https://www.merge.dev/agent-handler), read 5 November 2026 - [Connect to n8n MCP server - n8n Docs](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/), read 5 November 2026 - [Nango home](https://www.nango.dev/), read 5 November 2026 - [MCP Servers - Pipedream](https://pipedream.com/docs/connect/mcp), read 5 November 2026 - [AI Agent Integration Infrastructure | StackOne](https://www.stackone.com/), read 5 November 2026 - [Zapier home](https://zapier.com/mcp), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP gateways and proxies: vendor list | Agent MCP Directory" description: "Gateways and proxies: 13 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain." canonical: https://agentmcpdirectory.com/vendors/by-type/gateway site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP gateways and proxies: vendor list | Agent MCP Directory > Gateways and proxies: 13 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain. Source: https://agentmcpdirectory.com/vendors/by-type/gateway Site: Agent MCP Directory Last reviewed: 2026-11-05 # Gateways and proxies Vendors of gateways, proxies and control planes that sit between MCP clients and servers. 13 vendors typed here by main layer, each read on its own pages on 5 November 2026 and listed A to Z: Agent Router, agentgateway, Docker, IBM ContextForge, Kong, LiteLLM, Microsoft Azure, Mintive, Obot, Pomerium, Portkey, Speakeasy and Teleport. Of these, 11 state at least one standard on the pages read, and 9 publish a price for at least one product. Other layers they also cover: host or runtime (4), registry or directory (5) and auth provider (1). Mintive and Obot publish no price on the pages read. ## Gateways and proxies | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Agent Router | gateway or proxy | Agent Router, the renamed Envoy AI Gateway, is an open-source Envoy-based router that gives agents one OpenAI-compatible API for models and an MCPRoute gateway that aggregates and filters MCP servers. | 1 supported, 1 partial MCP | open source, Apache-2.0 as of 2026-11-05 | no cached score | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | agentgateway | gateway or proxy | agentgateway is an open-source Rust proxy, hosted as a Linux Foundation project, that routes and secures MCP, A2A, LLM and ordinary HTTP or gRPC traffic in one data plane. | 2 supported MCP, A2A | open source, Apache-2.0 as of 2026-11-05 | 50 (C) scanned 2026-11-01 | 13 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Docker | gateway or proxy also registry or directory, host or runtime | Docker packages MCP servers as container images in its MCP Catalog and runs them through the open-source MCP Gateway, which starts each server in an isolated container and injects credentials per call. | none recorded | open source, MIT as of 2026-11-05 | 69 (C) scanned 2026-10-11 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | IBM ContextForge | gateway or proxy also registry or directory | ContextForge is IBM's open-source registry and proxy that federates MCP servers, A2A agents and REST or gRPC APIs behind one MCP endpoint with guardrails, plugins and observability. | 2 supported MCP, A2A | open source, Apache-2.0 as of 2026-11-05 | no product domain | no scan | 2026-11-05 | | Kong | gateway or proxy also registry or directory | Kong turns APIs behind Kong Gateway or published in its Dev Portal into MCP servers, proxies MCP traffic with the AI MCP Proxy plugin, and lists an AI Registry product, on-premises or in Konnect. | 1 supported OpenAPI | AI Gateway Enterprise as of 2026-11-05 | 71 (B) scanned 2026-11-01 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | LiteLLM | gateway or proxy | LiteLLM is an open-source, self-hosted AI gateway whose proxy includes an MCP Gateway: one fixed endpoint for MCP tools, access controlled by API key and team, usable with any model LiteLLM routes. | 1 supported, 1 partial MCP | price not read | 73 (B) scanned 2026-11-01 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Microsoft Azure | gateway or proxy also host or runtime | Microsoft Azure exposes REST APIs as remote MCP servers through API Management's AI gateway, hosts MCP tool functions with the Azure Functions MCP extension, and publishes an open-source MCP Gateway for Kubernetes. | 1 partial MCP | open source, MIT as of 2026-11-05 | 24 (F) scanned 2026-10-15 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Mintive | gateway or proxy also host or runtime | Mintive, formerly MintMCP, sells a managed MCP gateway that hosts approved MCP servers, groups them into role-based bundles, gives agents their own credentials and logs every call. | none recorded | no published price | no cached score | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Obot | gateway or proxy also host or runtime, registry or directory | Obot is an open-source platform that hosts MCP servers, exposes them through a governed MCP gateway as virtual MCP servers, and keeps MCP and Agent Skills catalogs behind the MCP Registry API. | 2 supported MCP, Agent Skills | no published price | 67 (C) scanned 2026-10-09 | 33 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Pomerium | gateway or proxy also auth provider | Pomerium is an identity-aware proxy that puts internal or third-party MCP servers behind one gateway, runs downstream OAuth 2.1 and upstream OAuth for them, and limits tool calls by policy. | 2 supported MCP | per user per month as of 2026-11-05 | 59 (C) scanned 2026-08-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Portkey | gateway or proxy | Portkey, now presented as Palo Alto Networks Prisma AIRS AI Gateway, runs an MCP Gateway with a central registry of servers and tools, identity-provider sign-in and per-user tool policy, self-hosted or managed. | 1 supported MCP | open source, MIT as of 2026-11-05 | 69 (C) scanned 2026-10-20 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Speakeasy | gateway or proxy also registry or directory | Speakeasy now sells an AI control plane centred on an MCP gateway that discovers the MCP servers employees use, promotes approved ones into an internal registry and provisions them by IdP role. | 1 supported MCP | usage, no platform fee as of 2026-11-05 | 92 (A) scanned 2026-10-30 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Teleport | gateway or proxy | Teleport enrolls MCP servers as resources in a Teleport cluster, so engineers and AI clients reach them through Teleport with role-based permissions, audit and short-lived identity. | 1 supported MCP | price not read | 59 (C) scanned 2026-08-25 | 27 L2 Bot-Aware, 2026-11-05 | 2026-11-05 | ## Typed elsewhere, also covering this layer Gateways and proxies - [Akto](https://agentmcpdirectory.com/vendors/akto/) - [AWS](https://agentmcpdirectory.com/vendors/aws-agentcore/) - [Cloudflare](https://agentmcpdirectory.com/vendors/cloudflare/) - [Enkrypt AI](https://agentmcpdirectory.com/vendors/enkrypt-ai/) - [FastMCP and FastMCP Gateway](https://agentmcpdirectory.com/vendors/prefect-fastmcp/) - [Glama](https://agentmcpdirectory.com/vendors/glama/) - [Keycard](https://agentmcpdirectory.com/vendors/keycard/) - [Lasso Security](https://agentmcpdirectory.com/vendors/lasso-security/) - [Scalekit](https://agentmcpdirectory.com/vendors/scalekit/) - [StackOne](https://agentmcpdirectory.com/vendors/stackone/) - [Vercel](https://agentmcpdirectory.com/vendors/vercel/) ## The other layers Layers - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) 10 - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) 8 - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) 13 - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) 9 - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) 6 - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) 8 - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) 10 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/by-type/gateway/index.md) ## Sources - [Agent Router](https://aigateway.envoyproxy.io/), read 5 November 2026 - [agentgateway | Agent Connectivity Solved](https://agentgateway.dev/), read 5 November 2026 - [Docker MCP Catalog and Toolkit - Docker docs](https://docs.docker.com/ai/mcp-catalog-and-toolkit/), read 5 November 2026 - [GitHub - IBM/mcp-context-forge (ContextForge)](https://github.com/IBM/mcp-context-forge), read 5 November 2026 - [developer.konghq.com/mcp/](https://developer.konghq.com/mcp/), read 5 November 2026 - [LiteLLM - Open-Source AI Gateway & LLM Proxy](https://www.litellm.ai/), read 5 November 2026 - [Expose REST API as MCP server - Azure API Management | Microsoft Learn](https://learn.microsoft.com/en-us/azure/api-management/export-rest-mcp-server), read 5 November 2026 - [Mintive home](https://www.mintive.com/), read 5 November 2026 - [Obot home](https://obot.ai/), read 5 November 2026 - [Model Context Protocol (MCP) Support | Pomerium](https://www.pomerium.com/docs/capabilities/mcp), read 5 November 2026 - [Portkey home](https://portkey.ai/), read 5 November 2026 - [Speakeasy home](https://www.speakeasy.com/product/mcp-gateway), read 5 November 2026 - [goteleport.com/docs/enroll-resources/mcp-access/](https://goteleport.com/docs/enroll-resources/mcp-access/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP hosts and runtimes: vendor list | Agent MCP Directory" description: "Hosts and runtimes: 10 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain." canonical: https://agentmcpdirectory.com/vendors/by-type/host site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP hosts and runtimes: vendor list | Agent MCP Directory > Hosts and runtimes: 10 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain. Source: https://agentmcpdirectory.com/vendors/by-type/host Site: Agent MCP Directory Last reviewed: 2026-11-05 # Hosts and runtimes Vendors that run a remote MCP server for you: hosting platforms, runtimes and deploy tools. 10 vendors typed here by main layer, each read on its own pages on 5 November 2026 and listed A to Z: Alpic, Apify, AWS, Browserbase, Cloudflare, Google Cloud Run, Manufact, Mintlify, Netlify and Vercel. Of these, 6 state at least one standard on the pages read, and 8 publish a price for at least one product. Other layers they also cover: gateway or proxy (3), auth provider (2), SDK or framework (3) and connector platform (1). ## Hosts and runtimes | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Alpic | host or runtime also SDK or framework | Alpic is a cloud platform that deploys MCP servers and ChatGPT or Claude apps with no configuration, adds AI-specific analytics and session replay, and maintains Skybridge, an open-source MCP Apps framework. | none recorded | per request as of 2026-11-05 | 86 (A) scanned 2026-10-23 | 47 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Apify | host or runtime also connector platform | Apify runs a hosted MCP server that lets agents search, call and pay for Apify Actors, the scrapers and automations on its platform, with tool sets chosen through URL parameters. | none recorded | usage of Actors as of 2026-11-05 | 96 (A+) scanned 2026-11-04 | 73 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | AWS | host or runtime also gateway or proxy, auth provider | Amazon Bedrock AgentCore runs MCP servers as containers in AgentCore Runtime and offers AgentCore Gateway, a managed entry point that turns APIs and Lambda functions into tools for agents, priced per call. | 1 supported MCP | per vCPU-hour and GB-hour; per 1,000 invocations as of 2026-11-05 | 60 (C) scanned 2026-10-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Browserbase | host or runtime | Browserbase runs cloud browsers for agents and an MCP server, built on Stagehand, that gives any MCP client a browser it can drive with natural-language commands and persistent sessions. | none recorded | per plan as of 2026-11-05 | 84 (B) scanned 2026-11-03 | 31 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Cloudflare | host or runtime also gateway or proxy, auth provider | Cloudflare hosts remote MCP servers on Workers through the Agents SDK, ships the Workers OAuth Provider for both sides of MCP authorization, and fronts servers with MCP server portals and AI Gateway. | 4 supported MCP | Workers Paid minimum as of 2026-11-05 | 82 (B) scanned 2026-11-05 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Google Cloud Run | host or runtime | Google Cloud Run hosts remote MCP servers built with the official SDKs or FastMCP as streamable-HTTP services, with access controlled by IAM and a local proxy command for developer clients. | 1 supported MCP | price not read | 51 (C) scanned 2026-10-28 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Manufact | host or runtime also SDK or framework | Manufact pairs mcp-use, an open-source TypeScript and Python SDK for MCP servers and apps, with Manufact Cloud, which deploys MCP servers from GitHub and tests them across ChatGPT, Claude and coding agents. | none recorded | open source; credits plus usage as of 2026-11-05 | 83 (B) scanned 2026-11-04 | 60 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Mintlify | host or runtime | Mintlify generates and hosts a search MCP server for every docs site it builds, exposes skill files as MCP resources, registers WebMCP tools on Pro plans, and scores docs sites for agent readability. | 1 supported, 1 partial WebMCP, Agent Skills | included from Starter; Pro and Enterprise as of 2026-11-05 | 74 (B) scanned 2026-11-05 | 47 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Netlify | host or runtime | Netlify hosts stateless MCP servers as serverless functions answering at /mcp, publishes a deploy-button template, and runs its own remote Netlify MCP server for coding agents. | 1 supported MCP | price not read | 90 (A) scanned 2026-11-04 | 67 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Vercel | host or runtime also SDK or framework, gateway or proxy | Vercel hosts MCP servers built with mcp-handler as Vercel Functions, runs its own remote Vercel MCP server, and ships an MCP client in the AI SDK alongside the AI Gateway for model traffic. | 1 supported MCP | per plan plus usage as of 2026-11-05 | 91 (A) scanned 2026-11-05 | 60 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | ## Typed elsewhere, also covering this layer Hosts and runtimes - [Docker](https://agentmcpdirectory.com/vendors/docker/) - [FastMCP and FastMCP Gateway](https://agentmcpdirectory.com/vendors/prefect-fastmcp/) - [GitHub](https://agentmcpdirectory.com/vendors/github/) - [Glama](https://agentmcpdirectory.com/vendors/glama/) - [Microsoft Azure](https://agentmcpdirectory.com/vendors/microsoft-azure/) - [Mintive](https://agentmcpdirectory.com/vendors/mintive/) - [Obot](https://agentmcpdirectory.com/vendors/obot/) ## The other layers Layers - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) 10 - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) 8 - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) 13 - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) 9 - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) 6 - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) 8 - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) 10 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/by-type/host/index.md) ## Sources - [Alpic: build, deploy, monitor and distribute your ChatGPT Apps and MCP servers](https://alpic.ai/), read 5 November 2026 - [Apify MCP server - Apify docs](https://docs.apify.com/platform/integrations/mcp), read 5 November 2026 - [AWS home](https://aws.amazon.com/bedrock/agentcore/), read 5 November 2026 - [Browserbase MCP server - Browserbase Documentation](https://docs.browserbase.com/integrations/mcp/introduction), read 5 November 2026 - [Model Context Protocol (MCP) · Cloudflare Agents docs](https://developers.cloudflare.com/agents/model-context-protocol/), read 5 November 2026 - [Host MCP servers on Cloud Run  |  Google Cloud Documentation](https://cloud.google.com/run/docs/host-mcp-servers), read 5 November 2026 - [manufact.com/](https://manufact.com/), read 5 November 2026 - [Mintlify home](https://www.mintlify.com/docs/ai/model-context-protocol), read 5 November 2026 - [Building MCPs with Netlify - Netlify Developers](https://developers.netlify.com/guides/write-mcps-on-netlify/), read 5 November 2026 - [Model Context Protocol](https://vercel.com/docs/mcp), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP registries and directories: vendor list | Agent MCP Directory" description: "Registries and directories: 8 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain." canonical: https://agentmcpdirectory.com/vendors/by-type/registry site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP registries and directories: vendor list | Agent MCP Directory > Registries and directories: 8 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain. Source: https://agentmcpdirectory.com/vendors/by-type/registry Site: Agent MCP Directory Last reviewed: 2026-11-05 # Registries and directories Vendors that list MCP servers so that a client or an agent can find them. 8 vendors typed here by main layer, each read on its own pages on 5 November 2026 and listed A to Z: Anthropic, GitHub, Glama, MCP Market, Official MCP Registry, OpenAI, Ora and PulseMCP. Of these, 7 state at least one standard on the pages read, and 2 publish a price for at least one product. Other layers they also cover: host or runtime (2), gateway or proxy (1) and SDK or framework (2). Glama publishes no price on the pages read. ## Registries and directories | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Anthropic | registry or directory also SDK or framework | Anthropic runs the Claude Connectors Directory of reviewed remote MCP servers and an MCP connector in the Claude Messages API that calls remote MCP tools without the developer writing an MCP client. | 1 supported, 1 partial MCP | price not read | 62 (C) scanned 2026-10-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | GitHub | registry or directory also host or runtime | GitHub runs a curated MCP Registry for partner and community servers, hosts its own remote GitHub MCP server, and lets Copilot surfaces use MCP servers under an organisation policy that is off by default. | none recorded | price not read | 65 (C) scanned 2026-11-01 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Glama | registry or directory also host or runtime, gateway or proxy | Glama runs a public MCP server directory that counted 116,152 servers on 5 Nov 2026, and also hosts MCP servers on dedicated machines behind its own MCP gateway, with per-tool access control and full call logs. | 1 supported MCP | no published price | 80 (B) scanned 2026-10-19 | 47 L2 Bot-Aware, 2026-11-05 | 2026-11-05 | | MCP Market | registry or directory | MCP Market is a public directory of MCP servers, agent skills and MCP clients, sorted by category, with a section for official servers and a marketplace for selling skills. | 1 supported Agent Skills | price not read | 60 (C) scanned 2026-10-19 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Official MCP Registry | registry or directory | The official MCP Registry is the protocol project's central metadata store for public MCP servers, meant to be read by downstream marketplaces and private registries rather than directly by host applications. | 1 supported MCP | free as of 2026-11-05 | no cached score | 0 L0 Not Ready, 2026-11-05 | 2026-11-05 | | OpenAI | registry or directory also SDK or framework | OpenAI's developer docs, formerly the Apps SDK, cover plugins that bundle MCP servers, skills and optional UI for ChatGPT and Codex, and a public directory that reviews remote MCP servers before listing. | 3 supported MCP, Agent Skills | price not read | 58 (C) scanned 2026-11-05 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Ora | registry or directory | Ora scores domains, MCP server URLs and MCP Apps for agent readiness, lists scored products in a searchable directory, and exposes the same scan through a public MCP server and the ax CLI. | 8 supported, 1 partial MCP, WebMCP, CLIs, A2A, NLWeb, Agent Skills, OpenAPI | free, rate-limited by IP as of 2026-11-05 | 95 (A+) scanned 2026-11-05 | 75 L5 Agent-Native, 2026-11-05T14:39:47Z | 2026-11-05 | | PulseMCP | registry or directory | PulseMCP is an independent MCP directory of servers, clients and MCP Apps with The Agentic Loop newsletter, and offers partners an enriched registry API built on the official MCP Registry. | 1 supported MCP | price not read | 11 (F) scanned 2026-05-27 | 27 L2 Bot-Aware, 2026-11-05 | 2026-11-05 | ## Typed elsewhere, also covering this layer Registries and directories - [Arcade](https://agentmcpdirectory.com/vendors/arcade/) - [Docker](https://agentmcpdirectory.com/vendors/docker/) - [IBM ContextForge](https://agentmcpdirectory.com/vendors/ibm-contextforge/) - [Kong](https://agentmcpdirectory.com/vendors/kong/) - [Obot](https://agentmcpdirectory.com/vendors/obot/) - [Speakeasy](https://agentmcpdirectory.com/vendors/speakeasy/) ## The other layers Layers - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) 10 - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) 8 - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) 13 - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) 9 - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) 6 - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) 8 - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) 10 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/by-type/registry/index.md) ## Sources - [Anthropic home](https://claude.com/connectors), read 5 November 2026 - [GitHub home](https://github.com/mcp), read 5 November 2026 - [Glama MCP servers directory](https://glama.ai/mcp/servers), read 5 November 2026 - [MCP Market | Discover Top MCP Servers & Agent Skills](https://mcpmarket.com/), read 5 November 2026 - [Official MCP Registry home](https://registry.modelcontextprotocol.io/), read 5 November 2026 - [developers.openai.com/apps-sdk](https://developers.openai.com/apps-sdk), read 5 November 2026 - [Ora | Make your site work for agents](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=index), read 5 November 2026 - [PulseMCP | Keep up-to-date with MCP](https://www.pulsemcp.com/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP SDKs and frameworks: vendor list | Agent MCP Directory" description: "SDKs and frameworks: 8 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain." canonical: https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP SDKs and frameworks: vendor list | Agent MCP Directory > SDKs and frameworks: 8 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain. Source: https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework Site: Agent MCP Directory Last reviewed: 2026-11-05 # SDKs and frameworks Vendors of libraries and frameworks for building MCP servers and clients. 8 vendors typed here by main layer, each read on its own pages on 5 November 2026 and listed A to Z: FastMCP and FastMCP Gateway, LangChain, Mastra, MCP official SDKs, Pydantic AI, Spring AI, Stainless and xmcp. Of these, 4 state at least one standard on the pages read, and 8 publish a price for at least one product. Other layers they also cover: host or runtime (1) and gateway or proxy (1). ## SDKs and frameworks | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | FastMCP and FastMCP Gateway | SDK or framework also host or runtime, gateway or proxy | FastMCP is Prefect's open-source Python framework for MCP servers, clients and apps, and FastMCP Gateway is Prefect's commercial service that hosts and governs FastMCP servers from a git push. | 1 supported MCP | open source, Apache-2.0; free start, paid plans as of 2026-11-05 | 63 (C) scanned 2026-09-07 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | LangChain | SDK or framework | LangChain connects its agents to MCP servers through MCPAdapter, built on FastMCP, which discovers a server's tools and adapts them into LangChain tools; the older langchain-mcp-adapters package remains on GitHub. | none recorded | open source as of 2026-11-05 | 74 (B) scanned 2026-10-17 | 7 L0 Not Ready, 2026-11-05 | 2026-11-05 | | Mastra | SDK or framework | Mastra is an open-source TypeScript agent framework whose @mastra/mcp package provides an MCP client for agents and an MCPServer that exposes Mastra tools and agents to external MCP clients. | none recorded | open source; monthly plus usage as of 2026-11-05 | 78 (B) scanned 2026-11-01 | 33 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | MCP official SDKs | SDK or framework | The Model Context Protocol project publishes ten official SDKs, ranked in three tiers by feature completeness, protocol support and maintenance commitment, for building MCP servers and clients. | 1 supported MCP | open source as of 2026-11-05 | 69 (C) scanned 2026-10-16 | 53 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Pydantic AI | SDK or framework | Pydantic AI is a Python agent framework that connects agents to MCP servers through an MCP capability, runs servers locally by default with an opt-in for model providers' native MCP, and can serve agents as MCP servers. | none recorded | open source as of 2026-11-05 | 90 (A) scanned 2026-11-04 | 60 L5 Agent-Native, 2026-11-05 | 2026-11-05 | | Spring AI | SDK or framework | Spring AI builds on the MCP Java SDK with Spring Boot starters for MCP clients and servers, annotation-based tool handling, and the Spring WebFlux and WebMVC transports. | 1 supported MCP | open source as of 2026-11-05 | 58 (C) scanned 2026-04-24 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Stainless | SDK or framework | Stainless generates an MCP server from an OpenAPI spec as a subpackage of a generated TypeScript SDK, exposing a code execution tool and a docs search tool instead of one tool per endpoint. | 1 supported OpenAPI | per generator as of 2026-11-05 | 58 (C) scanned 2026-09-10 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | xmcp | SDK or framework | xmcp is a TypeScript framework from basement.studio that registers MCP tools, prompts and resources from project files and ships adapters for Next.js and Express plus auth and payment integrations. | none recorded | open source as of 2026-11-05 | 57 (C) scanned 2026-09-16 | 47 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | ## Typed elsewhere, also covering this layer SDKs and frameworks - [Alpic](https://agentmcpdirectory.com/vendors/alpic/) - [Anthropic](https://agentmcpdirectory.com/vendors/anthropic/) - [Manufact](https://agentmcpdirectory.com/vendors/manufact/) - [OpenAI](https://agentmcpdirectory.com/vendors/openai/) - [Vercel](https://agentmcpdirectory.com/vendors/vercel/) ## The other layers Layers - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) 10 - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) 8 - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) 13 - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) 9 - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) 6 - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) 8 - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) 10 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/index.md) ## Sources - [FastMCP: The Framework for MCP - FastMCP](https://gofastmcp.com/), read 5 November 2026 - [Model Context Protocol (MCP) - Docs by LangChain](https://docs.langchain.com/oss/python/langchain/mcp), read 5 November 2026 - [Mastra home](https://mastra.ai/), read 5 November 2026 - [SDKs - Model Context Protocol](https://modelcontextprotocol.io/docs/sdk), read 5 November 2026 (the project's own page) - [Model Context Protocol (MCP) | Pydantic Docs](https://ai.pydantic.dev/mcp/), read 5 November 2026 - [Model Context Protocol (MCP) :: Spring AI Reference](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html), read 5 November 2026 - [Stainless - MCP Portal](https://www.stainless.com/mcp), read 5 November 2026 - [xmcp.dev/](https://xmcp.dev/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP security scanners: vendor list | Agent MCP Directory" description: "Security scanners: 6 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain." canonical: https://agentmcpdirectory.com/vendors/by-type/security-scanner site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP security scanners: vendor list | Agent MCP Directory > Security scanners: 6 MCP vendors read on 5 November 2026, each with dated facts, prices and standards. Two checks on each domain. Source: https://agentmcpdirectory.com/vendors/by-type/security-scanner Site: Agent MCP Directory Last reviewed: 2026-11-05 # Security scanners Vendors that check MCP servers, tools and tool descriptions for risk. 6 vendors typed here by main layer, each read on its own pages on 5 November 2026 and listed A to Z: Akto, Cisco MCP Scanner, Enkrypt AI, Lasso Security, Snyk Agent Scan and Trail of Bits mcp-context-protector. Of these, 1 states at least one standard on the pages read, and 3 publish a price for at least one product. Other layers they also cover: gateway or proxy (3). Akto and Enkrypt AI publish no price on the pages read. ## Security scanners | Vendor | Type | What it does for this layer | Standards stated | Pricing | Ora score | Cloudflare scan | Last read | | --- | --- | --- | --- | --- | --- | --- | --- | | Akto | security scanner also gateway or proxy | Akto's MCP Security module finds MCP servers in a company's networks, probes them for prompt injection, tool poisoning and excessive permissions, and can route MCP tool calls through an inspecting agent-proxy. | none recorded | no published price | 62 (C) scanned 2026-09-05 | 27 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Cisco MCP Scanner | security scanner | Cisco's open-source MCP Scanner checks MCP servers, tools, prompts and resources for malicious content by combining YARA rules, an LLM judge and the Cisco AI Defense inspect API. | none recorded | open source, Apache-2.0 as of 2026-11-05 | 33 (D) scanned 2026-10-30 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Enkrypt AI | security scanner also gateway or proxy | Enkrypt AI sells an MCP Scanner that inventories MCP servers and tools and flags injection and over-privilege risks, and publishes an open-source inline MCP Gateway that approves, modifies or blocks tool calls. | none recorded | no published price | no cached score | 13 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Lasso Security | security scanner also gateway or proxy | Lasso Security publishes an open-source, plugin-based MCP gateway that masks secrets and personal data in traffic and scans MCP servers by reputation and tool descriptions before loading them. | none recorded | open source, MIT; no published price for its other products as of 2026-11-05 | 51 (C) scanned 2026-08-31 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | | Snyk Agent Scan | security scanner | Snyk Agent Scan, the former Invariant Labs mcp-scan, discovers agent configurations on a machine and scans their MCP servers, tools, prompts, resources and skills for prompt injection and other risks. | 1 supported Agent Skills | price not read | 79 (B) scanned 2026-11-05 | 40 L4 Agent-Integrated, 2026-11-05 | 2026-11-05 | | Trail of Bits mcp-context-protector | security scanner | mcp-context-protector from Trail of Bits wraps MCP servers to pin their configuration on first use, quarantine tool responses flagged by guardrails and strip ANSI control characters. | none recorded | open source, Apache-2.0 as of 2026-11-05 | 47 (D) scanned 2026-08-25 | 20 L1 Basic Web Presence, 2026-11-05 | 2026-11-05 | These scanners look for injection and over-privilege in a server's tools. To check whether agents can find, read and use a server, [Ora is the pick](https://agentmcpdirectory.com/test-your-mcp-server/), with the limits and the alternatives on that page. ## The other layers Layers - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) 10 - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) 8 - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) 13 - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) 9 - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) 6 - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) 8 - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) 10 Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/by-type/security-scanner/index.md) ## Sources - [Akto MCP Security Solution | MCP Vendor Security](https://www.akto.io/mcp-security), read 5 November 2026 - [GitHub - cisco-ai-defense/mcp-scanner](https://github.com/cisco-ai-defense/mcp-scanner), read 5 November 2026 - [Enkrypt AI MCP Scanner: Advanced AI Threat Detection & Security](https://www.enkryptai.com/product/mcp-scanner), read 5 November 2026 - [Secure AI Adoption at Enterprise Scale | Lasso](https://www.lasso.security/), read 5 November 2026 - [GitHub - snyk/agent-scan (formerly invariantlabs-ai/mcp-scan)](https://github.com/snyk/agent-scan), read 5 November 2026 - [GitHub - trailofbits/mcp-context-protector](https://github.com/trailofbits/mcp-context-protector), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Cisco MCP Scanner: MCP vendor profile | Agent MCP Directory" description: "Cisco MCP Scanner: security scanner. Products: MCP Scanner. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/cisco-mcp-scanner site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Cisco MCP Scanner: MCP vendor profile | Agent MCP Directory > Cisco MCP Scanner: security scanner. Products: MCP Scanner. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/cisco-mcp-scanner Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cisco MCP Scanner: MCP vendor profile Cisco's open-source MCP Scanner checks MCP servers, tools, prompts and resources for malicious content by combining YARA rules, an LLM judge and the Cisco AI Defense inspect API, as documented by the vendor. The README gives a CI example that runs a YARA-only scan with no API keys needed (github.com). ## At a glance | Listed as | Cisco MCP Scanner (AI Defense) | | --- | --- | | Type | Security scanners | | Operator | Cisco | | Home | github.com | | Price | open source, Apache-2.0 | | Read | 5 November 2026 | ## What it does for this layer Cisco licenses MCP Scanner under Apache-2.0, and its GitHub page showed about 1.1k stars on 5 Nov 2026 ([github.com](https://github.com/cisco-ai-defense/mcp-scanner), observed 5 November 2026). The README configures the LLM analyzer with model providers including AWS Bedrock Claude through an API key bearer token ([github.com](https://github.com/cisco-ai-defense/mcp-scanner)). The repository's About section links the Cisco blog post at blogs.cisco.com/ai/securing-the-ai-agent-supply-chain-with-ciscos-open-source-mcp-scanner ([github.com](https://github.com/cisco-ai-defense/mcp-scanner)). Cisco's MCP Scanner "combines Cisco AI Defense inspect API, YARA rules and LLM-based analysis to detect malicious MCP tools" ([github.com](https://github.com/cisco-ai-defense/mcp-scanner)). The scanner's analyzers are selected with --analyzers, for example yara, llm and api, and can be run one at a time ([github.com](https://github.com/cisco-ai-defense/mcp-scanner)). Cisco MCP Scanner can scan the prompts and resources of a server as well as its tools, over remote or stdio connections ([github.com](https://github.com/cisco-ai-defense/mcp-scanner)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Scanner | Open-source Python scanner for MCP servers with YARA, LLM and API analyzers. | open source, Apache-2.0; from 0 USD; The API analyzer needs Cisco AI Defense access (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | cisco.com | 33 of 100, grade D | 30 October 2026 | how it was taken | | Cloudflare agent-readiness scan | cisco.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Cisco MCP Scanner does not block calls at runtime; it reports findings from scans. - The API analyzer does not work without Cisco AI Defense credentials; YARA-only scans do. ## Related on this site Type - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/cisco-mcp-scanner/index.md) ## Sources - [GitHub - cisco-ai-defense/mcp-scanner](https://github.com/cisco-ai-defense/mcp-scanner), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Clerk: MCP vendor profile | Agent MCP Directory" description: "Clerk: auth provider. Products: OAuth server for MCP. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/clerk site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Clerk: MCP vendor profile | Agent MCP Directory > Clerk: auth provider. Products: OAuth server for MCP. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/clerk Site: Agent MCP Directory Last reviewed: 2026-11-05 # Clerk: MCP vendor profile Clerk runs an OAuth server inside the customer's app that MCP servers built on Next.js or Express can use, with CIMD, DCR fallback and consent screens, and ships its own MCP server, CLI and agent skills, as documented by the vendor. ## At a glance | Type | Auth providers | | --- | --- | | Home | clerk.com | | Price | per retained user | | Read | 5 November 2026 | ## What it does for this layer Clerk says it supports MCP "through Client ID Metadata Documents (CIMD), Dynamic Client Registration for clients that still require it, OAuth consent screens, and SDK support" ([clerk.com](https://clerk.com/docs/guides/development/mcp/overview)). Clerk runs its own MCP server that lets coding agents manage Clerk applications, users and production setup; the user signs in with a Clerk account when the client connects ([clerk.com](https://clerk.com/docs/guides/development/mcp/overview)). Clerk Agent Tasks create authenticated sessions on a user's behalf without the standard sign-in flow, for agent workflows ([clerk.com](https://clerk.com/docs/guides/development/mcp/overview)). Clerk bills on monthly retained users rather than monthly active users; a user who signs up and never returns after the first 24 hours is not billed ([clerk.com](https://clerk.com/pricing)). Clerk pricing lists Hobby free with 50,000 retained users per app, Pro at 25 USD a month (20 USD billed annually) and a 300 USD a month tier ([clerk.com](https://clerk.com/pricing)). Clerk Pro includes 50,000 retained users per app, then 0.02 USD per additional user a month, and one SSO connection with more at 75 USD a month each ([clerk.com](https://clerk.com/pricing)). Clerk ships agent skills installed with npx skills add clerk/skills and a CLI started with npx clerk@latest init ([clerk.com](https://clerk.com/docs/guides/development/mcp/overview)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | OAuth server for MCP | OAuth server with CIMD, DCR and consent screens for MCP servers built in Next.js or Express. | per retained user; from 0 USD; Hobby free to 50,000 MRUs per app (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | client ID metadata documents | Supports | Clerk lists CIMD support for MCP. | clerk.com | | MCP | dynamic client registration | Supports | DCR kept for clients that still require it. | clerk.com | | Agent Skills | skills package | Supports | clerk/skills installable for coding agents. | clerk.com | | CLIs | Clerk CLI | Supports | npx clerk@latest init with agent mode detection. | clerk.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | clerk.com | 90 of 100, grade A | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan | clerk.com | 87 of 100, L5 Agent-Native; 13 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Clerk does not host MCP servers; its guides cover Next.js and Express apps the developer deploys ([clerk.com](https://clerk.com/docs/guides/ai/mcp/build-mcp-server)). ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) - [CLIs](https://agentmcpdirectory.com/standards/cli-as-agent-surface/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/clerk/index.md) ## Sources - [Clerk home](https://clerk.com/), read 5 November 2026 - [clerk.com/docs/guides/development/mcp/overview](https://clerk.com/docs/guides/development/mcp/overview), read 5 November 2026 - [clerk.com/pricing](https://clerk.com/pricing), read 5 November 2026 - [clerk.com/docs/guides/ai/mcp/build-mcp-server](https://clerk.com/docs/guides/ai/mcp/build-mcp-server), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Cloudflare: MCP vendor profile | Agent MCP Directory" description: "Cloudflare: host or runtime. 4 products, 10 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/cloudflare site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Cloudflare: MCP vendor profile | Agent MCP Directory > Cloudflare: host or runtime. 4 products, 10 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/cloudflare Site: Agent MCP Directory Last reviewed: 2026-11-05 # Cloudflare: MCP vendor profile Cloudflare hosts remote MCP servers on Workers through the Agents SDK, ships the Workers OAuth Provider for both sides of MCP authorization, and fronts servers with MCP server portals and AI Gateway, as documented by the vendor. Cloudflare's MCP overview, last updated 27 Oct 2026, says remote MCP connections use Streamable HTTP with OAuth and local connections use stdio (developers.cloudflare.com). ## At a glance | Listed as | Cloudflare (Workers, Agents SDK, MCP portals, AI Gateway) | | --- | --- | | Type | Hosts and runtimes | | Also covers | gateway or proxy, auth provider | | Home | developers.cloudflare.com | | Price | Workers Paid minimum | | Read | 5 November 2026 | ## What it does for this layer Cloudflare advises MCP server authors to keep tool definitions out of the context window, noting that newer clients use Code Mode, where the model writes code that calls tools and loads only the definitions it needs ([developers.cloudflare.com](https://developers.cloudflare.com/agents/model-context-protocol/)). Cloudflare recommends per-operation OAuth scopes and returning an insufficientScope() challenge for step-up authorization instead of requesting every scope up front ([developers.cloudflare.com](https://developers.cloudflare.com/agents/model-context-protocol/)). Cloudflare says strict MCP clients validate tool calls against inputSchema and results against outputSchema, and advises defining both and returning matching structuredContent ([developers.cloudflare.com](https://developers.cloudflare.com/agents/model-context-protocol/)). The Workers OAuth Provider stores grants and tokens in a KV namespace bound as OAUTH\_KV, and needs the global\_fetch\_strictly\_public flag to fetch Client ID Metadata Documents ([developers.cloudflare.com](https://developers.cloudflare.com/agents/model-context-protocol/authorization/)). Cloudflare's authorization guide keeps Dynamic Client Registration as an option for older MCP clients and supports upstream sign-in with GitHub, Google or another provider through beginUpstream() and finishUpstream() ([developers.cloudflare.com](https://developers.cloudflare.com/agents/model-context-protocol/authorization/)). The Workers Paid plan has a minimum charge of 5 USD a month per account; the Workers Free plan allows 100,000 requests a day with 10 ms of CPU time per invocation ([developers.cloudflare.com](https://developers.cloudflare.com/workers/platform/pricing/)). Cloudflare's Agents docs list pages for building an MCP client, an MCPClientManager, charging for MCP tools and MCP governance ([developers.cloudflare.com](https://developers.cloudflare.com/agents/model-context-protocol/)). Cloudflare describes its connectivity cloud as delivering "60+ networking, security, and performance services" ([www.cloudflare.com](https://www.cloudflare.com/about-overview/), vendor's own claim). Cloudflare describes MCP authorization as "a subset of OAuth 2.1" and builds it with @cloudflare/workers-oauth-provider, using the OAuthAuthorizationServer and OAuthResourceServer classes ([developers.cloudflare.com](https://developers.cloudflare.com/agents/model-context-protocol/authorization/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Workers and Agents SDK | Host remote MCP servers with createMcpHandler. | Workers Paid minimum; from 5 USD; Workers Free: 100,000 requests a day (source, as of 5 November 2026) | | Workers OAuth Provider | Authorization server and resource server library for MCP on Workers. | price not read | | MCP server portals | One endpoint in front of many remote MCP servers. | price not read | | AI Gateway | Gateway for model traffic with analytics, caching and rate limits. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | streamable HTTP | Supports | Remote MCP connections use Streamable HTTP. | developers.cloudflare.com | | MCP | client ID metadata documents | Supports | The OAuth provider fetches CIMDs with global_fetch_strictly_public. | developers.cloudflare.com | | MCP | dynamic client registration | Supports | DCR kept as an option for older clients. | developers.cloudflare.com | | MCP | step-up authorization | Supports | insufficientScope() challenge for per-operation scopes. | developers.cloudflare.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | cloudflare.com | 82 of 100, grade B | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan | cloudflare.com | 53 of 100, L4 Agent-Integrated; 8 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Cloudflare does not list third-party MCP servers in a public registry of its own. - Cloudflare portals do not front stdio-only servers until they are put behind HTTP. ## Relation to Ora Cloudflare, Inc. runs the Is Your Site Agent-Ready? scanner at isitagentready.com, which checks standards from robots.txt and Markdown negotiation to MCP, OAuth, Agent Skills and agentic commerce, while Ora's home page offers its own scan for a domain or an MCP server URL; this directory records both scores for each vendor domain ([isitagentready.com](https://isitagentready.com/) and [ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026). ## Related on this site Hosts page - [Cloudflare](https://agentmcpdirectory.com/hosts/cloudflare/) - [Cloudflare AI Gateway](https://agentmcpdirectory.com/hosts/cloudflare-ai-gateway/) Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/cloudflare/index.md) ## Sources - [Model Context Protocol (MCP) · Cloudflare Agents docs](https://developers.cloudflare.com/agents/model-context-protocol/), read 5 November 2026 - [Authorization · Cloudflare Agents docs](https://developers.cloudflare.com/agents/model-context-protocol/authorization/), read 5 November 2026 - [Pricing · Cloudflare Workers docs](https://developers.cloudflare.com/workers/platform/pricing/), read 5 November 2026 - [About us | Cloudflare](https://www.cloudflare.com/about-overview/), read 5 November 2026 - [Is Your Site Agent-Ready?](https://isitagentready.com/), read 5 November 2026 - [Ora | Make your site work for agents](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Composio: MCP vendor profile | Agent MCP Directory" description: "Composio: connector platform. 2 products, 5 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/composio site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Composio: MCP vendor profile | Agent MCP Directory > Composio: connector platform. 2 products, 5 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/composio Site: Agent MCP Directory Last reviewed: 2026-11-05 # Composio: MCP vendor profile Composio gives agents per-user, authenticated access to 1000+ apps through a shared MCP server with seven meta-tools, per-session MCP endpoints, single-toolkit servers and agent plugins, as documented by the vendor. Composio recommends its native agent plugin, which uses the Composio CLI, for Codex or Claude Code users who did not specifically choose MCP (docs.composio.dev). ## At a glance | Type | Connector platforms | | --- | --- | | Home | composio.dev | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer Composio Connect is an MCP server at https://connect.composio.dev/mcp that gives an agent access to 1000+ apps, including Gmail, Notion, Slack, GitHub and Linear, through one connection ([docs.composio.dev](https://docs.composio.dev/docs/composio-connect.md)). Composio can build an MCP server scoped to one toolkit with composio.mcp.create, but its docs say a regular session gives "a much better MCP experience" for most uses ([docs.composio.dev](https://docs.composio.dev/docs/single-toolkit-mcp.md)). Composio's docs list a guide for giving an application-created session to an MCP-compatible framework ([docs.composio.dev](https://docs.composio.dev/llms.txt)). A single-toolkit Composio MCP server needs an auth configuration for the toolkit to be created first ([docs.composio.dev](https://docs.composio.dev/docs/single-toolkit-mcp.md)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Composio Connect | Shared MCP server with meta-tools over 1000+ apps. | price not read | | Sessions and single-toolkit MCP | Per-session or per-toolkit MCP endpoints for applications. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | CLIs | Composio CLI plugin | Supports | Native agent plugin for Codex and Claude Code built on the Composio CLI. | docs.composio.dev | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | composio.dev | 83 of 100, grade B | 26 October 2026 | how it was taken | | Cloudflare agent-readiness scan | composio.dev | 53 of 100, L4 Agent-Integrated; 8 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Composio does not expose every app tool directly through Connect; agents go through the meta-tools ([docs.composio.dev](https://docs.composio.dev/docs/composio-connect.md)). ## Related on this site Hosts page - [Composio](https://agentmcpdirectory.com/hosts/composio/) Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Standards - [CLIs](https://agentmcpdirectory.com/standards/cli-as-agent-surface/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/composio/index.md) ## Sources - [Composio home](https://composio.dev/), read 5 November 2026 - [Composio Connect - Composio docs](https://docs.composio.dev/docs/composio-connect.md), read 5 November 2026 - [Single Toolkit MCP - Composio docs](https://docs.composio.dev/docs/single-toolkit-mcp.md), read 5 November 2026 - [Composio docs llms.txt](https://docs.composio.dev/llms.txt), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Descope: MCP vendor profile | Agent MCP Directory" description: "Descope: auth provider. Products: MCP Authorization. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/descope site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Descope: MCP vendor profile | Agent MCP Directory > Descope: auth provider. Products: MCP Authorization. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/descope Site: Agent MCP Directory Last reviewed: 2026-11-05 # Descope: MCP vendor profile Descope acts as the authorization server for MCP servers: it publishes discovery metadata, registers clients by CIMD or DCR, runs login and consent, issues tokens and stores downstream credentials in a Connections vault, as documented by the vendor. Descope asks the MCP server to host a /.well-known/oauth-protected-resource document that names Descope as its authorization server (docs.descope.com). ## At a glance | Listed as | Descope (MCP Authorization) | | --- | --- | | Type | Auth providers | | Home | docs.descope.com | | Price | monthly base plus usage | | Read | 5 November 2026 | ## What it does for this layer Descope ships server-side MCP SDKs: @descope/mcp-express middleware with an authenticated /mcp endpoint and per-tool scopes, and the descope-mcp Python SDK with FastMCP integration ([docs.descope.com](https://docs.descope.com/mcp)). Descope Connections stores OAuth tokens, refresh tokens, static API keys and other credentials that MCP tools exchange for at call time, so the MCP client never holds the downstream credential ([docs.descope.com](https://docs.descope.com/mcp)). Descope lists an early-access Descope MCP gateway that routes to tenant-specific or shared MCP servers, and can also be the identity provider for a gateway the customer runs ([docs.descope.com](https://docs.descope.com/mcp)). Descope supports Cross App Access (XAA) for sellers of MCP servers that accept customers' ID-JAG tokens ([docs.descope.com](https://docs.descope.com/mcp)). Descope Access Control Policies define which MCP clients or AI agents may request or use specific MCP server scopes ([docs.descope.com](https://docs.descope.com/mcp)). Descope pricing lists Free Forever with 7,500 monthly active users and 10 tenants, Pro from 249 USD a month and Growth from 799 USD a month ([www.descope.com](https://www.descope.com/pricing)). Descope counts MCP authentication use as monthly active consents, one per unique user who consents to an app, priced separately from MAUs ([www.descope.com](https://www.descope.com/pricing)). Descope's MCP page says Descope "publishes the OAuth discovery metadata, registers MCP clients (CIMD/DCR), runs login and consent, and issues tokens", while the MCP server validates signature, aud and scope ([docs.descope.com](https://docs.descope.com/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Authorization | Managed authorization server, client registration, consent, token issuance and credential vault for MCP servers. | monthly base plus usage; from 0 USD; Free Forever 7,500 MAUs; Pro 249 USD a month (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | client ID metadata documents | Supports | Descope registers MCP clients by CIMD or DCR. | docs.descope.com | | MCP | dynamic client registration | Supports | Descope registers MCP clients by CIMD or DCR. | docs.descope.com | | MCP | protected resource metadata | Supports | The server hosts /.well-known/oauth-protected-resource naming Descope. | docs.descope.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | descope.com | 74 of 100, grade B | 20 October 2026 | how it was taken | | Cloudflare agent-readiness scan | descope.com | 53 of 100, L4 Agent-Integrated; 8 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Descope does not run the MCP server code; token checks happen in the developer's server, through the Descope SDKs or custom code. ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/descope/index.md) ## Sources - [MCP Authorization - Descope Documentation](https://docs.descope.com/mcp), read 5 November 2026 - [Descope pricing](https://www.descope.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Docker: MCP vendor profile | Agent MCP Directory" description: "Docker: gateway or proxy. Products: MCP Catalog, MCP Toolkit, MCP Gateway. 9 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/docker site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Docker: MCP vendor profile | Agent MCP Directory > Docker: gateway or proxy. Products: MCP Catalog, MCP Toolkit, MCP Gateway. 9 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/docker Site: Agent MCP Directory Last reviewed: 2026-11-05 # Docker: MCP vendor profile Docker packages MCP servers as container images in its MCP Catalog and runs them through the open-source MCP Gateway, which starts each server in an isolated container and injects credentials per call, as documented by the vendor. Organisations can build custom Docker MCP catalogs limited to approved servers for their teams (docs.docker.com). ## At a glance | Listed as | Docker (MCP Catalog, Toolkit and Gateway) | | --- | --- | | Type | Gateways and proxies | | Also covers | registry or directory, host or runtime | | Home | docs.docker.com | | Price | open source, MIT | | Read | 5 November 2026 | ## What it does for this layer Docker says its MCP Catalog provides "300+ verified servers packaged as container images with versioning, provenance, and security updates" ([docs.docker.com](https://docs.docker.com/ai/mcp-catalog-and-toolkit/), vendor's own claim). Docker's MCP Toolkit organises servers into catalogs, profiles and clients, so one setup serves several AI applications ([docs.docker.com](https://docs.docker.com/ai/mcp-catalog-and-toolkit/)). Docker describes the MCP Gateway as its "open source solution for orchestrating Model Context Protocol (MCP) servers", a proxy that manages configuration, credentials and access control ([docs.docker.com](https://docs.docker.com/ai/mcp-catalog-and-toolkit/mcp-gateway/)). The MCP Gateway runs in the background when Docker Desktop has MCP Toolkit enabled, and the --profile flag selects which servers it exposes ([docs.docker.com](https://docs.docker.com/ai/mcp-catalog-and-toolkit/mcp-gateway/)). MCP Gateway as part of Docker AI Governance is an invite-only feature handled by Docker Sales, per the docs note read on 5 Nov 2026 ([docs.docker.com](https://docs.docker.com/ai/mcp-catalog-and-toolkit/mcp-gateway/)). Docker publishes the gateway source at docker/mcp-gateway under the MIT license, with about 1.6k GitHub stars counted on 5 Nov 2026 ([github.com](https://github.com/docker/mcp-gateway), observed 5 November 2026). The docker mcp CLI plugin keeps secrets out of environment variables through Docker Desktop secrets management and includes built-in OAuth flows for servers that need an access token ([github.com](https://github.com/docker/mcp-gateway)). The Docker MCP Gateway runs each MCP server in an isolated container with restricted privileges, network access and resource usage, starting it on demand when a tool is called ([docs.docker.com](https://docs.docker.com/ai/mcp-catalog-and-toolkit/mcp-gateway/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Catalog | Curated MCP servers as container images, plus custom catalogs. | price not read | | MCP Toolkit | Docker Desktop feature that manages profiles and client connections. | price not read | | MCP Gateway | Open-source proxy that runs MCP servers in containers and routes tool calls. | open source, MIT; from 0 USD; Governance edition is invite-only (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | docker.com | 69 of 100, grade C | 11 October 2026 | how it was taken | | Cloudflare agent-readiness scan | docker.com | 27 of 100, L1 Basic Web Presence; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Docker's MCP Gateway is aimed at containers on a developer machine or Docker host; the docs read do not describe a hosted multi-tenant endpoint. - The Docker docs read here do not state which MCP protocol revision the Gateway implements. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/docker/index.md) ## Sources - [Docker MCP Catalog and Toolkit - Docker docs](https://docs.docker.com/ai/mcp-catalog-and-toolkit/), read 5 November 2026 - [MCP Gateway - Docker docs](https://docs.docker.com/ai/mcp-catalog-and-toolkit/mcp-gateway/), read 5 November 2026 - [GitHub - docker/mcp-gateway](https://github.com/docker/mcp-gateway), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Enkrypt AI: MCP vendor profile | Agent MCP Directory" description: "Enkrypt AI: security scanner. Products: MCP Scanner, MCP Gateway. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/enkrypt-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Enkrypt AI: MCP vendor profile | Agent MCP Directory > Enkrypt AI: security scanner. Products: MCP Scanner, MCP Gateway. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/enkrypt-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Enkrypt AI: MCP vendor profile Enkrypt AI sells an MCP Scanner that inventories MCP servers and tools and flags injection and over-privilege risks, and publishes an open-source inline MCP Gateway that approves, modifies or blocks tool calls, as documented by the vendor. The Enkrypt AI gateway evaluates tool calls before execution and validates tool responses before they return to the agent loop (www.enkryptai.com). ## At a glance | Listed as | Enkrypt AI (MCP Scanner, MCP Gateway) | | --- | --- | | Type | Security scanners | | Also covers | gateway or proxy | | Home | www.enkryptai.com | | Price | no published price | | Read | 5 November 2026 | ## What it does for this layer Enkrypt AI's MCP Scanner "discovers tools, analyzes capabilities and permissions, and surfaces high-risk exposure" ([www.enkryptai.com](https://www.enkryptai.com/product/mcp-scanner)). Enkrypt AI's scanner checks for direct and indirect prompt injection, including tool-steering ([www.enkryptai.com](https://www.enkryptai.com/product/mcp-scanner)). Enkrypt AI's scanner flags over-privilege, sensitive access, unsafe actions and governance gaps, and outputs an MCP inventory, a risk findings report and a remediation plan ([www.enkryptai.com](https://www.enkryptai.com/product/mcp-scanner)). The Enkrypt AI gateway records a policy decision log, an action trace and approval receipts for audit ([www.enkryptai.com](https://www.enkryptai.com/product/mcp-gateway)). Enkrypt AI's site banner on 5 Nov 2026 announced that Enkrypt AI "Joins Anaconda" ([www.enkryptai.com](https://www.enkryptai.com/product/mcp-scanner)). Enkrypt AI describes its MCP Gateway as "open source" and inline between agents and MCP servers to approve, modify or block tool calls ([www.enkryptai.com](https://www.enkryptai.com/product/mcp-gateway)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Scanner | Inventory and risk assessment of MCP servers and tools. | no published price | | MCP Gateway | Open-source inline proxy that enforces policy on MCP tool calls. | no published price | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | enkryptai.com | no cached score GET /api/score returned HTTP 404 (no cached score) | not scanned | how it was taken | | Cloudflare agent-readiness scan | enkryptai.com | 13 of 100, L1 Basic Web Presence; 2 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Enkrypt AI does not publish scanner prices on the pages read. - Enkrypt AI scans and proxies MCP servers but offers no hosting for them on the pages read. ## Related on this site Type - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/enkrypt-ai/index.md) ## Sources - [Enkrypt AI MCP Scanner: Advanced AI Threat Detection & Security](https://www.enkryptai.com/product/mcp-scanner), read 5 November 2026 - [Enkrypt AI MCP Gateway | Inline Policy Control for MCP Tool Traffic](https://www.enkryptai.com/product/mcp-gateway), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "GitHub: MCP vendor profile | Agent MCP Directory" description: "GitHub: registry or directory. Products: GitHub MCP Registry, plus 2 more. 7 dated facts, price status and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/github site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # GitHub: MCP vendor profile | Agent MCP Directory > GitHub: registry or directory. Products: GitHub MCP Registry, plus 2 more. 7 dated facts, price status and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/github Site: Agent MCP Directory Last reviewed: 2026-11-05 # GitHub: MCP vendor profile GitHub runs a curated MCP Registry for partner and community servers, hosts its own remote GitHub MCP server, and lets Copilot surfaces use MCP servers under an organisation policy that is off by default, as documented by the vendor. GitHub advises using the tools field in repository settings to allowlist specific tools, preferably read-only ones (docs.github.com). ## At a glance | Listed as | GitHub (MCP Registry, GitHub MCP server, Copilot MCP) | | --- | --- | | Type | Registries and directories | | Also covers | host or runtime | | Home | github.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer Copilot CLI supports local and remote MCP servers and has the GitHub MCP server built in without extra configuration ([docs.github.com](https://docs.github.com/en/copilot/concepts/context/mcp)). For Copilot cloud agent, the default Playwright MCP server can only reach web resources in the agent's own environment through localhost or 127.0.0.1 ([docs.github.com](https://docs.github.com/en/copilot/concepts/context/mcp)). The Copilot docs navigation lists a page titled "Change MCP registry" next to "Configure toolsets" and enterprise configuration ([docs.github.com](https://docs.github.com/en/copilot/concepts/context/mcp)). GitHub's Copilot docs describe the GitHub MCP Registry as "a curated list of MCP servers from partners and the community" ([docs.github.com](https://docs.github.com/en/copilot/concepts/context/mcp)). GitHub's "MCP servers in Copilot" policy lets enterprises and organisations enable or disable MCP for members, and the policy is disabled by default ([docs.github.com](https://docs.github.com/en/copilot/concepts/context/mcp)). In Copilot cloud agent, the default GitHub MCP server uses a specially scoped token with read-only access to the current repository ([docs.github.com](https://docs.github.com/en/copilot/concepts/context/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | GitHub MCP Registry | Curated directory of partner and community MCP servers. | price not read | | GitHub MCP server | Remote and local MCP server for GitHub data. | price not read | | Copilot MCP support | MCP in Copilot CLI, cloud agent, code review and IDEs under an org policy. | price not read | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | github.com | 65 of 100, grade C | 1 November 2026 | how it was taken | | Cloudflare agent-readiness scan | github.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Copilot cloud agent does not connect to OAuth-protected remote MCP servers set in repository settings ([docs.github.com](https://docs.github.com/en/copilot/concepts/context/mcp)). ## Related on this site Hosts page - [GitHub MCP Registry](https://agentmcpdirectory.com/hosts/github-mcp-registry/) Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/github/index.md) ## Sources - [GitHub home](https://github.com/mcp), read 5 November 2026 - [Model Context Protocol (MCP) - GitHub Docs](https://docs.github.com/en/copilot/concepts/context/mcp), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Glama: MCP vendor profile | Agent MCP Directory" description: "Glama: registry or directory. Products: MCP directory, plus 2 more. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/glama site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Glama: MCP vendor profile | Agent MCP Directory > Glama: registry or directory. Products: MCP directory, plus 2 more. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/glama Site: Agent MCP Directory Last reviewed: 2026-11-05 # Glama: MCP vendor profile Glama runs a public MCP server directory that counted 116,152 servers on 5 Nov 2026, and also hosts MCP servers on dedicated machines behind its own MCP gateway, with per-tool access control and full call logs, as documented by the vendor. ## At a glance | Type | Registries and directories | | --- | --- | | Also covers | host or runtime, gateway or proxy | | Home | glama.ai | | Price | no published price | | Read | 5 November 2026 | ## What it does for this layer Glama says it "has operated more than 20,000 MCP server instances" ([glama.ai](https://glama.ai/mcp/hosting), vendor's own claim). Glama-hosted deployments get health checks against /ping with retry-on-failure and optional persistent volumes mounted at /data ([glama.ai](https://glama.ai/mcp/hosting)). The gateway in front of each Glama deployment manages OAuth 2.1 credentials with automatic refresh and logs every JSON-RPC call with full payloads ([glama.ai](https://glama.ai/mcp/hosting)). Glama hosting offers tool-call analytics over 1 hour to 90 day windows and automated health tests that understand the MCP handshake ([glama.ai](https://glama.ai/mcp/hosting)). Glama-hosted servers are private by default and can be switched to a public listing ([glama.ai](https://glama.ai/mcp/hosting)). Glama's MCP Gateway fronts three kinds of endpoints: open-source servers hosted on Glama, pre-indexed hosted connectors such as Linear, Stripe and PostHog, and any remote MCP server with the customer's own credentials ([glama.ai](https://glama.ai/mcp/gateway)). Glama's hosting page cites a 2026 scan of 2,181 remote MCP endpoints that found 52% dead and 9% healthy ([glama.ai](https://glama.ai/mcp/hosting), vendor's own claim). Glama's server directory page counted 116,152 servers and stamped itself "Updated 2026-11-05 14:34" when read on 5 Nov 2026 ([glama.ai](https://glama.ai/mcp/servers), observed 5 November 2026). Glama MCP Hosting deploys private or public MCP servers on dedicated infrastructure with a gateway, call logs, per-tool access control and directory distribution ([glama.ai](https://glama.ai/mcp/hosting)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP directory | Public directory of MCP servers and connectors with grades. | no published price | | MCP Hosting | Dedicated-machine hosting for MCP servers with a built-in gateway. | no published price | | MCP Gateway | Reverse proxy with logging, per-tool access control and credential management. | no published price | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | OAuth 2.1 credentials | Supports | Gateway manages OAuth 2.1 credentials with automatic refresh. | glama.ai | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | glama.ai | 80 of 100, grade B | 19 October 2026 | how it was taken | | Cloudflare agent-readiness scan | glama.ai | 47 of 100, L2 Bot-Aware; 7 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Glama does not publish hosting prices on the pages read. - Glama's directory grades do not come with a published method on the pages read. ## Related on this site Hosts page - [Glama](https://agentmcpdirectory.com/hosts/glama/) Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/glama/index.md) ## Sources - [Glama MCP servers directory](https://glama.ai/mcp/servers), read 5 November 2026 - [MCP Server Hosting - Deploy Private or Public MCP Servers | Glama](https://glama.ai/mcp/hosting), read 5 November 2026 - [The Glama MCP Gateway | Glama](https://glama.ai/mcp/gateway), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Google Cloud Run: MCP vendor profile | Agent MCP Directory" description: "Google Cloud Run: host or runtime. Products: Cloud Run. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/google-cloud-run site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Google Cloud Run: MCP vendor profile | Agent MCP Directory > Google Cloud Run: host or runtime. Products: Cloud Run. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/google-cloud-run Site: Agent MCP Directory Last reviewed: 2026-11-05 # Google Cloud Run: MCP vendor profile Google Cloud Run hosts remote MCP servers built with the official SDKs or FastMCP as streamable-HTTP services, with access controlled by IAM and a local proxy command for developer clients, as documented by the vendor. Cloud Run deploys an MCP server with gcloud run deploy, either from an image with --image and --port or from source with --source (cloud.google.com). ## At a glance | Type | Hosts and runtimes | | --- | --- | | Operator | Google | | Home | cloud.google.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer New Google Cloud customers get 300 USD in free credits, per the Cloud Run MCP guide ([cloud.google.com](https://cloud.google.com/run/docs/host-mcp-servers)). Cloud Run "supports hosting MCP servers with streamable HTTP transport, but not MCP servers with stdio transport." ([cloud.google.com](https://cloud.google.com/run/docs/host-mcp-servers)). Google's guide applies to servers built with an official MCP SDK or FastMCP and to existing community MCP servers ([cloud.google.com](https://cloud.google.com/run/docs/host-mcp-servers)). Local MCP clients can authenticate with the Cloud Run Invoker IAM role (roles/run.invoker) ([cloud.google.com](https://cloud.google.com/run/docs/host-mcp-servers)). gcloud run services proxy MCP\_SERVER\_NAME --region REGION --port=3000 creates a local proxy on port 3000 that exposes the remote MCP server to a local client ([cloud.google.com](https://cloud.google.com/run/docs/host-mcp-servers)). The Cloud Run guide separates authentication for local MCP clients from MCP clients that run on Cloud Run itself ([cloud.google.com](https://cloud.google.com/run/docs/host-mcp-servers)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Cloud Run | Serverless container hosting for remote MCP servers. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | streamable HTTP | Supports | Hosts streamable-HTTP MCP servers; stdio is not supported. | cloud.google.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | cloud.google.com | 51 of 100, grade C | 28 October 2026 | how it was taken | | Cloudflare agent-readiness scan | cloud.google.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Cloud Run does not act as an OAuth authorization server for public MCP clients in the guide read; it relies on IAM. ## Related on this site Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/google-cloud-run/index.md) ## Sources - [Host MCP servers on Cloud Run  |  Google Cloud Documentation](https://cloud.google.com/run/docs/host-mcp-servers), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "IBM ContextForge: MCP vendor profile | Agent MCP Directory" description: "IBM ContextForge: gateway or proxy. Products: ContextForge. 7 dated facts, prices and standards, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/ibm-contextforge site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # IBM ContextForge: MCP vendor profile | Agent MCP Directory > IBM ContextForge: gateway or proxy. Products: ContextForge. 7 dated facts, prices and standards, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/ibm-contextforge Site: Agent MCP Directory Last reviewed: 2026-11-05 # IBM ContextForge: MCP vendor profile ContextForge is IBM's open-source registry and proxy that federates MCP servers, A2A agents and REST or gRPC APIs behind one MCP endpoint with guardrails, plugins and observability, as documented by the vendor. ContextForge runs as an MCP server itself, installs from PyPI or Docker, and scales on Kubernetes with Redis-backed federation and caching (github.com). ## At a glance | Type | Gateways and proxies | | --- | --- | | Also covers | registry or directory | | Operator | IBM | | Home | github.com | | Price | open source, Apache-2.0 | | Read | 5 November 2026 | ## What it does for this layer ContextForge's Tools Gateway covers MCP, REST, gRPC-to-MCP translation and TOON compression ([github.com](https://github.com/IBM/mcp-context-forge)). The IBM/mcp-context-forge repository is licensed Apache-2.0 ([github.com](https://github.com/IBM/mcp-context-forge)). The repository had about 4.8k stars and 3,367 commits on 5 Nov 2026 ([github.com](https://github.com/IBM/mcp-context-forge), observed 5 November 2026). The repository ships Docker Compose files for SSO, TLS, SIEM export to OpenSearch, and tracing with Langfuse or Phoenix ([github.com](https://github.com/IBM/mcp-context-forge), observed 5 November 2026). ContextForge supports plugins for guardrails on agent and tool calls, according to the repository description ([github.com](https://github.com/IBM/mcp-context-forge)). ContextForge describes itself as "an open source registry and proxy that federates MCP, A2A, and REST/gRPC APIs with centralized governance, discovery, and observability" ([github.com](https://github.com/IBM/mcp-context-forge)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | ContextForge | Self-hosted gateway, registry and proxy for MCP, A2A, REST and gRPC. | open source, Apache-2.0; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | MCP server | Supports | Runs as an MCP server in front of federated tools. | github.com | | A2A | A2A federation | Supports | Federates A2A agents with MCP tools. | github.com | ## What it does not do - IBM ContextForge is self-hosted software; the repository does not describe a managed IBM service. - ContextForge does not grade or verify the upstream servers it federates. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [A2A](https://agentmcpdirectory.com/standards/a2a/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/ibm-contextforge/index.md) ## Sources - [GitHub - IBM/mcp-context-forge (ContextForge)](https://github.com/IBM/mcp-context-forge), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Keycard: MCP vendor profile | Agent MCP Directory" description: "Keycard: auth provider. Products: Keycard platform. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/keycard site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Keycard: MCP vendor profile | Agent MCP Directory > Keycard: auth provider. Products: Keycard platform. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/keycard Site: Agent MCP Directory Last reviewed: 2026-11-05 # Keycard: MCP vendor profile Keycard gives each agent its own identity and issues scoped, just-in-time credentials at runtime, and puts MCP servers behind a unified access gateway with per-tool policy and an audit log, as documented by the vendor. Keycard's MCP SDK ships as keycardai-mcp and keycardai-fastmcp on PyPI and @keycardai/mcp on npm, with @keycardai/cloudflare for Cloudflare Workers (docs.keycard.ai). ## At a glance | Type | Auth providers | | --- | --- | | Also covers | gateway or proxy | | Home | www.keycard.ai | | Price | per transaction | | Read | 5 November 2026 | ## What it does for this layer Keycard's guide puts Keycard in front of an MCP server or API "so every request carries a verified user, explicit scopes, and an audit record" ([docs.keycard.ai](https://docs.keycard.ai/guides/mcp-server/)). A Keycard unified access gateway "aggregates the tools from multiple upstream MCP servers behind a single MCP endpoint", and the admin chooses which tools it serves and who may call them ([docs.keycard.ai](https://docs.keycard.ai/admin/unified-access-gateway/)). The Keycard MCP package verifies bearer tokens, serves OAuth metadata endpoints and provides grant decorators for delegated access to external APIs ([docs.keycard.ai](https://docs.keycard.ai/sdk/mcp/)). Keycard docs include guides to run workloads on Render, Fly.io and Vercel without secrets and to authenticate Entra Agent ID agents ([docs.keycard.ai](https://docs.keycard.ai/)). Keycard pricing lists a Free tier with 5,000 transactions a month as a hard cap and a 500 USD a month tier with 100,000 transactions, then 1 USD per 1,000 ([www.keycard.ai](https://www.keycard.ai/pricing/)). Keycard says all plans include OAuth 2.1, Token Exchange, SPIFFE, WIMSE, MCP, A2A, API and CLI protocols ([www.keycard.ai](https://www.keycard.ai/pricing/)). Keycard's about page states "$38M raised" ([www.keycard.ai](https://www.keycard.ai/about/), vendor's own claim). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Keycard platform | Agent identity, runtime authorization, unified MCP access gateway and audit log. | per transaction; from 0 USD; Free 5,000 transactions a month (hard cap); 500 USD a month for 100,000 (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | OAuth metadata endpoints | Supports | The MCP SDK serves OAuth metadata endpoints and verifies bearer tokens. | docs.keycard.ai | | A2A | A2A in all plans | Supports | Pricing lists A2A among supported protocols. | www.keycard.ai | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | keycard.ai | 65 of 100, grade C | 23 August 2026 | how it was taken | | Cloudflare agent-readiness scan | keycard.ai | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Keycard does not host MCP server code; it sits in front of servers the customer runs or installs from its catalog. ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [A2A](https://agentmcpdirectory.com/standards/a2a/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/keycard/index.md) ## Sources - [Keycard home](https://www.keycard.ai/), read 5 November 2026 - [Protect MCP servers and APIs | Keycard](https://docs.keycard.ai/guides/mcp-server/), read 5 November 2026 - [Unified Access Gateway | Keycard](https://docs.keycard.ai/admin/unified-access-gateway/), read 5 November 2026 - [MCP | Keycard](https://docs.keycard.ai/sdk/mcp/), read 5 November 2026 - [Keycard Docs | Keycard](https://docs.keycard.ai/), read 5 November 2026 - [Pricing - Keycard](https://www.keycard.ai/pricing/), read 5 November 2026 - [About - Keycard](https://www.keycard.ai/about/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Kong: MCP vendor profile | Agent MCP Directory" description: "Kong: gateway or proxy. Products: AI MCP Proxy plugin, plus 1 more. 5 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/kong site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Kong: MCP vendor profile | Agent MCP Directory > Kong: gateway or proxy. Products: AI MCP Proxy plugin, plus 1 more. 5 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/kong Site: Agent MCP Directory Last reviewed: 2026-11-05 # Kong: MCP vendor profile Kong turns APIs behind Kong Gateway or published in its Dev Portal into MCP servers, proxies MCP traffic with the AI MCP Proxy plugin, and lists an AI Registry product, on-premises or in Konnect, as documented by the vendor. Kong's product menu lists an "AI Registry" marked NEW alongside AI Gateway and Context Mesh (konghq.com). ## At a glance | Listed as | Kong (AI Gateway, MCP Traffic Gateway) | | --- | --- | | Type | Gateways and proxies | | Also covers | registry or directory | | Home | developer.konghq.com | | Price | AI Gateway Enterprise | | Read | 5 November 2026 | ## What it does for this layer Kong offers two ways to expose APIs as MCP servers: AI Gateway, which converts any Gateway API into an MCP server, and Dev Portal, which generates one from APIs already published there ([developer.konghq.com](https://developer.konghq.com/mcp/)). The AI MCP Proxy plugin acts as a protocol bridge between MCP and HTTP, with a mode parameter that proxies MCP requests, converts RESTful APIs into MCP tools, or exposes grouped tools as an MCP server ([developer.konghq.com](https://developer.konghq.com/plugins/ai-mcp-proxy/)). In conversion modes the Kong plugin maps each MCP tool call to an OpenAPI operation and must be scoped to a Route; consumer and consumer-group scoping is not supported in any mode ([developer.konghq.com](https://developer.konghq.com/plugins/ai-mcp-proxy/)). Kong's MCP Traffic Gateway works on-premises and in Konnect ([developer.konghq.com](https://developer.konghq.com/mcp/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | AI MCP Proxy plugin | MCP-to-HTTP bridge and REST-to-MCP conversion in Kong AI Gateway. | AI Gateway Enterprise; Enterprise tier only (source, as of 5 November 2026) | | Dev Portal MCP servers | MCP servers generated from APIs published in a Kong Dev Portal. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | OpenAPI | OpenAPI to tools | Supports | Conversion maps MCP tool calls to OpenAPI operations. | developer.konghq.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | konghq.com | 71 of 100, grade B | 1 November 2026 | how it was taken | | Cloudflare agent-readiness scan | konghq.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Kong's MCP plugin is not in the free or open-source edition ([developer.konghq.com](https://developer.konghq.com/plugins/ai-mcp-proxy/)). ## Related on this site Hosts page - [Kong AI Gateway](https://agentmcpdirectory.com/hosts/kong-ai-gateway/) Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [OpenAPI](https://agentmcpdirectory.com/standards/openapi-as-agent-surface/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/kong/index.md) ## Sources - [developer.konghq.com/mcp/](https://developer.konghq.com/mcp/), read 5 November 2026 - [developer.konghq.com/plugins/ai-mcp-proxy/](https://developer.konghq.com/plugins/ai-mcp-proxy/), read 5 November 2026 - [Kong Pricing for API and AI Connectivity Platform | Konnect | Kong Inc.](https://konghq.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "LangChain: MCP vendor profile | Agent MCP Directory" description: "LangChain: SDK or framework. Products: MCPAdapter (langchain.mcp). 6 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/langchain site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # LangChain: MCP vendor profile | Agent MCP Directory > LangChain: SDK or framework. Products: MCPAdapter (langchain.mcp). 6 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/langchain Site: Agent MCP Directory Last reviewed: 2026-11-05 # LangChain: MCP vendor profile LangChain connects its agents to MCP servers through MCPAdapter, built on FastMCP, which discovers a server's tools and adapts them into LangChain tools; the older langchain-mcp-adapters package remains on GitHub, as documented by the vendor. The langchain.mcp namespace requires langchain\[mcp\] 1.4.0 or later and is in beta; importing it raises a LangChainBetaWarning once per process (docs.langchain.com). ## At a glance | Listed as | LangChain (MCPAdapter, langchain-mcp-adapters) | | --- | --- | | Type | SDKs and frameworks | | Home | docs.langchain.com | | Price | open source | | Read | 5 November 2026 | ## What it does for this layer LangChain's MCPAdapter is built on FastMCP, which handles transport inference, protocol negotiation, connection management and authentication ([docs.langchain.com](https://docs.langchain.com/oss/python/langchain/mcp)). MCPAdapter infers the transport from its target: an in-process FastMCP server, a local script over stdio, or a remote URL ([docs.langchain.com](https://docs.langchain.com/oss/python/langchain/mcp)). LangChain warns that a string target must be an http or https URL, because a string naming an existing .py or .js file would be launched as a subprocess ([docs.langchain.com](https://docs.langchain.com/oss/python/langchain/mcp)). The earlier langchain-mcp-adapters package converts MCP tools into LangChain tools for LangGraph agents; the repository is MIT licensed with about 3.6k stars on 5 Nov 2026 ([github.com](https://github.com/langchain-ai/langchain-mcp-adapters)). LangChain runs a public docs MCP server at https://docs.langchain.com/mcp ([docs.langchain.com](https://docs.langchain.com/oss/python/langchain/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCPAdapter (langchain.mcp) | Client adapter that turns MCP server tools into LangChain tools. | open source; from 0 USD (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | langchain.com | 74 of 100, grade B | 17 October 2026 | how it was taken | | Cloudflare agent-readiness scan | langchain.com | 7 of 100, L0 Not Ready; 1 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - LangChain's MCPAdapter is a client-side adapter; it does not host MCP servers. ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/langchain/index.md) ## Sources - [Model Context Protocol (MCP) - Docs by LangChain](https://docs.langchain.com/oss/python/langchain/mcp), read 5 November 2026 - [GitHub - langchain-ai/langchain-mcp-adapters](https://github.com/langchain-ai/langchain-mcp-adapters), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Lasso Security: MCP vendor profile | Agent MCP Directory" description: "Lasso Security: security scanner. Products: MCP Gateway (open source). 9 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/lasso-security site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Lasso Security: MCP vendor profile | Agent MCP Directory > Lasso Security: security scanner. Products: MCP Gateway (open source). 9 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/lasso-security Site: Agent MCP Directory Last reviewed: 2026-11-05 # Lasso Security: MCP vendor profile Lasso Security publishes an open-source, plugin-based MCP gateway that masks secrets and personal data in traffic and scans MCP servers by reputation and tool descriptions before loading them, as documented by the vendor. Lasso's gateway intercepts requests and responses to sanitise sensitive information (github.com). ## At a glance | Listed as | Lasso Security (MCP Gateway) | | --- | --- | | Type | Security scanners | | Also covers | gateway or proxy | | Operator | Lasso Security | | Home | www.lasso.security | | Price | open source, MIT; no published price for its other products | | Read | 5 November 2026 | ## What it does for this layer The basic plugin masks secrets such as GitHub tokens, AWS access tokens, GCP API keys, JWTs and Slack app tokens ([github.com](https://github.com/lasso-security/mcp-gateway)). The presidio plugin uses Presidio to identify and anonymise credit cards, IP addresses, emails and phone numbers ([github.com](https://github.com/lasso-security/mcp-gateway)). The Lasso scanner blocks MCP servers whose reputation score falls below a threshold of 30 and writes the results back into the MCP configuration file ([github.com](https://github.com/lasso-security/mcp-gateway)). The gateway reads an existing client configuration, for example mcp-gateway --mcp-json-path ~/.cursor/mcp.json ([github.com](https://github.com/lasso-security/mcp-gateway)). Lasso's gateway is MIT-licensed open source, and GitHub listed 397 stars for it on 5 Nov 2026 ([github.com](https://github.com/lasso-security/mcp-gateway), observed 5 November 2026). Lasso's home page lists MCP and AI gateway security among its products for AI agents ([www.lasso.security](https://www.lasso.security/)). Lasso's repository describes mcp-gateway as "A plugin-based gateway that orchestrates other MCPs" ([github.com](https://github.com/lasso-security/mcp-gateway)). mcp-gateway --scan rates server reputation from marketplace (Smithery, NPM) and GitHub data and scans tool descriptions for hidden instructions and sensitive file patterns ([github.com](https://github.com/lasso-security/mcp-gateway)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Gateway (open source) | Plugin-based local MCP gateway with secret masking, PII anonymisation and a pre-load scanner. | open source, MIT; from 0 USD (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | lasso.security | 51 of 100, grade C | 31 August 2026 | how it was taken | | Cloudflare agent-readiness scan | lasso.security | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Lasso's open-source gateway does not host MCP servers; it orchestrates servers listed in a client config. - The Lasso pages read do not publish prices for its commercial products. ## Related on this site Type - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/lasso-security/index.md) ## Sources - [Secure AI Adoption at Enterprise Scale | Lasso](https://www.lasso.security/), read 5 November 2026 - [GitHub - lasso-security/mcp-gateway](https://github.com/lasso-security/mcp-gateway), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "LiteLLM: MCP vendor profile | Agent MCP Directory" description: "LiteLLM: gateway or proxy. 2 products, 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/litellm site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # LiteLLM: MCP vendor profile | Agent MCP Directory > LiteLLM: gateway or proxy. 2 products, 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/litellm Site: Agent MCP Directory Last reviewed: 2026-11-05 # LiteLLM: MCP vendor profile LiteLLM is an open-source, self-hosted AI gateway whose proxy includes an MCP Gateway: one fixed endpoint for MCP tools, access controlled by API key and team, usable with any model LiteLLM routes, as documented by the vendor. The LiteLLM MCP gateway supports Streamable HTTP, SSE and stdio transports to upstream servers (docs.litellm.ai). ## At a glance | Listed as | LiteLLM (BerriAI) | | --- | --- | | Type | Gateways and proxies | | Operator | BerriAI | | Home | www.litellm.ai | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer LiteLLM exposes /mcp-rest/tools/list and /mcp-rest/tools/call so tools can be called with curl without an LLM ([docs.litellm.ai](https://docs.litellm.ai/docs/mcp)). LiteLLM prefixes each tool name with its MCP server name and now requires new server names to comply with SEP-986 ([docs.litellm.ai](https://docs.litellm.ai/docs/mcp)). The LiteLLM docs say the gateway "negotiates the protocol version during initialize" ([docs.litellm.ai](https://docs.litellm.ai/docs/mcp)). LiteLLM's home page says it offers one OpenAI-compatible API to "140+ providers and 1,800+ models" and is "Open source. Self-hosted." ([www.litellm.ai](https://www.litellm.ai/), vendor's own claim). The BerriAI/litellm repository had about 62.8k stars on 5 Nov 2026 and describes a Rust core with a Python SDK ([github.com](https://github.com/BerriAI/litellm), observed 5 November 2026). LiteLLM Proxy provides "an MCP Gateway that allows you to use a fixed endpoint for all MCP tools and control MCP access by Key, Team" ([docs.litellm.ai](https://docs.litellm.ai/docs/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | LiteLLM Proxy (MCP Gateway) | Self-hosted AI gateway with MCP tool routing and per-key, per-team permissions. | price not read | | LiteLLM Enterprise | Commercial edition offered from the home page; no price on the page read. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | streamable HTTP | Supports | Streamable HTTP listed among supported MCP transports. | docs.litellm.ai | | MCP | spec revision | Partial | Version negotiation during initialize implies pre-2026-07-28 revisions; the page links a list of tested versions. | docs.litellm.ai | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | litellm.ai | 73 of 100, grade B | 1 November 2026 | how it was taken | | Cloudflare agent-readiness scan | litellm.ai | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - LiteLLM does not host MCP server code as a managed service on the pages read; the proxy is self-hosted. - The MCP overview does not describe acting as an OAuth authorization server for MCP clients. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/litellm/index.md) ## Sources - [LiteLLM - Open-Source AI Gateway & LLM Proxy](https://www.litellm.ai/), read 5 November 2026 - [MCP Overview | liteLLM](https://docs.litellm.ai/docs/mcp), read 5 November 2026 - [GitHub - BerriAI/litellm](https://github.com/BerriAI/litellm), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Logto: MCP vendor profile | Agent MCP Directory" description: "Logto: auth provider. Products: Logto Cloud, Logto (self-hosted). 5 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/logto site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Logto: MCP vendor profile | Agent MCP Directory > Logto: auth provider. Products: Logto Cloud, Logto (self-hosted). 5 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/logto Site: Agent MCP Directory Last reviewed: 2026-11-05 # Logto: MCP vendor profile Logto is an open-source identity platform whose MCP guide makes Logto the authorization server for an MCP server through the mcp-auth library and MCP SDK v2, with the server registered as an API resource, as documented by the vendor. Logto's guide adds a whoami tool that returns the current user's identity claims from the access token (docs.logto.io). ## At a glance | Type | Auth providers | | --- | --- | | Home | logto.io | | Price | monthly plus token usage | | Read | 5 November 2026 | ## What it does for this layer Logto documents a separate use case for enabling third-party AI agent access to an MCP server ([docs.logto.io](https://docs.logto.io/use-cases/ai/mcp-server-add-auth)). Logto Cloud pricing starts from 24 USD a month, with 50K free tokens then usage billing, and a self-hosted option ([logto.io](https://logto.io/pricing)). Logto's guide integrates Logto with an MCP server "using mcp-auth and the MCP official SDK v2" ([docs.logto.io](https://docs.logto.io/use-cases/ai/mcp-server-add-auth)). In Logto, the MCP server is registered as an API resource, and its resource identifier must match the indicator configured in the server ([docs.logto.io](https://docs.logto.io/use-cases/ai/mcp-server-add-auth)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Logto Cloud | Hosted identity with MCP server authorization. | monthly plus token usage; from 24 USD; From 24 USD a month (source, as of 5 November 2026) | | Logto (self-hosted) | Open-source identity platform run on the customer's infrastructure. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | resource indicator | Supports | MCP server registered as an API resource whose identifier must match. | docs.logto.io | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | logto.io | no cached score GET /api/score returned HTTP 404 (no cached score) | not scanned | how it was taken | | Cloudflare agent-readiness scan | logto.io | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Logto's main MCP guide registers the client in advance rather than showing dynamic client registration ([docs.logto.io](https://docs.logto.io/use-cases/ai/mcp-server-add-auth)). - Logto does not host the MCP server. ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/logto/index.md) ## Sources - [Logto home](https://logto.io/), read 5 November 2026 - [Enable auth for your MCP-powered apps with Logto | Logto docs](https://docs.logto.io/use-cases/ai/mcp-server-add-auth), read 5 November 2026 - [Pricing · Logto](https://logto.io/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Make: MCP vendor profile | Agent MCP Directory" description: "Make: connector platform. Products: Make MCP Server. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/make site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Make: MCP vendor profile | Agent MCP Directory > Make: connector platform. Products: Make MCP Server. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/make Site: Agent MCP Directory Last reviewed: 2026-11-05 # Make: MCP vendor profile Make runs a hosted, stateless Streamable HTTP MCP server that lets Claude, ChatGPT and other clients run Make scenarios and manage scenarios, connections, webhooks and teams, scoped at connect time, as documented by the vendor. Make MCP connects by OAuth or an API key, sent in an Authorization header or embedded in the URL (developers.make.com). ## At a glance | Listed as | Make (Make MCP Server) | | --- | --- | | Type | Connector platforms | | Home | developers.make.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer Make MCP tools run active and on-demand scenarios and view or modify scenarios, connections, webhooks, data stores, teams and organisations ([developers.make.com](https://developers.make.com/mcp-server)). Make scopes decide which tools a client gets; scenario run tools are on all plans and management tools need a paid plan ([developers.make.com](https://developers.make.com/mcp-server)). Make Skills are Markdown files with instructions for building scenarios that also carry Make MCP connection details for clients ([developers.make.com](https://developers.make.com/mcp-server)). Make documents testing its server with npx @modelcontextprotocol/inspector --cli and the http transport ([developers.make.com](https://developers.make.com/mcp-server)). Make describes its MCP server as "a Make-hosted, cloud-based server that runs via stateless Streamable HTTP" ([developers.make.com](https://developers.make.com/mcp-server)). Make's MCP URL depends on the organisation's zone, for example eu2.make.com, with the server at https:///mcp/v2 ([developers.make.com](https://developers.make.com/mcp-server)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Make MCP Server | Hosted MCP server for running and managing Make scenarios. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | stateless streamable HTTP | Supports | Server runs via stateless Streamable HTTP. | developers.make.com | | Agent Skills | Make Skills | Supports | Markdown skills with connection details for clients. | developers.make.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | make.com | 78 of 100, grade B | 2 November 2026 | how it was taken | | Cloudflare agent-readiness scan | make.com | 27 of 100, L1 Basic Web Presence; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Make does not host third-party MCP servers; its server exposes Make itself. ## Related on this site Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/make/index.md) ## Sources - [Make MCP Server - Make Developer Hub](https://developers.make.com/mcp-server), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Manufact: MCP vendor profile | Agent MCP Directory" description: "Manufact: host or runtime. Products: mcp-use, Manufact Cloud. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/manufact site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Manufact: MCP vendor profile | Agent MCP Directory > Manufact: host or runtime. Products: mcp-use, Manufact Cloud. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/manufact Site: Agent MCP Directory Last reviewed: 2026-11-05 # Manufact: MCP vendor profile Manufact pairs mcp-use, an open-source TypeScript and Python SDK for MCP servers and apps, with Manufact Cloud, which deploys MCP servers from GitHub and tests them across ChatGPT, Claude and coding agents, as documented by the vendor. npx create-mcp-use-app scaffolds an mcp-use project, and a git push deploys it through Manufact's GitHub App with branch previews (manufact.com). ## At a glance | Listed as | Manufact (mcp-use) | | --- | --- | | Type | Hosts and runtimes | | Also covers | SDK or framework | | Home | manufact.com | | Price | open source; credits plus usage | | Read | 5 November 2026 | ## What it does for this layer Manufact Cloud runs publishing checks and prepares listing materials for the ChatGPT and Claude plugin stores from the same deployed server ([manufact.com](https://manufact.com/)). Manufact offers an MCP Quality Score, a server tunnel for local MCP servers and an mcp-use Inspector for debugging in the browser ([manufact.com](https://manufact.com/)). Manufact pricing lists Free with 5 USD of included credits a month and one project, Pay as you go with 10 USD of credits and 10 projects, and Pro at 250 USD a month plus usage with 300 USD of credits ([manufact.com](https://manufact.com/pricing)). Manufact says it is two things: mcp-use, an open-source SDK for MCP Apps and servers in TypeScript and Python, and Manufact Cloud, a hosting platform where every push auto-deploys ([manufact.com](https://manufact.com/)). Manufact cites "10M+" SDK downloads across Python and TypeScript and "10k+" GitHub stars ([manufact.com](https://manufact.com/), vendor's own claim). Manufact quotes Y Combinator describing mcp-use as open-source dev tools and infrastructure for MCP ([manufact.com](https://manufact.com/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | mcp-use | Open-source TypeScript and Python SDK for MCP servers and MCP Apps. | open source; from 0 USD (source, as of 5 November 2026) | | Manufact Cloud | Git-based hosting, evals and analytics for MCP servers. | credits plus usage; from 0 USD; Pro 250 USD a month plus usage (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | manufact.com | 83 of 100, grade B | 4 November 2026 | how it was taken | | Cloudflare agent-readiness scan | manufact.com | 60 of 100, L4 Agent-Integrated; 9 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Manufact does not act as an identity provider for MCP servers on the pages read. - Manufact is not a public registry; its catalog ranks servers by its own quality score. ## Related on this site Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/manufact/index.md) ## Sources - [manufact.com/](https://manufact.com/), read 5 November 2026 - [MCP Hosting Pricing and Plans | Manufact](https://manufact.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Mastra: MCP vendor profile | Agent MCP Directory" description: "Mastra: SDK or framework. Products: @mastra/mcp, Mastra platform. 6 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/mastra site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Mastra: MCP vendor profile | Agent MCP Directory > Mastra: SDK or framework. Products: @mastra/mcp, Mastra platform. 6 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/mastra Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mastra: MCP vendor profile Mastra is an open-source TypeScript agent framework whose @mastra/mcp package provides an MCP client for agents and an MCPServer that exposes Mastra tools and agents to external MCP clients, as documented by the vendor. Mastra's MCP support installs as @mastra/mcp with npm, pnpm, yarn or bun, and the docs link a migration guide for users of @mastra/mcp 1.x (mastra.ai). ## At a glance | Type | SDKs and frameworks | | --- | --- | | Home | mastra.ai | | Price | open source; monthly plus usage | | Read | 5 November 2026 | ## What it does for this layer Mastra's MCPClient lists tools from configured servers so an agent can use them, for example tools: await mcpClient.listTools() ([mastra.ai](https://mastra.ai/docs/tools-mcp/mcp-overview)). npx @mastra/mcp generate writes a typed MCPServers interface that the MCPClient constructor accepts ([mastra.ai](https://mastra.ai/docs/tools-mcp/mcp-overview)). The Mastra docs URL /docs/tools-mcp/mcp-overview redirected to /docs/connections/mcp on 5 Nov 2026 ([mastra.ai](https://mastra.ai/docs/tools-mcp/mcp-overview), observed 5 November 2026). Mastra pricing lists a free tier with 100K observability events and 24 CPU hours, and a 250 USD a month tier with 1M events and 250 CPU hours ([mastra.ai](https://mastra.ai/pricing)). Mastra can create an MCPServer to expose Mastra primitives to external MCP clients ([mastra.ai](https://mastra.ai/docs/tools-mcp/mcp-overview)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | @mastra/mcp | MCP client and server package for Mastra agents. | open source; from 0 USD (source, as of 5 November 2026) | | Mastra platform | Hosted observability and compute for Mastra agents. | monthly plus usage; from 0 USD; 250 USD a month tier (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | mastra.ai | 78 of 100, grade B | 1 November 2026 | how it was taken | | Cloudflare agent-readiness scan | mastra.ai | 33 of 100, L1 Basic Web Presence; 5 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Mastra is TypeScript only on the pages read. - Mastra's MCP client does not act as an authorization server; it completes OAuth as a client ([mastra.ai](https://mastra.ai/docs/tools-mcp/mcp-overview)). ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/mastra/index.md) ## Sources - [Mastra home](https://mastra.ai/), read 5 November 2026 - [MCP | Connections | Mastra Docs](https://mastra.ai/docs/tools-mcp/mcp-overview), read 5 November 2026 - [Pricing | Mastra](https://mastra.ai/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP Market: MCP vendor profile | Agent MCP Directory" description: "MCP Market: registry or directory. Products: MCP Market directory. 6 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/mcp-market site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP Market: MCP vendor profile | Agent MCP Directory > MCP Market: registry or directory. Products: MCP Market directory. 6 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/mcp-market Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP Market: MCP vendor profile MCP Market is a public directory of MCP servers, agent skills and MCP clients, sorted by category, with a section for official servers and a marketplace for selling skills, as documented by the vendor. MCP Market lists servers by category, including Developer Tools, Data Science and ML, API Development, Security and Testing, and Deployment and DevOps (mcpmarket.com). ## At a glance | Type | Registries and directories | | --- | --- | | Home | mcpmarket.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer MCP Market showed "51,763 Servers" with the note "Updated just now" on 5 Nov 2026 ([mcpmarket.com](https://mcpmarket.com/), observed 5 November 2026). MCP Market describes itself as a "Directory of awesome MCP servers and clients to connect AI agents with your favorite tools" ([mcpmarket.com](https://mcpmarket.com/)). MCP Market has a section for official MCP servers with a "View all official servers" link ([mcpmarket.com](https://mcpmarket.com/)). MCP Market lists Agent Skills next to MCP servers, MCP clients and agent tools ([mcpmarket.com](https://mcpmarket.com/)). MCP Market's navigation includes "Sell Skills", a marketplace path for skill authors ([mcpmarket.com](https://mcpmarket.com/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Market directory | Public directory of MCP servers, skills and clients. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | Agent Skills | skills listings | Supports | Lists Agent Skills next to MCP servers. | mcpmarket.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | mcpmarket.com | 60 of 100, grade C | 19 October 2026 | how it was taken | | Cloudflare agent-readiness scan | mcpmarket.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - MCP Market does not state how it verifies the servers it lists on the home page read. - MCP Market does not host MCP servers. ## Related on this site Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/mcp-market/index.md) ## Sources - [MCP Market | Discover Top MCP Servers & Agent Skills](https://mcpmarket.com/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "MCP official SDKs: MCP vendor profile | Agent MCP Directory" description: "MCP official SDKs: SDK or framework. Products: Official SDKs. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/mcp-official-sdks site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # MCP official SDKs: MCP vendor profile | Agent MCP Directory > MCP official SDKs: SDK or framework. Products: Official SDKs. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/mcp-official-sdks Site: Agent MCP Directory Last reviewed: 2026-11-05 # MCP official SDKs: MCP vendor profile The Model Context Protocol project publishes ten official SDKs, ranked in three tiers by feature completeness, protocol support and maintenance commitment, for building MCP servers and clients, as documented by the vendor. The MCP SDK page lists ten official SDKs under the modelcontextprotocol GitHub organisation: TypeScript, Python, C#, Go, Rust, Ruby, Java, Swift, PHP and Kotlin (modelcontextprotocol.io). ## At a glance | Listed as | MCP official SDKs (modelcontextprotocol) | | --- | --- | | Type | SDKs and frameworks | | Operator | MCP maintainers under the Agentic AI Foundation | | Home | modelcontextprotocol.io | | Price | open source | | Read | 5 November 2026 | ## What it does for this layer The SDK page says SDKs "adopt new protocol revisions on their own schedules", so each SDK's own documentation states which revisions it supports ([modelcontextprotocol.io](https://modelcontextprotocol.io/docs/sdk)). All official MCP SDKs support creating servers with tools, resources and prompts, building clients, local and remote transports, and type-safe protocol compliance ([modelcontextprotocol.io](https://modelcontextprotocol.io/docs/sdk)). The SDK page resolved to the 2026-07-28 documentation version (/docs/2026-07-28/sdk) on 5 Nov 2026 ([modelcontextprotocol.io](https://modelcontextprotocol.io/docs/sdk), observed 5 November 2026). TypeScript, Python, C#, Go, Rust and Ruby are Tier 1 SDKs; Java is Tier 2; Swift, PHP and Kotlin are Tier 3 ([modelcontextprotocol.io](https://modelcontextprotocol.io/docs/sdk)). The MCP project classifies SDKs into tiers "based on feature completeness, protocol support, and maintenance commitment" ([modelcontextprotocol.io](https://modelcontextprotocol.io/docs/sdk)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Official SDKs | Ten language SDKs for MCP servers and clients. | open source; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | reference implementations | Supports | Official SDKs for the protocol, adopting revisions on their own schedules. | modelcontextprotocol.io | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | modelcontextprotocol.io | 69 of 100, grade C | 16 October 2026 | how it was taken | | Cloudflare agent-readiness scan | modelcontextprotocol.io | 53 of 100, L4 Agent-Integrated; 8 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - The MCP project does not host servers built with the SDKs. ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/mcp-official-sdks/index.md) ## Sources - [SDKs - Model Context Protocol](https://modelcontextprotocol.io/docs/sdk), read 5 November 2026 (the project's own page) Last reviewed 5 November 2026 --- --- title: "Merge: MCP vendor profile | Agent MCP Directory" description: "Merge: connector platform. Products: Agent Handler. 8 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/merge site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Merge: MCP vendor profile | Agent MCP Directory > Merge: connector platform. Products: Agent Handler. 8 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/merge Site: Agent MCP Directory Last reviewed: 2026-11-05 # Merge: MCP vendor profile Merge Agent Handler gives AI agents per-end-user access to 190+ MCP-ready third-party connectors through Tool Packs, with a Security Gateway that scans every tool call against data-loss rules, as documented by the vendor. A Merge Tool Pack is the set of tools an agent can reach at a given moment, governed and versioned per agent surface (docs.merge.dev). ## At a glance | Listed as | Merge (Agent Handler) | | --- | --- | | Type | Connector platforms | | Home | www.merge.dev | | Price | no published price | | Read | 5 November 2026 | ## What it does for this layer Each Agent Handler MCP connection uses the URL pattern https://ah-api.merge.dev/api/v1/tool-packs//registered-users//mcp, with an Access Key in the Authorization header ([docs.merge.dev](https://docs.merge.dev/merge-agent-handler/build/connecting-agents/mcp-integration.md)). Merge's Security Gateway scans every tools/call against entity rules (identity, government and financial IDs, payment, health, network), custom regex rules and natural-language guardrails ([docs.merge.dev](https://docs.merge.dev/merge-agent-handler/overview.md)). An agent with no Merge account can sign itself up with one unauthenticated POST to https://ah-api.merge.dev/api/v1/agent/signup/, which returns an API key, a starter Tool Pack and a Registered User ([docs.merge.dev](https://docs.merge.dev/merge-agent-handler/overview.md)). End users authenticate through Merge Link with OAuth, API keys or custom auth, or share credentials across a Group ([docs.merge.dev](https://docs.merge.dev/merge-agent-handler/overview.md)). Merge lists SOC 2 Type II, ISO 27001, HIPAA, GDPR and CCPA for Agent Handler, with extra application-level encryption on PII ([docs.merge.dev](https://docs.merge.dev/merge-agent-handler/overview.md)). Merge's docs run their own MCP server at https://docs.merge.dev/\_mcp/server ([docs.merge.dev](https://docs.merge.dev/merge-agent-handler/overview.md)). Merge describes Agent Handler as "the tool-calling platform for AI agents" with 190+ MCP-ready third-party connectors, a count dated September 2026 ([docs.merge.dev](https://docs.merge.dev/merge-agent-handler/overview.md)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Agent Handler | Per-user tool access for agents over MCP or HTTPS, with Tool Packs, DLP and audit. | no published price | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | merge.dev | 65 of 100, grade C | 26 October 2026 | how it was taken | | Cloudflare agent-readiness scan | merge.dev | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Merge Agent Handler is for agents acting for a product's customers, not for a company's own internal team, per Merge's guidance. - Merge does not publish Agent Handler prices on the pages read. ## Related on this site Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/merge/index.md) ## Sources - [Merge home](https://www.merge.dev/agent-handler), read 5 November 2026 - [Merge Agent Handler overview - Merge docs](https://docs.merge.dev/merge-agent-handler/overview.md), read 5 November 2026 - [MCP integration - Merge Agent Handler docs](https://docs.merge.dev/merge-agent-handler/build/connecting-agents/mcp-integration.md), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Microsoft Azure: MCP vendor profile | Agent MCP Directory" description: "Microsoft Azure: gateway or proxy. 3 products, 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/microsoft-azure site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Microsoft Azure: MCP vendor profile | Agent MCP Directory > Microsoft Azure: gateway or proxy. 3 products, 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/microsoft-azure Site: Agent MCP Directory Last reviewed: 2026-11-05 # Microsoft Azure: MCP vendor profile Microsoft Azure exposes REST APIs as remote MCP servers through API Management's AI gateway, hosts MCP tool functions with the Azure Functions MCP extension, and publishes an open-source MCP Gateway for Kubernetes, as documented by the vendor. MCP server support in API Management applies to the Developer, Basic, Basic v2, Standard, Standard v2, Premium and Premium v2 tiers (learn.microsoft.com). ## At a glance | Listed as | Microsoft Azure (API Management, Functions, MCP Gateway) | | --- | --- | | Type | Gateways and proxies | | Also covers | host or runtime | | Operator | Microsoft | | Home | learn.microsoft.com | | Price | open source, MIT | | Read | 5 November 2026 | ## What it does for this layer The Azure Functions MCP extension does not support PowerShell apps, and with the SSE transport it relies on Azure Queue storage in the host storage account ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-mcp)). Locally the Functions MCP extension needs Azure Functions Core Tools 4.0.7030 or later and Microsoft.Azure.Functions.Worker 2.1.0 or later ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-mcp)). Microsoft's open-source MCP Gateway is "a reverse proxy and management layer for MCP servers" with session-aware stateful routing on Kubernetes; the repository is MIT licensed with about 907 stars on 5 Nov 2026 ([github.com](https://github.com/microsoft/mcp-gateway)). Azure API Management can expose a REST API it manages as a remote MCP server through its built-in AI gateway, turning API operations into MCP tools ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/api-management/export-rest-mcp-server)). API Management MCP servers built from REST APIs support tools only, not MCP resources or prompts, and MCP servers are not supported in workspaces ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/api-management/export-rest-mcp-server)). API Management can also front existing MCP servers hosted outside API Management ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/api-management/export-rest-mcp-server)). The Azure Functions MCP extension creates remote MCP servers from functions with tool, resource and prompt triggers ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Azure API Management MCP servers | Expose REST APIs or front existing MCP servers through the AI gateway. | price not read | | Azure Functions MCP extension | Host MCP tools, resources and prompts as functions. | price not read | | microsoft/mcp-gateway | Open-source Kubernetes reverse proxy for MCP servers. | open source, MIT; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | tools only from REST | Partial | REST-derived MCP servers support tools but not resources or prompts. | learn.microsoft.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | learn.microsoft.com | 24 of 100, grade F | 15 October 2026 | how it was taken | | Cloudflare agent-readiness scan | learn.microsoft.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - API Management does not turn non-HTTP API types into MCP servers. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/microsoft-azure/index.md) ## Sources - [Expose REST API as MCP server - Azure API Management | Microsoft Learn](https://learn.microsoft.com/en-us/azure/api-management/export-rest-mcp-server), read 5 November 2026 - [Model context protocol bindings for Azure Functions | Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-mcp), read 5 November 2026 - [GitHub - microsoft/mcp-gateway](https://github.com/microsoft/mcp-gateway), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Mintive: MCP vendor profile | Agent MCP Directory" description: "Mintive: gateway or proxy. Products: MCP Gateway. 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/mintive site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Mintive: MCP vendor profile | Agent MCP Directory > Mintive: gateway or proxy. Products: MCP Gateway. 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/mintive Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mintive: MCP vendor profile Mintive, formerly MintMCP, sells a managed MCP gateway that hosts approved MCP servers, groups them into role-based bundles, gives agents their own credentials and logs every call, as documented by the vendor. Mintive Agent Identities give each agent delegated, least-privilege credentials that can be revoked on their own, for Claude, ChatGPT workspace agents and Cursor background agents (www.mintmcp.com). ## At a glance | Listed as | Mintive (formerly MintMCP) | | --- | --- | | Type | Gateways and proxies | | Also covers | host or runtime | | Home | www.mintive.com | | Price | no published price | | Read | 5 November 2026 | ## What it does for this layer mintmcp.com redirected to mintive.com on 5 Nov 2026, and the page title reads "Mintive (formerly MintMCP)" ([www.mintmcp.com](https://www.mintmcp.com/), observed 5 November 2026). Mintive's Mint Guard screens calls for prompt injection, exposed secrets and personal data before they reach company systems ([www.mintmcp.com](https://www.mintmcp.com/)). Mintive lists SOC 2 Type II, SSO through SAML or OIDC, audit log export to a SIEM or over OTLP, and EU and US data residency ([www.mintmcp.com](https://www.mintmcp.com/)). Mintive says more than 50 customers run 2.5 million agent calls a day through it ([www.mintmcp.com](https://www.mintmcp.com/), vendor's own claim). Mintive pricing is custom, with per-user licensing and platform fees; plans include managed MCP server hosting and "1,000+ pre-built connectors" ([www.mintmcp.com](https://www.mintmcp.com/pricing)). Mintive's MCP Gateway lets an admin approve servers, group them into role-based bundles and switch off destructive tools ([www.mintmcp.com](https://www.mintmcp.com/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Gateway | Managed MCP server hosting and routing with role-based bundles. | custom, per user plus platform fee; No public price (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | mintive.com | no cached score GET /api/score returned HTTP 404 (no cached score) | not scanned | how it was taken | | Cloudflare agent-readiness scan | mintive.com | 27 of 100, L1 Basic Web Presence; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Mintive does not publish list prices. - Mintive is not an open-source gateway; the pages read describe a managed service only. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/mintive/index.md) ## Sources - [Mintive home](https://www.mintive.com/), read 5 November 2026 - [Mintive (formerly MintMCP) home page](https://www.mintmcp.com/), read 5 November 2026 - [Mintive pricing](https://www.mintmcp.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Mintlify: MCP vendor profile | Agent MCP Directory" description: "Mintlify: host or runtime. Products: Search MCP server, plus 2 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/mintlify site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Mintlify: MCP vendor profile | Agent MCP Directory > Mintlify: host or runtime. Products: Search MCP server, plus 2 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/mintlify Site: Agent MCP Directory Last reviewed: 2026-11-05 # Mintlify: MCP vendor profile Mintlify generates and hosts a search MCP server for every docs site it builds, exposes skill files as MCP resources, registers WebMCP tools on Pro plans, and scores docs sites for agent readability, as documented by the vendor. Skills with a groups field are only exposed to authenticated end users whose groups match, on Mintlify sites that use authentication (www.mintlify.com). ## At a glance | Type | Hosts and runtimes | | --- | --- | | Home | www.mintlify.com | | Price | included from Starter; Pro and Enterprise | | Read | 5 November 2026 | ## What it does for this layer Mintlify's search MCP server lets a connected AI application search a docs site and retrieve full pages as Markdown ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol.md)). The Mintlify query docs filesystem tool reads a site's virtual filesystem with shell-style commands, including batch reads across pages in one call ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol.md)). Mintlify's WebMCP page says it registers tools with the browser's navigator.modelContext API, while the WebMCP draft documents document.modelContext ([www.mintlify.com](https://www.mintlify.com/docs/ai/model-context-protocol.md) and [github.com](https://github.com/webmachinelearning/webmcp), observed 5 November 2026). Mintlify pricing lists Starter at 0 USD a month with an MCP server, 5 editor seats and a custom domain ([www.mintlify.com](https://www.mintlify.com/pricing)). Mintlify Pro is 450 USD a month billed annually or 540 USD billed monthly, with unlimited editor seats and the Assistant ([www.mintlify.com](https://www.mintlify.com/pricing)). Mintlify's Agent Score page scores docs "the way an agent sees them" and says it is "Built on the AFDocs standard", with a live leaderboard by category ([www.mintlify.com](https://www.mintlify.com/score)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Search MCP server | Hosted MCP server generated for each Mintlify docs site. | included from Starter; from 0 USD (source, as of 5 November 2026) | | WebMCP tools | Docs tools registered in the page for in-browser agents. | Pro and Enterprise; from 450 USD; Pro 450 USD a month billed annually (source, as of 5 November 2026) | | Agent Score | Agent-readability score and leaderboard for docs sites. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | WebMCP | WebMCP tools on pages | Partial | Registers WebMCP tools on Pro and Enterprise plans, citing navigator.modelContext rather than the draft's document.modelContext. | www.mintlify.com | | Agent Skills | skills as resources | Supports | skill.md files exposed as MCP resources. | www.mintlify.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | mintlify.com | 74 of 100, grade B | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan | mintlify.com | 47 of 100, L1 Basic Web Presence; 7 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Mintlify does not host MCP servers for anything other than the docs sites it builds. - Mintlify's WebMCP tools are not on the free Starter plan. ## Relation to Ora Ora's launch post of 19 October 2026 gives Mintlify the docs seat on the AgentReady.org committee, reviewing how to build docs that agents read and cite, and names mintlify.com/score as the public ranker that grades documentation ([ora.ai](https://ora.ai/blog/agentready-launch?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026). ## Related on this site Hosts page - [Mintlify MCP](https://agentmcpdirectory.com/hosts/mintlify-mcp/) Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Standards - [WebMCP](https://agentmcpdirectory.com/standards/webmcp/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/mintlify/index.md) ## Sources - [Mintlify home](https://www.mintlify.com/docs/ai/model-context-protocol), read 5 November 2026 - [Model Context Protocol - Mintlify docs (markdown)](https://www.mintlify.com/docs/ai/model-context-protocol.md), read 5 November 2026 - [webmachinelearning/webmcp: WebMCP draft (GitHub)](https://github.com/webmachinelearning/webmcp), read 5 November 2026 (the project's own page) - [Pricing - Mintlify](https://www.mintlify.com/pricing), read 5 November 2026 - [Agent Score - Mintlify](https://www.mintlify.com/score), read 5 November 2026 - [Introducing AgentReady.org: the first open standard for AX | Ora](https://ora.ai/blog/agentready-launch?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "n8n: MCP vendor profile | Agent MCP Directory" description: "n8n: connector platform. Products: Instance-level MCP server, plus 1 more. 7 dated facts, price status and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/n8n site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # n8n: MCP vendor profile | Agent MCP Directory > n8n: connector platform. Products: Instance-level MCP server, plus 1 more. 7 dated facts, price status and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/n8n Site: Agent MCP Directory Last reviewed: 2026-11-05 # n8n: MCP vendor profile n8n includes a built-in MCP server per instance that lets MCP clients search workflows, run the ones marked available to MCP, and create or edit workflows and data tables, on n8n Cloud or self-hosted, as documented by the vendor. n8n recommends OAuth for the MCP connection, with access-token rotation and callback URL restrictions documented (docs.n8n.io). ## At a glance | Listed as | n8n (instance-level MCP) | | --- | --- | | Type | Connector platforms | | Home | docs.n8n.io | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer The n8n MCP server URL is copied from Settings, Instance-level MCP, Connect a client, and ends in /mcp-server/http ([docs.n8n.io](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/)). Auto-exposing new workflows to MCP is rolling out gradually from n8n 2.36.0, per the docs on 5 Nov 2026 ([docs.n8n.io](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/)). n8n documents a separate MCP Server Trigger node and explains how it differs from instance-level MCP access ([docs.n8n.io](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/)). On self-hosted n8n, instance-level MCP access can be disabled completely ([docs.n8n.io](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/)). MCP clients can manage n8n agents from n8n 2.34.0; agents are marked Preview ([docs.n8n.io](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/)). n8n runs a docs MCP server alongside the instance-level server ([docs.n8n.io](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Instance-level MCP server | Built-in MCP server for an n8n Cloud or self-hosted instance. | price not read | | MCP Server Trigger node | Workflow node that exposes a workflow as an MCP server. | price not read | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | n8n.io | 71 of 100, grade B | 9 October 2026 | how it was taken | | Cloudflare agent-readiness scan | n8n.io | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - n8n does not expose every workflow to MCP by default; workflows must be marked available ([docs.n8n.io](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/)). ## Related on this site Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/n8n/index.md) ## Sources - [Connect to n8n MCP server - n8n Docs](https://docs.n8n.io/advanced-ai/accessing-n8n-mcp-server/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Nango: MCP vendor profile | Agent MCP Directory" description: "Nango: connector platform. Products: MCP Auth. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/nango site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Nango: MCP vendor profile | Agent MCP Directory > Nango: connector platform. Products: MCP Auth. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/nango Site: Agent MCP Directory Last reviewed: 2026-11-05 # Nango: MCP vendor profile Nango is an integration layer whose MCP Auth lets an app authorise each end user against external MCP servers such as Notion, Linear or HubSpot, store the tokens and call those servers through Nango's proxy, as documented by the vendor. ## At a glance | Type | Connector platforms | | --- | --- | | Also covers | auth provider | | Home | www.nango.dev | | Price | free tier, then credits | | Read | 5 November 2026 | ## What it does for this layer Nango offers catalog MCP servers and a Generic MCP Server OAuth2 integration for any server that supports the MCP protocol ([nango.dev](https://nango.dev/docs/guides/auth/mcp-auth.md)). Nango can register itself with an MCP server by dynamic client registration or by publishing a Client ID Metadata Document, which needs a public HTTPS Nango instance ([nango.dev](https://nango.dev/docs/guides/auth/mcp-auth.md)). Some providers, for example HubSpot MCP, require the developer to register their own MCP auth app and enter its client ID and secret in Nango ([nango.dev](https://nango.dev/docs/guides/auth/mcp-auth.md)). Nango's docs list a Management MCP for managing Nango from an MCP client, and a migration from the Connection MCP to scoped agent sessions ([www.nango.dev](https://www.nango.dev/llms.txt)). Nango pricing lists Free at 0 USD with hard-capped limits, Pay-as-you-go at 50 USD a month with 50 USD of credits, and custom Enterprise with self-hosting ([www.nango.dev](https://www.nango.dev/pricing)). Nango's MCP Auth "lets your application authorize end users to access external MCP servers, such as Notion MCP, Linear MCP, or HubSpot MCP" ([nango.dev](https://nango.dev/docs/guides/auth/mcp-auth.md)). Nango handles OAuth with the MCP provider, stores the tokens and lets the app call the MCP server through Nango's proxy ([nango.dev](https://nango.dev/docs/guides/auth/mcp-auth.md)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Auth | Per-user OAuth to external MCP servers with token storage and proxy. | free tier, then credits; from 0 USD; Pay-as-you-go 50 USD a month (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | client ID metadata documents | Supports | Nango can publish a CIMD the provider fetches at connect time. | nango.dev | | MCP | dynamic client registration | Supports | Nango registers through the server's DCR endpoint. | nango.dev | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | nango.dev | 65 of 100, grade C | 26 October 2026 | how it was taken | | Cloudflare agent-readiness scan | nango.dev | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Nango does not host MCP servers; it authorises users against servers run by others. ## Related on this site Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/nango/index.md) ## Sources - [Nango home](https://www.nango.dev/), read 5 November 2026 - [nango.dev/docs/guides/auth/mcp-auth.md](https://nango.dev/docs/guides/auth/mcp-auth.md), read 5 November 2026 - [Nango llms.txt](https://www.nango.dev/llms.txt), read 5 November 2026 - [Pricing | Nango](https://www.nango.dev/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Netlify: MCP vendor profile | Agent MCP Directory" description: "Netlify: host or runtime. Products: Netlify Functions, plus 1 more. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/netlify site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Netlify: MCP vendor profile | Agent MCP Directory > Netlify: host or runtime. Products: Netlify Functions, plus 1 more. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/netlify Site: Agent MCP Directory Last reviewed: 2026-11-05 # Netlify: MCP vendor profile Netlify hosts stateless MCP servers as serverless functions answering at /mcp, publishes a deploy-button template, and runs its own remote Netlify MCP server for coding agents, as documented by the vendor. Netlify's guide uses a stateless form of MCP: transactional HTTP calls with StreamableHTTPServerTransport, not long-lived SSE connections (developers.netlify.com). ## At a glance | Type | Hosts and runtimes | | --- | --- | | Home | developers.netlify.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer Netlify's example serves the MCP server at the /mcp path, http://localhost:8888/mcp locally and https:///mcp when deployed ([developers.netlify.com](https://developers.netlify.com/guides/write-mcps-on-netlify/)). Netlify recommends its remote MCP server for the most current capabilities and offers a local server, @netlify/mcp, for environments that require one ([docs.netlify.com](https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/)). Netlify's guide builds an MCP server and deploys it to Netlify as a serverless function, with a deploy button that creates a new site with "a serverless MCP ready to go" ([developers.netlify.com](https://developers.netlify.com/guides/write-mcps-on-netlify/)). Netlify's guide tests the deployed server with the MCP Inspector through npx mcp-remote@next ([developers.netlify.com](https://developers.netlify.com/guides/write-mcps-on-netlify/)). Netlify runs a remote MCP server at https://mcp.netlify.com/mcp; connections made with the older https://netlify-mcp.netlify.app/mcp URL keep working ([docs.netlify.com](https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/)). Netlify's docs add its MCP server to agents with npx -y add-mcp https://mcp.netlify.com/mcp ([docs.netlify.com](https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Netlify Functions | Serverless hosting for stateless MCP servers. | price not read | | Netlify MCP server | Remote and local MCP server that gives agents Netlify expertise and the Netlify CLI. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | stateless streamable HTTP | Supports | Guide uses stateless StreamableHTTPServerTransport. | developers.netlify.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | netlify.com | 90 of 100, grade A | 4 November 2026 | how it was taken | | Cloudflare agent-readiness scan | netlify.com | 67 of 100, L5 Agent-Native; 10 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Netlify does not run a public registry of MCP servers. ## Related on this site Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/netlify/index.md) ## Sources - [Building MCPs with Netlify - Netlify Developers](https://developers.netlify.com/guides/write-mcps-on-netlify/), read 5 November 2026 - [Agent setup overview | Netlify Docs](https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Obot: MCP vendor profile | Agent MCP Directory" description: "Obot: gateway or proxy. Products: Obot (open source), Obot Cloud. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/obot site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Obot: MCP vendor profile | Agent MCP Directory > Obot: gateway or proxy. Products: Obot (open source), Obot Cloud. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/obot Site: Agent MCP Directory Last reviewed: 2026-11-05 # Obot: MCP vendor profile Obot is an open-source platform that hosts MCP servers, exposes them through a governed MCP gateway as virtual MCP servers, and keeps MCP and Agent Skills catalogs behind the MCP Registry API, as documented by the vendor. Obot can inspect, reject or modify MCP requests and responses with MCP or webhook filters (docs.obot.ai). ## At a glance | Type | Gateways and proxies | | --- | --- | | Also covers | host or runtime, registry or directory | | Home | obot.ai | | Price | no published price | | Read | 5 November 2026 | ## What it does for this layer Obot docs describe Obot as "an open-source platform for organizations to manage, secure, and govern their AI ecosystems", with docs at version v0.27.0 on 5 Nov 2026 ([docs.obot.ai](https://docs.obot.ai/)). Obot's MCP Gateway creates vMCPs from catalog servers with only the tools users need and shares them with users and groups through one connection URL ([docs.obot.ai](https://docs.obot.ai/)). Obot controls server and tool access by user or identity-provider group and manages MCP OAuth, user and shared credentials, and Kubernetes secret bindings ([docs.obot.ai](https://docs.obot.ai/)). Obot hosts npx, uvx and containerised MCP servers as Docker containers or Kubernetes workloads, with domain-based egress rules ([docs.obot.ai](https://docs.obot.ai/)). Obot runs as Obot Cloud (hosted trial), locally with Docker, or in production on Kubernetes with a Helm chart ([docs.obot.ai](https://docs.obot.ai/)). Obot's LLM Gateway connects clients to OpenAI, Anthropic, Amazon Bedrock, Azure and Responses-compatible providers and records token usage and estimated cost ([docs.obot.ai](https://docs.obot.ai/)). Obot's MCP and Skills Registries can be curated in Obot or indexed from Git repositories, and expose MCP catalogs through the standard MCP Registry API ([docs.obot.ai](https://docs.obot.ai/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Obot (open source) | Self-hosted MCP gateway, hosting, registries and LLM gateway. | no published price | | Obot Cloud | Hosted Obot instance offered as a free trial. | no published price | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | registry API | Supports | Exposes MCP catalogs through the standard MCP Registry API. | docs.obot.ai | | Agent Skills | skills registry | Supports | Curates Agent Skills catalogs alongside MCP servers. | docs.obot.ai | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | obot.ai | 67 of 100, grade C | 9 October 2026 | how it was taken | | Cloudflare agent-readiness scan | obot.ai | 33 of 100, L1 Basic Web Presence; 5 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Obot's docs and home page read here give no price for Obot Cloud or the enterprise edition. - Obot is not a public directory of MCP servers; its catalogs are curated per organisation. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/obot/index.md) ## Sources - [Obot home](https://obot.ai/), read 5 November 2026 - [What is Obot? | Obot Docs](https://docs.obot.ai/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Official MCP Registry: MCP vendor profile | Agent MCP Directory" description: "Official MCP Registry: registry or directory. Products: MCP Registry API. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/official-mcp-registry site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Official MCP Registry: MCP vendor profile | Agent MCP Directory > Official MCP Registry: registry or directory. Products: MCP Registry API. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/official-mcp-registry Site: Agent MCP Directory Last reviewed: 2026-11-05 # Official MCP Registry: MCP vendor profile The official MCP Registry is the protocol project's central metadata store for public MCP servers, meant to be read by downstream marketplaces and private registries rather than directly by host applications, as documented by the vendor. The MCP project expects downstream aggregators to pull registry metadata on a regular but infrequent schedule, for example once per hour (modelcontextprotocol.io). ## At a glance | Type | Registries and directories | | --- | --- | | Operator | MCP Registry maintainers | | Home | registry.modelcontextprotocol.io | | Price | free | | Read | 5 November 2026 | ## What it does for this layer The MCP project calls the registry "the official centralized metadata repository for publicly accessible MCP servers", backed by contributors such as Anthropic, GitHub, PulseMCP and Microsoft ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). The registry accepts open-source and closed-source servers, as long as the install method (for example an npm package or a public Docker image) or the remote server itself is publicly reachable ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). The registry docs say it "is not intended to be directly consumed by host applications"; hosts should read downstream registries that implement its OpenAPI spec ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). The registry defines an OpenAPI spec that other MCP registries, public or private, can implement so host applications get one interface ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). The registry codebase "is not designed for self-hosting", and its maintainers do not support forks ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). The registry was still labelled a preview on 5 Nov 2026, with a warning that breaking changes or data resets may occur before general availability ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Registry API | Public REST API and OpenAPI spec for server metadata. | free; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | registry schema | Supports | Defines the server metadata schema and an OpenAPI spec other registries can implement. | modelcontextprotocol.io | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | registry.modelcontextprotocol.io | no cached score GET /api/score returned HTTP 404 (no cached score) | not scanned | how it was taken | | Cloudflare agent-readiness scan | registry.modelcontextprotocol.io | 0 of 100, L0 Not Ready; 0 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - The official registry does not curate or rate servers; that is left to downstream aggregators ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). ## Related on this site Hosts page - [Official MCP Registry](https://agentmcpdirectory.com/hosts/official-mcp-registry/) Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/official-mcp-registry/index.md) ## Sources - [Official MCP Registry home](https://registry.modelcontextprotocol.io/), read 5 November 2026 - [The MCP Registry - Model Context Protocol](https://modelcontextprotocol.io/registry/about), read 5 November 2026 (the project's own page) Last reviewed 5 November 2026 --- --- title: "OpenAI: MCP vendor profile | Agent MCP Directory" description: "OpenAI: registry or directory. 2 products, 8 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/openai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # OpenAI: MCP vendor profile | Agent MCP Directory > OpenAI: registry or directory. 2 products, 8 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/openai Site: Agent MCP Directory Last reviewed: 2026-11-05 # OpenAI: MCP vendor profile OpenAI's developer docs, formerly the Apps SDK, cover plugins that bundle MCP servers, skills and optional UI for ChatGPT and Codex, and a public directory that reviews remote MCP servers before listing, as documented by the vendor. OpenAI's auth guide expects authenticated plugin MCP servers to implement OAuth 2.1 conforming to the MCP authorization spec at revision 2025-11-25 (developers.openai.com). ## At a glance | Listed as | OpenAI (Plugins and Apps SDK directory) | | --- | --- | | Type | Registries and directories | | Also covers | SDK or framework | | Home | developers.openai.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer OpenAI says supported clients use Client ID Metadata Documents, dynamic client registration, predefined OAuth clients and PKCE ([developers.openai.com](https://developers.openai.com/plugins/build/auth.md)). OpenAI lists the MCP authorization requirements as hosting protected resource metadata, publishing OAuth metadata from the authorization server and echoing the resource parameter ([developers.openai.com](https://developers.openai.com/plugins/build/auth.md)). Remote MCP servers are submitted through "With MCP" using a stable, public HTTPS endpoint; local or desktop-only servers have a separate path ([developers.openai.com](https://developers.openai.com/plugins/deploy/submission.md)). Publishing a plugin under a person or company name requires individual or business verification in the OpenAI organization settings ([developers.openai.com](https://developers.openai.com/plugins/deploy/submission.md)). After first publication, changes to the MCP server are picked up automatically and go live once they pass automated checks; metadata and skill changes still need resubmission ([developers.openai.com](https://developers.openai.com/plugins/deploy/submission.md)). OpenAI's review page for remote MCP servers covers organization verification, management permissions, server requirements, review snapshots and version maintenance ([developers.openai.com](https://developers.openai.com/plugins/deploy/app-review.md)). developers.openai.com/apps-sdk opened a Plugins index on 5 Nov 2026 that describes plugins built "with skills, MCP servers, and optional UI" ([developers.openai.com](https://developers.openai.com/apps-sdk)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Plugins directory | Public directory of ChatGPT and Codex plugins with MCP servers, reviewed on submission. | price not read | | Plugins SDK (formerly Apps SDK) | Docs and UI reference for MCP servers with optional UI in ChatGPT. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | authorization spec 2025-11-25 | Supports | Auth guide links the 2025-11-25 authorization spec. | developers.openai.com | | MCP | client ID metadata documents | Supports | Supported clients use CIMD, DCR, predefined clients and PKCE. | developers.openai.com | | Agent Skills | skills in plugins | Supports | Plugins bundle skills around MCP tools. | developers.openai.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | openai.com | 58 of 100, grade C | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan | openai.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - OpenAI does not host the developer's MCP server; submissions point at the developer's own HTTPS endpoint. - The directory does not list a plugin before review and verification. ## Related on this site Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/openai/index.md) ## Sources - [developers.openai.com/apps-sdk](https://developers.openai.com/apps-sdk), read 5 November 2026 - [developers.openai.com/plugins/build/auth.md](https://developers.openai.com/plugins/build/auth.md), read 5 November 2026 - [developers.openai.com/plugins/deploy/submission.md](https://developers.openai.com/plugins/deploy/submission.md), read 5 November 2026 - [developers.openai.com/plugins/deploy/app-review.md](https://developers.openai.com/plugins/deploy/app-review.md), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Ora: MCP vendor profile | Agent MCP Directory" description: "Ora: registry or directory. Products: Ora MCP server, ax CLI, plus 2 more. 14 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/ora site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Ora: MCP vendor profile | Agent MCP Directory > Ora: registry or directory. Products: Ora MCP server, ax CLI, plus 2 more. 14 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/ora Site: Agent MCP Directory Last reviewed: 2026-11-05 # Ora: MCP vendor profile Ora scores domains, MCP server URLs and MCP Apps for agent readiness, lists scored products in a searchable directory, and exposes the same scan through a public MCP server and the ax CLI, as documented by the vendor. Ora declares its MCP server in /.well-known/mcp.json at https://ora.ai/api/mcp over streamable-http, with 18 tools that include scan\_domain, get\_score, run\_journey and generate\_agent\_files (ora.ai). ## At a glance | Type | Registries and directories | | --- | --- | | Operator | era labs | | Home | ora.ai | | Price | free, rate-limited by IP | | Read | 5 November 2026 | ## What it does for this layer Ora's integrations page says the server "runs on the legacy-era MCP 1.x serving stack" and is compatible with clients that support protocol revisions through 2025-11-25 ([ora.ai](https://ora.ai/integrations?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). Ora's integrations page lists Cursor, Claude.ai, VS Code, Goose and Windsurf as platforms where the Ora MCP server can be added ([ora.ai](https://ora.ai/integrations?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). The ax CLI runs the Ora audit with npx ax audit and, per the CLI docs, needs "Zero install, no account"; --json emits the full report and --min-score exits non-zero below a threshold so a CI step fails ([ora.ai](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). The ax CLI can audit a local server through the user's own tunnel with --tunnel-cmd, for example ngrok on port 3000 ([ora.ai](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). Ora's pricing endpoint lists a single Free plan at 0 USD with "10 scans per minute", "Unlimited score lookups" and MCP server access, and says all endpoints are open and rate-limited by IP ([ora.ai](https://ora.ai/pricing?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). Ora's auth.md states that no Ora API is OAuth-protected: there is no /.well-known/oauth-protected-resource, and /.well-known/openid-configuration is described as "a discovery signal, not a live OAuth authorization server" ([ora.ai](https://ora.ai/auth.md?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). Feedback writes to Ora are MCP-only and require the get\_verification\_challenge tool, a reverse challenge that proves the caller is an agent, with no account or key ([ora.ai](https://ora.ai/auth.md?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). Ora issues API keys manually per partner; auth.md says Ora "does not currently support agentic self-registration" ([ora.ai](https://ora.ai/auth.md?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). Ora's llms.txt says every ora.ai page registers WebMCP tools through document.modelContext: scan\_domain, get\_score and get\_leaderboard ([ora.ai](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). The Ora directory page calls itself "The agentic index of the web" and tags each listed product with capabilities such as MCP server and OpenAPI next to its agent-readiness score ([ora.ai](https://ora.ai/directory?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). The Ora home page showed "145,714 sites scanned" on 5 Nov 2026 ([ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), vendor's own claim). A GET of the official MCP Registry search for "eralabs" (and for "ora.ai") returned zero servers on 5 Nov 2026, so Ora's MCP server is not listed there under its own namespace ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/v0/servers?search=eralabs), observed 5 November 2026). Ora runs a second, read-only docs MCP server at https://ora.ai/api/docs/mcp with search\_docs, get\_docs\_page and get\_endpoint tools ([ora.ai](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Ora MCP server | Public Streamable HTTP MCP server with scan, score, leaderboard, discovery, feedback, skills and journey tools. | free, rate-limited by IP; from 0 USD (source, as of 5 November 2026) | | ax CLI | npm package that runs the Ora audit from a terminal or CI and can gate a build on a minimum score. | free; from 0 USD (source, as of 5 November 2026) | | Ora directory (ARD) | Searchable index of scored products, MCP servers, docs and paid capabilities, with an /api/ard/search endpoint. | price not read | | Journey | Sends a real agent at a domain with an intent and records the trajectory; custom tasks need a partner key. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | spec revision | Partial | Ora states compatibility with protocol revisions through 2025-11-25 on an MCP 1.x stack; no statement of 2026-07-28 support. | ora.ai | | MCP | streamable HTTP | Supports | mcp.json declares transport streamable-http at https://ora.ai/api/mcp. | ora.ai | | MCP | discovery file | Supports | Ora publishes /.well-known/mcp.json with the server URL, transport and tool list. | ora.ai | | WebMCP | WebMCP tools on pages | Supports | Every ora.ai page registers scan_domain, get_score and get_leaderboard through document.modelContext. | ora.ai | | CLIs | ax audit | Supports | npx ax audit with --json and --min-score for CI. | ora.ai | | A2A | agent card | Supports | llms.txt links an A2A agent card at /.well-known/agent-card.json. | ora.ai | | NLWeb | ask method | Supports | llms.txt describes a native NLWeb ask through MCP and at /ask. | ora.ai | | Agent Skills | skills index | Supports | Skills are served by the MCP server and listed at /.well-known/agent-skills/index.json. | ora.ai | | OpenAPI | OpenAPI document | Supports | llms.txt points to https://ora.ai/api/openapi.json for the REST shapes. | ora.ai | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | ora.ai | 95 of 100, grade A+ | 5 November 2026 | how it was taken | | Ora leaderboard score in this directory's row, 4 November | ora.ai | 84 of 100, grade B | 4 November 2026 | the directory row | | Cloudflare agent-readiness scan, earlier reading | ora.ai | 75 of 100, L2 Bot-Aware; 12 of 16 counted checks passed | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan, later reading | ora.ai | 75 of 100, L5 Agent-Native; 12 of 16 counted checks passed Second reading the same day: the score stayed at 75 and the band moved from L2 Bot-Aware to L5 Agent-Native. | 5 November 2026, 14:39 UTC | how it was taken | Ora scores its own domain here, so the 95 is Ora's reading of Ora. The leaderboard row in this directory recorded 84 on 4 November 2026, and Ora's cached score read 95 on 5 November 2026. Cloudflare's scanner, run by a different party, read the same domain at 75 twice on 5 November 2026, band L2 Bot-Aware first and band L5 Agent-Native on the later scan. ## What it does not do - Ora does not host, proxy or gateway other companies' MCP servers. Ora is the check this directory recommends for testing an MCP server: [the reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/), [the checks it runs](https://agentmcpdirectory.com/mcp-checks/), [its own MCP server and tools](https://agentmcpdirectory.com/ora-mcp-server/) and [the directory's companies by Ora score](https://agentmcpdirectory.com/ora-scores/). ## Related on this site Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) - [WebMCP](https://agentmcpdirectory.com/standards/webmcp/) - [CLIs](https://agentmcpdirectory.com/standards/cli-as-agent-surface/) - [A2A](https://agentmcpdirectory.com/standards/a2a/) - [NLWeb](https://agentmcpdirectory.com/standards/nlweb/) - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) - [OpenAPI](https://agentmcpdirectory.com/standards/openapi-as-agent-surface/) Directory - [Ora](https://agentmcpdirectory.com/directory/ora-ai/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/ora/index.md) ## Sources - [Ora | Make your site work for agents](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [ora MCP manifest (/.well-known/mcp.json)](https://ora.ai/.well-known/mcp.json?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [ora Integrations](https://ora.ai/integrations?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [CLI - Docs | Ora](https://ora.ai/docs/cli?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [ora pricing (JSON)](https://ora.ai/pricing?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [Agent authentication on ora.ai (auth.md)](https://ora.ai/auth.md?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [ora llms.txt](https://ora.ai/llms.txt?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [The agentic index of the web | Ora](https://ora.ai/directory?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 - [Official MCP Registry API search for eralabs](https://registry.modelcontextprotocol.io/v0/servers?search=eralabs), read 5 November 2026 (the project's own page) - [Ora public leaderboard](https://ora.ai/leaderboard?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 4 November 2026 (vendor-published score) Last reviewed 5 November 2026 --- --- title: "Pipedream: MCP vendor profile | Agent MCP Directory" description: "Pipedream: connector platform. Products: Connect (MCP), Conduit. 8 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/pipedream site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Pipedream: MCP vendor profile | Agent MCP Directory > Pipedream: connector platform. Products: Connect (MCP), Conduit. 8 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/pipedream Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pipedream: MCP vendor profile Pipedream Connect runs a remote MCP server that gives agents per-user access to 3,000+ apps and 10,000+ prebuilt tools, with Pipedream managing OAuth and storing each user's credentials, as documented by the vendor. Pipedream says user credentials are encrypted at rest and requests go through Pipedream's servers, so credentials are never exposed to AI models (pipedream.com). ## At a glance | Listed as | Pipedream (Connect MCP) | | --- | --- | | Type | Connector platforms | | Home | pipedream.com | | Price | free to build, paid in production | | Read | 5 November 2026 | ## What it does for this layer Developers point clients at Pipedream's remote MCP server at https://remote.mcp.pipedream.net/v3 ([pipedream.com](https://pipedream.com/docs/connect/mcp/developers)). Each Pipedream MCP request carries headers for the project (x-pd-project-id), environment (x-pd-environment, development or production), end user (x-pd-external-user-id) and app (x-pd-app-slug) ([pipedream.com](https://pipedream.com/docs/connect/mcp/developers)). Pipedream pricing says it is "Free to build" and charges when integrations go to production; the Startup plan is 99 USD a month billed annually or 150 USD billed monthly ([pipedream.com](https://pipedream.com/pricing)). Pipedream's pricing page lists a second product, Conduit, "For companies deploying AI securely across their organization" ([pipedream.com](https://pipedream.com/pricing)). Pipedream says its MCP server covers 3,000+ integrated apps and "Over 10,000 pre-built tools" ([pipedream.com](https://pipedream.com/docs/connect/mcp), vendor's own claim). Pipedream MCP is powered by Pipedream Connect, with fully managed OAuth and credential storage isolated per user ([pipedream.com](https://pipedream.com/docs/connect/mcp)). End users can connect their own accounts through Pipedream MCP at mcp.pipedream.com ([pipedream.com](https://pipedream.com/docs/connect/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Connect (MCP) | Remote MCP server with per-user OAuth across 3,000+ apps. | free to build, paid in production; from 99 USD; Startup 99 USD a month billed annually (source, as of 5 November 2026) | | Conduit | Pipedream product for deploying AI across an organisation. | price not read | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | pipedream.com | no cached score GET /api/score returned HTTP 404 (no cached score) | not scanned | how it was taken | | Cloudflare agent-readiness scan | pipedream.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Pipedream does not host the developer's own MCP server code on the pages read; it serves its own tools. ## Related on this site Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/pipedream/index.md) ## Sources - [MCP Servers - Pipedream](https://pipedream.com/docs/connect/mcp), read 5 November 2026 - [Develop with Pipedream MCP - Pipedream](https://pipedream.com/docs/connect/mcp/developers), read 5 November 2026 - [Pricing - Pipedream](https://pipedream.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Pomerium: MCP vendor profile | Agent MCP Directory" description: "Pomerium: gateway or proxy. Products: Pomerium Zero, Pomerium Enterprise. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/pomerium site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Pomerium: MCP vendor profile | Agent MCP Directory > Pomerium: gateway or proxy. Products: Pomerium Zero, Pomerium Enterprise. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/pomerium Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pomerium: MCP vendor profile Pomerium is an identity-aware proxy that puts internal or third-party MCP servers behind one gateway, runs downstream OAuth 2.1 and upstream OAuth for them, and limits tool calls by policy, as documented by the vendor. Pomerium service accounts let CI pipelines and autonomous agents call MCP tools as a specific user without an interactive login (www.pomerium.com). ## At a glance | Type | Gateways and proxies | | --- | --- | | Also covers | auth provider | | Home | www.pomerium.com | | Price | per user per month | | Read | 5 November 2026 | ## What it does for this layer Pomerium places internal MCP servers behind its gateway so external clients such as Claude, ChatGPT and VS Code can reach them, handling authentication, authorization and TLS termination ([www.pomerium.com](https://www.pomerium.com/docs/capabilities/mcp)). Pomerium authenticates the user through the organisation's identity provider with downstream OAuth 2.1 and manages the upstream OAuth flow, caching and refreshing tokens and injecting them into proxied requests ([www.pomerium.com](https://www.pomerium.com/docs/capabilities/mcp)). Pomerium's upstream OAuth pipeline supports pre-registered credentials for providers such as GitHub and Google and full auto-discovery via RFC 9728 for MCP servers that advertise their own metadata ([www.pomerium.com](https://www.pomerium.com/docs/capabilities/mcp)). Pomerium Policy Language has an mcp\_tool criterion that matches tool names by exact name, prefix, suffix or list, so admins can block patterns such as admin\_\* tools ([www.pomerium.com](https://www.pomerium.com/docs/capabilities/mcp)). Pomerium logs every MCP tool call with the method, tool name and parameters ([www.pomerium.com](https://www.pomerium.com/docs/capabilities/mcp)). For local development, ssh -R 0 pom.run exposes a local MCP server over HTTPS through Pomerium ([www.pomerium.com](https://www.pomerium.com/docs/capabilities/mcp)). Pomerium pricing lists Zero Personal free and Zero Business at 9 USD per user a month (7 USD billed annually), with Enterprise for self-hosting both planes ([www.pomerium.com](https://www.pomerium.com/pricing)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Pomerium Zero | Managed control plane with the data plane in the customer's environment. | per user per month; from 9 USD; Zero Personal free; Business 9 USD per user a month (source, as of 5 November 2026) | | Pomerium Enterprise | Self-hosted control and data planes. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | protected resource metadata | Supports | Auto-discovers upstream servers via RFC 9728. | www.pomerium.com | | MCP | OAuth 2.1 for clients | Supports | Downstream OAuth 2.1 through the identity provider. | www.pomerium.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | pomerium.com | 59 of 100, grade C | 30 August 2026 | how it was taken | | Cloudflare agent-readiness scan | pomerium.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Pomerium runs no MCP server code for customers; the servers stay on the customer's own infrastructure or the third party's. - Pomerium is not a public directory of MCP servers. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/pomerium/index.md) ## Sources - [Model Context Protocol (MCP) Support | Pomerium](https://www.pomerium.com/docs/capabilities/mcp), read 5 November 2026 - [Pricing | Pomerium](https://www.pomerium.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Portkey: MCP vendor profile | Agent MCP Directory" description: "Portkey: gateway or proxy. Products: MCP Gateway, plus 1 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/portkey site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Portkey: MCP vendor profile | Agent MCP Directory > Portkey: gateway or proxy. Products: MCP Gateway, plus 1 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/portkey Site: Agent MCP Directory Last reviewed: 2026-11-05 # Portkey: MCP vendor profile Portkey, now presented as Palo Alto Networks Prisma AIRS AI Gateway, runs an MCP Gateway with a central registry of servers and tools, identity-provider sign-in and per-user tool policy, self-hosted or managed, as documented by the vendor. Portkey describes its MCP Gateway as "A unified layer to access and govern MCP tools, without modifying your agents or servers" (portkey.ai). ## At a glance | Listed as | Portkey (Prisma AIRS AI Gateway) | | --- | --- | | Type | Gateways and proxies | | Operator | Palo Alto Networks | | Home | portkey.ai | | Price | open source, MIT | | Read | 5 November 2026 | ## What it does for this layer Portkey supports OAuth 2.1, API tokens and header auth for vendor and partner MCP servers ([portkey.ai](https://portkey.ai/features/mcp)). Portkey lists SOC 2 compliance and HIPAA, with SaaS, private cloud, VPC or fully self-hosted deployment ([portkey.ai](https://portkey.ai/features/mcp)). Portkey's open-source gateway repository is MIT licensed, had about 13.3k stars on 5 Nov 2026, and says it routes to "1,600+ LLMs" with "50+ AI Guardrails" ([github.com](https://github.com/Portkey-AI/gateway)). Portkey's MCP page is headed "Portkey is now PRISMA AIRS AI Gateway" ([portkey.ai](https://portkey.ai/features/mcp)). Portkey's MCP Gateway can be self-hosted, deployed to the customer's cloud or run fully managed ([portkey.ai](https://portkey.ai/features/mcp)). Portkey lists a central registry for MCP servers and tools and bring-your-own auth with Okta, Entra and other providers ([portkey.ai](https://portkey.ai/features/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Gateway | Governed access layer for MCP servers and tools. | price not read | | Portkey AI Gateway (open source) | MIT-licensed LLM gateway with guardrails. | open source, MIT; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | OAuth 2.1 upstream | Supports | OAuth 2.1, API tokens and header auth for upstream servers. | portkey.ai | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | portkey.ai | 69 of 100, grade C | 20 October 2026 | how it was taken | | Cloudflare agent-readiness scan | portkey.ai | 27 of 100, L1 Basic Web Presence; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Portkey's MCP page does not give an acquisition date for the Palo Alto Networks rebrand. ## Related on this site Hosts page - [Portkey](https://agentmcpdirectory.com/hosts/portkey/) Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/portkey/index.md) ## Sources - [Portkey home](https://portkey.ai/), read 5 November 2026 - [MCP Gateway - Secure Access to MCP Servers | Portkey](https://portkey.ai/features/mcp), read 5 November 2026 - [GitHub - Portkey-AI/gateway](https://github.com/Portkey-AI/gateway), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "FastMCP and FastMCP Gateway: MCP vendor profile | Agent MCP Directory" description: "FastMCP and FastMCP Gateway: SDK or framework. 2 products, 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/prefect-fastmcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # FastMCP and FastMCP Gateway: MCP vendor profile | Agent MCP Directory > FastMCP and FastMCP Gateway: SDK or framework. 2 products, 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/prefect-fastmcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # FastMCP and FastMCP Gateway: MCP vendor profile FastMCP is Prefect's open-source Python framework for MCP servers, clients and apps, and FastMCP Gateway is Prefect's commercial service that hosts and governs FastMCP servers from a git push, as documented by the vendor. The FastMCP site banner on 5 Nov 2026 announced FastMCP 4 as "built for the new MCP protocol" (gofastmcp.com). ## At a glance | Listed as | FastMCP and FastMCP Gateway (Prefect) | | --- | --- | | Type | SDKs and frameworks | | Also covers | host or runtime, gateway or proxy | | Operator | Prefect | | Home | gofastmcp.com | | Price | open source, Apache-2.0; free start, paid plans | | Read | 5 November 2026 | ## What it does for this layer FastMCP says it created the high-level Python API that was incorporated into the official MCP Python SDK in 2024 ([gofastmcp.com](https://gofastmcp.com/)). FastMCP says the standalone project is downloaded "more than a million times a day" and that some version of it "powers 70% of MCP servers across all languages" ([gofastmcp.com](https://gofastmcp.com/), vendor's own claim). FastMCP's source at PrefectHQ/fastmcp carries the Apache-2.0 license and showed about 28.3k GitHub stars on 5 Nov 2026 ([github.com](https://github.com/PrefectHQ/fastmcp), observed 5 November 2026). Prefect's FastMCP Gateway page cites "58M+ downloads a month" for FastMCP ([www.prefect.io](https://www.prefect.io/horizon), vendor's own claim). A git push deploys a FastMCP server to FastMCP Gateway at a horizon.prefect.io address, for example https://my-tools.horizon.prefect.io ([www.prefect.io](https://www.prefect.io/horizon)). Prefect says FastMCP Gateway puts one governed endpoint between AI clients and tools, with every call authenticated, authorised and logged ([www.prefect.io](https://www.prefect.io/horizon)). Prefect's pricing page refers to FastMCP Gateway as "our managed MCP platform", and the FastMCP Gateway page offers a free start ([www.prefect.io](https://www.prefect.io/pricing)). The www.prefect.io/horizon URL redirected to www.prefect.io/fastmcp on 5 Nov 2026 ([www.prefect.io](https://www.prefect.io/horizon), observed 5 November 2026). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | FastMCP | Open-source Python framework for MCP servers, clients and apps. | open source, Apache-2.0; from 0 USD (source, as of 5 November 2026) | | FastMCP Gateway | Managed hosting and governance for FastMCP servers. | free start, paid plans; from 0 USD; Commercial; plan prices not read (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | new protocol revision | Supports | FastMCP 4 is described as built for the new MCP protocol. | gofastmcp.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | gofastmcp.com | 63 of 100, grade C | 7 September 2026 | how it was taken | | Cloudflare agent-readiness scan | gofastmcp.com | 53 of 100, L4 Agent-Integrated; 8 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - FastMCP is Python only; TypeScript users need another framework. - FastMCP Gateway does not host servers written outside FastMCP, per the push-to-deploy flow on the page read. ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/prefect-fastmcp/index.md) ## Sources - [FastMCP: The Framework for MCP - FastMCP](https://gofastmcp.com/), read 5 November 2026 - [GitHub - PrefectHQ/fastmcp](https://github.com/PrefectHQ/fastmcp), read 5 November 2026 - [FastMCP Gateway: Deliver context and tools to every agent, safely | Prefect](https://www.prefect.io/horizon), read 5 November 2026 - [Pricing - Prefect Cloud](https://www.prefect.io/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "PulseMCP: MCP vendor profile | Agent MCP Directory" description: "PulseMCP: registry or directory. 2 products, 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/pulsemcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # PulseMCP: MCP vendor profile | Agent MCP Directory > PulseMCP: registry or directory. 2 products, 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/pulsemcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # PulseMCP: MCP vendor profile PulseMCP is an independent MCP directory of servers, clients and MCP Apps with The Agentic Loop newsletter, and offers partners an enriched registry API built on the official MCP Registry, as documented by the vendor. PulseMCP said on 5 Nov 2026 that new server submissions and listing changes were paused while it reworks how it ingests and manages listings (www.pulsemcp.com). ## At a glance | Type | Registries and directories | | --- | --- | | Home | www.pulsemcp.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer PulseMCP enriches listings with popularity data, security analyses, corrections to server.json metadata and compatibility analysis ([www.pulsemcp.com](https://www.pulsemcp.com/api)). PulseMCP's site describes a team member as an active member of the MCP Steering Committee who helps maintain the official MCP Registry ([www.pulsemcp.com](https://www.pulsemcp.com/)). PulseMCP's server directory page title read "MCP Server Directory: 21,580+ updated daily", and the page counted 21,587 servers on 5 Nov 2026 ([www.pulsemcp.com](https://www.pulsemcp.com/servers), observed 5 November 2026). PulseMCP's directory is fed by manual submissions, automated scraping and crawling with manual curation, and integration with the official MCP Registry ([www.pulsemcp.com](https://www.pulsemcp.com/api)). PulseMCP publishes The Agentic Loop newsletter and lists MCP clients and MCP Apps alongside servers ([www.pulsemcp.com](https://www.pulsemcp.com/)). The official MCP Registry names PulseMCP among the contributors that back the registry, with Anthropic, GitHub and Microsoft ([modelcontextprotocol.io](https://modelcontextprotocol.io/registry/about)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | PulseMCP directory | Public directory of MCP servers, clients and apps. | price not read | | PulseMCP Server Registry API | Enriched registry data for partners, by arrangement. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | registry schema | Supports | Integrates the official MCP Registry and corrects server.json metadata. | www.pulsemcp.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | pulsemcp.com | 11 of 100, grade F | 27 May 2026 | how it was taken | | Cloudflare agent-readiness scan | pulsemcp.com | 27 of 100, L2 Bot-Aware; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - PulseMCP's registry API is not self-serve; it is offered to partners by arrangement ([www.pulsemcp.com](https://www.pulsemcp.com/api)). ## Related on this site Type - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/pulsemcp/index.md) ## Sources - [PulseMCP | Keep up-to-date with MCP](https://www.pulsemcp.com/), read 5 November 2026 - [MCP Server Directory: 21,580+ updated daily | PulseMCP](https://www.pulsemcp.com/servers), read 5 November 2026 - [Pulse REST API for MCP Servers | PulseMCP](https://www.pulsemcp.com/api), read 5 November 2026 - [The MCP Registry - Model Context Protocol](https://modelcontextprotocol.io/registry/about), read 5 November 2026 (the project's own page) Last reviewed 5 November 2026 --- --- title: "Pydantic AI: MCP vendor profile | Agent MCP Directory" description: "Pydantic AI: SDK or framework. Products: Pydantic AI. 6 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/pydantic-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Pydantic AI: MCP vendor profile | Agent MCP Directory > Pydantic AI: SDK or framework. Products: Pydantic AI. 6 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/pydantic-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Pydantic AI: MCP vendor profile Pydantic AI is a Python agent framework that connects agents to MCP servers through an MCP capability, runs servers locally by default with an opt-in for model providers' native MCP, and can serve agents as MCP servers, as documented by the vendor. ## At a glance | Type | SDKs and frameworks | | --- | --- | | Operator | Pydantic | | Home | ai.pydantic.dev | | Price | open source | | Read | 5 November 2026 | ## What it does for this layer Pydantic AI says agents "can connect to MCP servers and use their tools" and can also be used within MCP servers ([ai.pydantic.dev](https://ai.pydantic.dev/mcp/)). The recommended way to give a Pydantic AI agent an MCP server is the MCP capability, which runs the server locally by default to keep credentials, hooks and tracing under the developer's control ([ai.pydantic.dev](https://ai.pydantic.dev/mcp/)). With native=True, the Pydantic AI MCP capability uses the model provider's native MCP support and falls back to local if the model does not support it ([ai.pydantic.dev](https://ai.pydantic.dev/mcp/)). Pydantic AI's local MCP side accepts a URL, a FastMCP transport, a pre-built fastmcp.Client, an in-process FastMCP server or a local script ([ai.pydantic.dev](https://ai.pydantic.dev/mcp/)). For lower-level control, Pydantic AI offers MCPToolset to manage the toolset lifecycle or share one MCP server across several agents, and MCPServerTool for provider-native MCP only ([ai.pydantic.dev](https://ai.pydantic.dev/mcp/)). Pydantic's MCP page names its own Logfire MCP server for logs, traces and metrics and a Run Python MCP server that runs code in a sandbox ([ai.pydantic.dev](https://ai.pydantic.dev/mcp/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Pydantic AI | Open-source Python agent framework with MCP client and server support. | open source; from 0 USD (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | pydantic.dev | 90 of 100, grade A | 4 November 2026 | how it was taken | | Cloudflare agent-readiness scan | pydantic.dev | 60 of 100, L5 Agent-Native; 9 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Pydantic AI does not host remote MCP servers; it runs them locally or calls them by URL. ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/pydantic-ai/index.md) ## Sources - [Model Context Protocol (MCP) | Pydantic Docs](https://ai.pydantic.dev/mcp/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Scalekit: MCP vendor profile | Agent MCP Directory" description: "Scalekit: auth provider. Products: MCP Auth, AgentKit. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/scalekit site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Scalekit: MCP vendor profile | Agent MCP Directory > Scalekit: auth provider. Products: MCP Auth, AgentKit. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/scalekit Site: Agent MCP Directory Last reviewed: 2026-11-05 # Scalekit: MCP vendor profile Scalekit is an OAuth 2.1 authorization server for MCP servers with DCR and CIMD, and also sells AgentKit, an MCP gateway with 600+ connectors and virtual MCP servers scoped by agent role, as documented by the vendor. Scalekit warns that toggling DCR or CIMD requires restarting the MCP server because frameworks such as FastMCP cache authorization server details (docs.scalekit.com). ## At a glance | Type | Auth providers | | --- | --- | | Also covers | gateway or proxy, connector platform | | Home | www.scalekit.com | | Price | per tool call | | Read | 5 November 2026 | ## What it does for this layer Scalekit recommends keeping both Dynamic Client Registration and Client ID Metadata Document enabled for public clients such as Claude, Cursor and VS Code, so clients without CIMD fall back to DCR ([docs.scalekit.com](https://docs.scalekit.com/authenticate/mcp/quickstart/)). Scalekit has the MCP server host /.well-known/oauth-protected-resource with the metadata JSON copied from the dashboard, whose authorization\_servers field holds the Scalekit resource identifier ([docs.scalekit.com](https://docs.scalekit.com/authenticate/mcp/quickstart/)). Scalekit offers a FastMCP plugin that, per the quickstart, adds auth to an MCP server "in just 5 lines of code" ([docs.scalekit.com](https://docs.scalekit.com/authenticate/mcp/quickstart/), vendor's own claim). Scalekit pricing describes AgentKit as connecting agents "to 600+ connectors and 30,000+ tools" ([www.scalekit.com](https://www.scalekit.com/pricing), vendor's own claim). Scalekit's AgentKit Free plan includes 10,000 tool calls and 10,000 trigger events a month; Growth is 99 USD a month with 100,000 tool calls plus 0.50 USD per 1,000 more ([www.scalekit.com](https://www.scalekit.com/pricing)). Scalekit's product menu lists AgentKit as an "MCP Gateway for agents" with "Virtual MCP servers" that scope tools by agent role ([www.scalekit.com](https://www.scalekit.com/mcp-auth)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Auth | OAuth 2.1 authorization server for MCP servers with DCR and CIMD. | price not read | | AgentKit | MCP gateway with connectors, per-user credentials, virtual MCP servers and logs. | per tool call; from 0 USD; Free 10,000 tool calls a month; Growth 99 USD a month (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | dynamic client registration | Supports | DCR toggle in the dashboard. | docs.scalekit.com | | MCP | client ID metadata documents | Supports | CIMD toggle in the dashboard. | docs.scalekit.com | | MCP | protected resource metadata | Supports | Server hosts /.well-known/oauth-protected-resource. | docs.scalekit.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | scalekit.com | 74 of 100, grade B | 10 October 2026 | how it was taken | | Cloudflare agent-readiness scan | scalekit.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Scalekit does not host the developer's MCP server; the server validates Scalekit tokens with the SDK ([docs.scalekit.com](https://docs.scalekit.com/authenticate/mcp/quickstart/)). ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/scalekit/index.md) ## Sources - [Auth for MCP Servers: Drop-in OAuth 2.1 | Scalekit](https://www.scalekit.com/mcp-auth), read 5 November 2026 - [MCP auth quickstart - Scalekit docs](https://docs.scalekit.com/authenticate/mcp/quickstart/), read 5 November 2026 - [AgentKit Pricing: AI Agent Integrations, Free to Start](https://www.scalekit.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Snyk Agent Scan: MCP vendor profile | Agent MCP Directory" description: "Snyk Agent Scan: security scanner. Products: Agent Scan. 9 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/snyk-agent-scan site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Snyk Agent Scan: MCP vendor profile | Agent MCP Directory > Snyk Agent Scan: security scanner. Products: Agent Scan. 9 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/snyk-agent-scan Site: Agent MCP Directory Last reviewed: 2026-11-05 # Snyk Agent Scan: MCP vendor profile Snyk Agent Scan, the former Invariant Labs mcp-scan, discovers agent configurations on a machine and scans their MCP servers, tools, prompts, resources and skills for prompt injection and other risks, as documented by the vendor. Agent Scan validates components with local checks and the Agent Scan API, sending agent application details, MCP server configurations and signatures for analysis (github.com). ## At a glance | Listed as | Snyk Agent Scan (formerly Invariant Labs mcp-scan) | | --- | --- | | Type | Security scanners | | Operator | Snyk | | Home | github.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer Running Agent Scan requires a Snyk API token set as an environment variable before any scan ([github.com](https://github.com/snyk/agent-scan)). Snyk does not publish an npm package for Agent Scan; it installs with uvx (for example uvx --python 3.13 snyk-agent-scan@latest scan mcp.json) or as a standalone binary ([github.com](https://github.com/snyk/agent-scan)). Agent Scan v0.5.x with issue-code output is planned for deprecation; v0.6 and later report risk-based output, and Snyk calls the raw CLI output experimental ([github.com](https://github.com/snyk/agent-scan)). Agent Scan accepts --mcp-oauth-tokens-path to scan remote MCP servers protected by OAuth ([github.com](https://github.com/snyk/agent-scan)). Snyk keeps Agent Scan open source under Apache-2.0; its repository counted about 3.2k stars on 5 Nov 2026 ([github.com](https://github.com/snyk/agent-scan), observed 5 November 2026). The former invariantlabs-ai/mcp-scan repository URL redirected to github.com/snyk/agent-scan on 5 Nov 2026 ([github.com](https://github.com/snyk/agent-scan), observed 5 November 2026). Snyk describes Agent Scan as a "Security scanner for AI agents, MCP servers and agent skills" that looks for prompt injections and vulnerabilities ([github.com](https://github.com/snyk/agent-scan)). Agent Scan scans MCP servers, tools, prompts, resources and skills and discovers configurations for Claude Code and Desktop, Cursor, Gemini CLI and Windsurf ([github.com](https://github.com/snyk/agent-scan)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Agent Scan | CLI scanner for agent configs, MCP servers and skills, backed by the Snyk analysis API. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | Agent Skills | skills scanning | Supports | Agent Scan 0.4 added scanning of agent skills. | github.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | snyk.io | 79 of 100, grade B | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan | snyk.io | 40 of 100, L4 Agent-Integrated; 6 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Agent Scan does not sit in the request path at runtime; it scans configurations and definitions. ## Related on this site Type - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) Standards - [Agent Skills](https://agentmcpdirectory.com/standards/agent-skills/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/snyk-agent-scan/index.md) ## Sources - [GitHub - snyk/agent-scan (formerly invariantlabs-ai/mcp-scan)](https://github.com/snyk/agent-scan), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Speakeasy: MCP vendor profile | Agent MCP Directory" description: "Speakeasy: gateway or proxy. Products: MCP Gateway. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/speakeasy site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Speakeasy: MCP vendor profile | Agent MCP Directory > Speakeasy: gateway or proxy. Products: MCP Gateway. 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/speakeasy Site: Agent MCP Directory Last reviewed: 2026-11-05 # Speakeasy: MCP vendor profile Speakeasy now sells an AI control plane centred on an MCP gateway that discovers the MCP servers employees use, promotes approved ones into an internal registry and provisions them by IdP role, as documented by the vendor. Speakeasy's gateway surfaces "shadow MCP" servers in use, who uses them and which tools they expose, and blocks unsanctioned servers by default (www.speakeasy.com). ## At a glance | Listed as | Speakeasy (MCP Gateway) | | --- | --- | | Type | Gateways and proxies | | Also covers | registry or directory | | Home | www.speakeasy.com | | Price | usage, no platform fee | | Read | 5 November 2026 | ## What it does for this layer Speakeasy assigns servers to groups in Okta or Entra so they appear in members' Claude, Cursor and ChatGPT clients ([www.speakeasy.com](https://www.speakeasy.com/product/mcp-gateway.md)). Speakeasy lists "OAuth 2.1 with CIMD and EMA" and RBAC down to the individual tool ([www.speakeasy.com](https://www.speakeasy.com/product/mcp-gateway.md)). Speakeasy streams one audit log of tool calls to Datadog, Splunk or another SIEM ([www.speakeasy.com](https://www.speakeasy.com/product/mcp-gateway.md)). Speakeasy has no platform fee and bills 0.35 USD per million tokens of agent session storage, 0.99 USD per million tokens scanned for risk and 20 USD per GiB of MCP gateway egress ([www.speakeasy.com](https://www.speakeasy.com/pricing)). Speakeasy's catalog page lists MCP servers for GitHub, Notion, Linear, Stripe, PostHog, Supabase, Figma, HubSpot and Context7 ([www.speakeasy.com](https://www.speakeasy.com/product/mcp-gateway.md)). Speakeasy's llms.txt calls Speakeasy "the AI control plane for the AI-native enterprise" with the MCP Gateway at its centre ([www.speakeasy.com](https://www.speakeasy.com/llms.txt)). Admins promote a discovered server into Speakeasy's registry in one step, filtered to approved tools ([www.speakeasy.com](https://www.speakeasy.com/product/mcp-gateway.md)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP Gateway | Governed MCP gateway with registry, IdP provisioning, RBAC and audit. | usage, no platform fee; from 0.35 USD; per million tokens of session storage (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | client ID metadata documents | Supports | "OAuth 2.1 with CIMD and EMA". | www.speakeasy.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | speakeasy.com | 92 of 100, grade A | 30 October 2026 | how it was taken | | Cloudflare agent-readiness scan | speakeasy.com | 53 of 100, L4 Agent-Integrated; 8 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Speakeasy's gateway is for a company's own employees and agents, not a public directory. - The Speakeasy product page read here does not describe generating SDKs. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) - [Registries and directories](https://agentmcpdirectory.com/vendors/by-type/registry/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/speakeasy/index.md) ## Sources - [Speakeasy home](https://www.speakeasy.com/product/mcp-gateway), read 5 November 2026 - [Speakeasy llms.txt](https://www.speakeasy.com/llms.txt), read 5 November 2026 - [Speakeasy MCP Gateway (product page, markdown)](https://www.speakeasy.com/product/mcp-gateway.md), read 5 November 2026 - [Speakeasy pricing](https://www.speakeasy.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Spring AI: MCP vendor profile | Agent MCP Directory" description: "Spring AI: SDK or framework. Products: Spring AI MCP. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/spring-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Spring AI: MCP vendor profile | Agent MCP Directory > Spring AI: SDK or framework. Products: Spring AI MCP. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/spring-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Spring AI: MCP vendor profile Spring AI builds on the MCP Java SDK with Spring Boot starters for MCP clients and servers, annotation-based tool handling, and the Spring WebFlux and WebMVC transports, as documented by the vendor. Spring AI's MCP docs cover STDIO and SSE servers, Streamable-HTTP servers and Stateless Streamable-HTTP servers (docs.spring.io). ## At a glance | Listed as | Spring AI (MCP) | | --- | --- | | Type | SDKs and frameworks | | Home | docs.spring.io | | Price | open source | | Read | 5 November 2026 | ## What it does for this layer Starting with Spring AI 2.0, the Spring-specific transports mcp-spring-webflux and mcp-spring-webmvc moved from the MCP Java SDK into the Spring AI project, which Spring calls a breaking change ([docs.spring.io](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html)). The Java MCP implementation documented by Spring AI uses a three-layer architecture with the transport layer at the bottom ([docs.spring.io](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html)). Spring AI's docs include a guide on migrating the Anthropic module to the official Java SDK ([docs.spring.io](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html)). Spring AI documents MCP Client Boot Starters and MCP Server Boot Starters for Spring Boot applications ([docs.spring.io](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html)). Spring AI provides an MCP Annotations module for annotation-based handling of MCP server and client operations ([docs.spring.io](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Spring AI MCP | Boot starters, annotations and Spring transports for MCP in Java. | open source; from 0 USD (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | stateless streamable HTTP | Supports | Docs for Stateless Streamable-HTTP MCP servers. | docs.spring.io | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | spring.io | 58 of 100, grade C | 24 April 2026 | how it was taken | | Cloudflare agent-readiness scan | spring.io | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Spring AI does not host MCP servers; it is a library for Spring applications. ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/spring-ai/index.md) ## Sources - [Model Context Protocol (MCP) :: Spring AI Reference](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-overview.html), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "StackOne: MCP vendor profile | Agent MCP Directory" description: "StackOne: connector platform. Products: StackOne MCP server, plus 1 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/stackone site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # StackOne: MCP vendor profile | Agent MCP Directory > StackOne: connector platform. Products: StackOne MCP server, plus 1 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/stackone Site: Agent MCP Directory Last reviewed: 2026-11-05 # StackOne: MCP vendor profile StackOne runs a hosted MCP server and an enterprise Tool Gateway MCP that give agents 43,000+ actions across 630+ connectors, with per-account tool catalogs and StackOne handling provider authentication, as documented by the vendor. StackOne's hosted MCP server is at https://mcp.stackone.com/mcp, and ChatGPT, Claude or Cursor can connect by signing in with a StackOne login over OAuth (docs.stackone.com). ## At a glance | Type | Connector platforms | | --- | --- | | Also covers | gateway or proxy | | Home | www.stackone.com | | Price | no published price | | Read | 5 November 2026 | ## What it does for this layer StackOne says its connectors cover "43,000+ pre-built actions across 635 connectors", ready for MCP, A2A, CLI, SDK or API clients ([www.stackone.com](https://www.stackone.com/llms.txt), vendor's own claim). StackOne's Tool Gateway MCP is "the enterprise MCP gateway": one URL connects every employee's AI to business systems, with the IT team choosing access above the gateway ([www.stackone.com](https://www.stackone.com/platform/mcp/)). StackOne says agents sign in with MCP OAuth, scoped API keys or short-lived session tokens ([www.stackone.com](https://www.stackone.com/llms.txt)). StackOne announced Tool Policies on its home page, described as AI agent permissions "down to the field" ([www.stackone.com](https://www.stackone.com/)). The StackOne MCP server generates its tool catalog from the account's configured connectors and enabled actions ([docs.stackone.com](https://docs.stackone.com/embed/call-actions/mcp)). StackOne provides a pre-built MCP server for each linked account, with authentication to third-party providers handled by StackOne ([docs.stackone.com](https://docs.stackone.com/embed/call-actions/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | StackOne MCP server | Hosted MCP server per linked account across StackOne connectors. | no published price | | Tool Gateway MCP | Enterprise MCP gateway for employees' AI assistants. | no published price | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | A2A | A2A access | Supports | Connectors are offered over MCP, A2A, CLI, SDK or API. | www.stackone.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | stackone.com | 87 of 100, grade A | 15 October 2026 | how it was taken | | Cloudflare agent-readiness scan | stackone.com | 73 of 100, L5 Agent-Native; 11 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - StackOne does not publish prices on the pages read. - StackOne does not host customer-written MCP servers; it serves its own connectors. ## Related on this site Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [A2A](https://agentmcpdirectory.com/standards/a2a/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/stackone/index.md) ## Sources - [AI Agent Integration Infrastructure | StackOne](https://www.stackone.com/), read 5 November 2026 - [StackOne llms.txt](https://www.stackone.com/llms.txt), read 5 November 2026 - [MCP - Stackone](https://docs.stackone.com/embed/call-actions/mcp), read 5 November 2026 - [Tool Gateway MCP: the enterprise MCP gateway | StackOne](https://www.stackone.com/platform/mcp/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Stainless: MCP vendor profile | Agent MCP Directory" description: "Stainless: SDK or framework. Products: MCP server generator. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/stainless site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Stainless: MCP vendor profile | Agent MCP Directory > Stainless: SDK or framework. Products: MCP server generator. 6 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/stainless Site: Agent MCP Directory Last reviewed: 2026-11-05 # Stainless: MCP vendor profile Stainless generates an MCP server from an OpenAPI spec as a subpackage of a generated TypeScript SDK, exposing a code execution tool and a docs search tool instead of one tool per endpoint, as documented by the vendor. Stainless pricing counts a "generator" as any single SDK, docs site or MCP server (www.stainless.com). ## At a glance | Type | SDKs and frameworks | | --- | --- | | Home | www.stainless.com | | Price | per generator | | Read | 5 November 2026 | ## What it does for this layer Stainless-hosted code execution (stainless-sandbox mode) is deprecated, and the tool may return 410 Gone, in which case the docs say to run with --code-execution-mode=local ([www.stainless.com](https://www.stainless.com/docs/mcp)). Stainless runs an MCP Portal page with guides and a customer story about Scorecard's remote MCP server, built with Stainless and Clerk ([www.stainless.com](https://www.stainless.com/mcp)). Stainless generates MCP servers from an OpenAPI specification; the docs say "MCP server generation is experimental" ([www.stainless.com](https://www.stainless.com/docs/mcp)). A Stainless MCP server is generated as a subpackage of the TypeScript SDK at packages/mcp-server, enabled by adding mcp\_server options to the typescript target ([www.stainless.com](https://www.stainless.com/docs/mcp)). The Stainless code execution tool accepts TypeScript that runs against the generated SDK, and --code-execution-mode=local runs it in a Deno subprocess ([www.stainless.com](https://www.stainless.com/docs/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | MCP server generator | Generates an MCP server package from an OpenAPI spec. | per generator; from 0 USD; Free plan available; paid tiers by SDKs and endpoints (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | OpenAPI | OpenAPI as source | Supports | Generates the MCP server from an OpenAPI specification. | www.stainless.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | stainless.com | 58 of 100, grade C | 10 September 2026 | how it was taken | | Cloudflare agent-readiness scan | stainless.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Stainless does not generate one MCP tool per endpoint by default ([www.stainless.com](https://www.stainless.com/docs/mcp)). ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Standards - [OpenAPI](https://agentmcpdirectory.com/standards/openapi-as-agent-surface/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/stainless/index.md) ## Sources - [Stainless - MCP Portal](https://www.stainless.com/mcp), read 5 November 2026 - [Create an MCP server from your OpenAPI specification | Stainless](https://www.stainless.com/docs/mcp), read 5 November 2026 - [Stainless - Pricing - Get the pricing that’s right for your API.](https://www.stainless.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Stytch: MCP vendor profile | Agent MCP Directory" description: "Stytch: auth provider. Products: Connected Apps. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/stytch site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Stytch: MCP vendor profile | Agent MCP Directory > Stytch: auth provider. Products: Connected Apps. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/stytch Site: Agent MCP Directory Last reviewed: 2026-11-05 # Stytch: MCP vendor profile Stytch Connected Apps turns an app into the OAuth authorization server for its remote MCP server, treating each MCP client as a Connected App that asks for consent through the authorization code grant, as documented by the vendor. Stytch pricing says 10,000 monthly active users and AI agents are "Always free" (stytch.com). ## At a glance | Listed as | Stytch (Connected Apps for MCP) | | --- | --- | | Type | Auth providers | | Operator | Twilio | | Home | stytch.com | | Price | free tier then usage | | Read | 5 November 2026 | ## What it does for this layer Stytch's own MCP server at https://mcp.stytch.dev/mcp answers an unauthenticated request with a resource\_metadata pointer to /.well-known/oauth-protected-resource, and the guide uses it as the worked example ([stytch.com](https://stytch.com/docs/guides/connected-apps/mcp-server-overview)). Stytch pricing states no hard caps: past the free 10,000 MAUs, 5 SSO or SCIM connections, 1,000 M2M tokens and 10,000 fingerprints, usage is billed per unit, for example 125 USD per connection and 0.005 USD per fingerprint ([stytch.com](https://stytch.com/pricing)). The Stytch home page says Stytch "has joined Twilio" ([stytch.com](https://stytch.com/)). The Stytch home page markets agent detection with the line "Detect and stop malicious and misbehaving agents" ([stytch.com](https://stytch.com/), vendor's own claim). Stytch's MCP guide says "MCP Clients are a type of Connected App" that request access to a member's account through the authorization\_code grant ([stytch.com](https://stytch.com/docs/guides/connected-apps/mcp-server-overview)). With Stytch, the app hosts a Stytch component for the OAuth consent step, either in its main frontend or in a standalone MCP server ([stytch.com](https://stytch.com/docs/guides/connected-apps/mcp-server-overview)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Connected Apps | OAuth authorization server and consent UI that lets MCP clients connect to an app's MCP server. | free tier then usage; from 0 USD; 10,000 MAUs and AI agents free (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | protected resource metadata | Supports | The worked example serves /.well-known/oauth-protected-resource. | stytch.com | | MCP | OAuth authorization code grant | Supports | MCP clients use the authorization_code grant as Connected Apps. | stytch.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | stytch.com | 63 of 100, grade C | 31 August 2026 | how it was taken | | Cloudflare agent-readiness scan | stytch.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Stytch does not host the MCP server; the guide has the developer build it on Cloudflare, Vercel or another host ([stytch.com](https://stytch.com/docs/guides/connected-apps/mcp-server-overview)). - The Stytch MCP guide read here does not state Client ID Metadata Document support. ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/stytch/index.md) ## Sources - [Stytch - A better way to build auth](https://stytch.com/), read 5 November 2026 - [MCP authorization overview - Stytch Docs](https://stytch.com/docs/guides/connected-apps/mcp-server-overview), read 5 November 2026 - [Modern authentication pricing | Stytch](https://stytch.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Teleport: MCP vendor profile | Agent MCP Directory" description: "Teleport: gateway or proxy. Products: Teleport MCP access. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/teleport site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Teleport: MCP vendor profile | Agent MCP Directory > Teleport: gateway or proxy. Products: Teleport MCP access. 7 dated facts, price status, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/teleport Site: Agent MCP Directory Last reviewed: 2026-11-05 # Teleport: MCP vendor profile Teleport enrolls MCP servers as resources in a Teleport cluster, so engineers and AI clients reach them through Teleport with role-based permissions, audit and short-lived identity, as documented by the vendor. Teleport supports dynamic MCP server registration without editing the static configuration of Application Service instances (goteleport.com). ## At a glance | Listed as | Teleport (MCP access) | | --- | --- | | Type | Gateways and proxies | | Home | goteleport.com | | Price | price not read | | Read | 5 November 2026 | ## What it does for this layer Teleport documents enrollment for streamable-HTTP, stdio and SSE MCP servers ([goteleport.com](https://goteleport.com/docs/enroll-resources/mcp-access/)). Teleport can authenticate itself to an MCP server with JWTs signed by Teleport's CA that carry the user's identity, roles and traits ([goteleport.com](https://goteleport.com/docs/enroll-resources/mcp-access/)). Teleport documents client setup for MCP clients such as Claude Desktop and Cursor, and the Teleport CLI can query enrolled servers ([goteleport.com](https://goteleport.com/docs/enroll-resources/mcp-access/)). Teleport uses its role-based access control system to set granular permissions for MCP servers connected to a cluster ([goteleport.com](https://goteleport.com/docs/enroll-resources/mcp-access/)). Teleport connects an MCP server through the Teleport Application Service and grants access with a role that carries MCP permissions ([goteleport.com](https://goteleport.com/docs/enroll-resources/mcp-access/)). Teleport also documents MCP access to databases through the same client configuration path ([goteleport.com](https://goteleport.com/docs/enroll-resources/mcp-access/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Teleport MCP access | Enrollment of MCP servers into a Teleport cluster with RBAC and audit. | price not read | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | streamable HTTP | Supports | Enrollment guide for streamable-HTTP MCP servers. | goteleport.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | goteleport.com | 59 of 100, grade C | 25 August 2026 | how it was taken | | Cloudflare agent-readiness scan | goteleport.com | 27 of 100, L2 Bot-Aware; 4 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Teleport does not offer a public MCP registry. - Teleport's MCP docs read here do not describe CIMD or DCR for third-party MCP clients. ## Related on this site Type - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/teleport/index.md) ## Sources - [goteleport.com/docs/enroll-resources/mcp-access/](https://goteleport.com/docs/enroll-resources/mcp-access/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Trail of Bits mcp-context-protector: MCP | Agent MCP Directory" description: "Trail of Bits mcp-context-protector: security scanner. 1 product, 7 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/trailofbits-context-protector site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Trail of Bits mcp-context-protector: MCP | Agent MCP Directory > Trail of Bits mcp-context-protector: security scanner. 1 product, 7 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/trailofbits-context-protector Site: Agent MCP Directory Last reviewed: 2026-11-05 # Trail of Bits mcp-context-protector: MCP vendor profile mcp-context-protector from Trail of Bits wraps MCP servers to pin their configuration on first use, quarantine tool responses flagged by guardrails and strip ANSI control characters, as documented by the vendor. Trail of Bits releases mcp-context-protector under Apache-2.0, and GitHub counted 228 stars for it on 5 Nov 2026 (github.com, observed 5 November 2026). ## At a glance | Type | Security scanners | | --- | --- | | Operator | Trail of Bits | | Home | github.com | | Price | open source, Apache-2.0 | | Read | 5 November 2026 | ## What it does for this layer Trail of Bits calls mcp-context-protector an "MCP security wrapper" for the risks of running untrusted MCP servers, including line jumping and unexpected configuration changes ([github.com](https://github.com/trailofbits/mcp-context-protector)). Clients run their MCP servers through mcp-context-protector, and the README shows a Claude Desktop configuration that enables tool configuration pinning ([github.com](https://github.com/trailofbits/mcp-context-protector)). The README warns that some clients, including Cursor at the time of writing, join stdio server arguments into one space-delimited string, and adds a --command-args option for that case ([github.com](https://github.com/trailofbits/mcp-context-protector)). mcp-context-protector pins server configurations with trust-on-first-use, so a changed tool configuration is caught before the client sees it ([github.com](https://github.com/trailofbits/mcp-context-protector)). mcp-context-protector scans tool responses with guardrails and quarantines flagged responses ([github.com](https://github.com/trailofbits/mcp-context-protector)). mcp-context-protector sanitises ANSI control characters in server output ([github.com](https://github.com/trailofbits/mcp-context-protector)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | mcp-context-protector | Open-source wrapper that pins MCP server configs and screens responses. | open source, Apache-2.0; from 0 USD (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | trailofbits.com | 47 of 100, grade D | 25 August 2026 | how it was taken | | Cloudflare agent-readiness scan | trailofbits.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - mcp-context-protector does not scan a whole machine for agent configs; it wraps the servers a client is configured to run through it. - Trail of Bits does not sell mcp-context-protector as a hosted service. ## Related on this site Type - [Security scanners](https://agentmcpdirectory.com/vendors/by-type/security-scanner/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/trailofbits-context-protector/index.md) ## Sources - [GitHub - trailofbits/mcp-context-protector](https://github.com/trailofbits/mcp-context-protector), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Vercel: MCP vendor profile | Agent MCP Directory" description: "Vercel: host or runtime. Products: mcp-handler, Vercel MCP, plus 2 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/vercel site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Vercel: MCP vendor profile | Agent MCP Directory > Vercel: host or runtime. Products: mcp-handler, Vercel MCP, plus 2 more. 7 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/vercel Site: Agent MCP Directory Last reviewed: 2026-11-05 # Vercel: MCP vendor profile Vercel hosts MCP servers built with mcp-handler as Vercel Functions, runs its own remote Vercel MCP server, and ships an MCP client in the AI SDK alongside the AI Gateway for model traffic, as documented by the vendor. The AI SDK supports HTTP, SSE, stdio and custom transports, and an OAuth client provider for automatic authorization (ai-sdk.dev). ## At a glance | Listed as | Vercel (mcp-handler, Vercel MCP, AI SDK, AI Gateway) | | --- | --- | | Type | Hosts and runtimes | | Also covers | SDK or framework, gateway or proxy | | Home | vercel.com | | Price | per plan plus usage | | Read | 5 November 2026 | ## What it does for this layer The AI SDK recommends the HTTP transport, such as StreamableHTTPClientTransport, for production, and says stdio "should only be used for connecting to local servers" ([ai-sdk.dev](https://ai-sdk.dev/docs/ai-sdk-core/mcp-tools)). The AI SDK calls its MCP client "lightweight" and says it does not support automatic session persistence, resumable streams or receiving notifications ([ai-sdk.dev](https://ai-sdk.dev/docs/ai-sdk-core/mcp-tools)). Vercel pricing lists Hobby at 0 USD a month and Pro at 20 USD a month with 20 USD of included usage credit ([vercel.com](https://vercel.com/pricing)). Vercel pricing describes Pro as including a flat-rate CDN with traffic spike protection ([vercel.com](https://vercel.com/pricing)). Vercel's MCP docs cover deploying MCP servers on Vercel, trying Vercel's own MCP server, and connecting eve, the AI SDK or TanStack AI to MCP servers ([vercel.com](https://vercel.com/docs/mcp)). The AI SDK MCP client is created with createMCPClient from @ai-sdk/mcp ([ai-sdk.dev](https://ai-sdk.dev/docs/ai-sdk-core/mcp-tools)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | mcp-handler | Adapter for building MCP servers in Next.js and other frameworks on Vercel. | price not read | | Vercel MCP | Vercel's own remote MCP server with OAuth. | price not read | | AI SDK MCP client | createMCPClient for connecting agents to MCP servers. | price not read | | Vercel platform | Hosting for MCP servers as Functions. | per plan plus usage; from 20 USD; Pro 20 USD a month; Hobby free (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | streamable HTTP | Supports | AI SDK recommends Streamable HTTP for production. | ai-sdk.dev | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | vercel.com | 91 of 100, grade A | 5 November 2026 | how it was taken | | Cloudflare agent-readiness scan | vercel.com | 60 of 100, L1 Basic Web Presence; 9 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Vercel does not run a public MCP registry. ## Relation to Ora Ora says in its launch post of 19 October 2026 that it built the is-agentic.com scanner with Vercel for sites whose job is content, and the AgentReady.org committee gives Vercel infrastructure and web essentials: whether agents can reach a page and read the answer in it ([ora.ai](https://ora.ai/blog/agentready-launch?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026). ## Related on this site Hosts page - [Vercel](https://agentmcpdirectory.com/hosts/vercel/) - [Vercel AI Gateway](https://agentmcpdirectory.com/hosts/vercel-ai-gateway/) Type - [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/) - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) - [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/vercel/index.md) ## Sources - [Model Context Protocol](https://vercel.com/docs/mcp), read 5 November 2026 - [Model Context Protocol (MCP) | AI SDKOpenAIPhotoroomLeonardo AIZapier](https://ai-sdk.dev/docs/ai-sdk-core/mcp-tools), read 5 November 2026 - [Vercel Pricing: Hobby, Pro, and Enterprise plans](https://vercel.com/pricing), read 5 November 2026 - [Introducing AgentReady.org: the first open standard for AX | Ora](https://ora.ai/blog/agentready-launch?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=profile), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "WorkOS: MCP vendor profile | Agent MCP Directory" description: "WorkOS: auth provider. Products: AuthKit (MCP Auth). 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/workos site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # WorkOS: MCP vendor profile | Agent MCP Directory > WorkOS: auth provider. Products: AuthKit (MCP Auth). 8 dated facts, prices, standards and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/workos Site: Agent MCP Directory Last reviewed: 2026-11-05 # WorkOS: MCP vendor profile WorkOS AuthKit is a spec-compatible OAuth authorization server for MCP servers, built on WorkOS Connect, with CIMD and optional DCR client registration and resource indicators, as documented by the vendor. In WorkOS, Client ID Metadata Document support is off by default and is enabled in the Dashboard under Connect, Configuration (workos.com). ## At a glance | Listed as | WorkOS (AuthKit for MCP) | | --- | --- | | Type | Auth providers | | Home | workos.com | | Price | per MAU above 1 million, per connection | | Read | 5 November 2026 | ## What it does for this layer WorkOS keeps Dynamic Client Registration as an opt-in for backwards compatibility with MCP clients that do not support CIMD yet ([workos.com](https://workos.com/docs/authkit/mcp)). WorkOS asks the developer to register the MCP endpoint URL as a Resource Indicator, which clients send as the resource parameter; several resource URLs can be added ([workos.com](https://workos.com/docs/authkit/mcp)). WorkOS pricing lists the first 1 million monthly active users free and 2,500 USD a month for each additional million ([workos.com](https://workos.com/pricing)). WorkOS prices enterprise SSO connections from 125 USD each for 1 to 15 connections down to 65 USD each for 51 to 100 ([workos.com](https://workos.com/pricing)). The WorkOS product menu lists MCP Auth next to auth.md, described as "User registration for agents" ([workos.com](https://workos.com/mcp)). WorkOS describes AuthKit as "a spec-compatible OAuth authorization server" that sits in front of an MCP server acting as the resource server ([workos.com](https://workos.com/docs/authkit/mcp)). AuthKit's MCP support is built on WorkOS Connect, and its metadata at /.well-known/oauth-authorization-server lists authorize, introspection, register and token endpoints ([workos.com](https://workos.com/docs/authkit/mcp)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | AuthKit (MCP Auth) | OAuth authorization server for MCP servers with CIMD, DCR and resource indicators. | per MAU above 1 million, per connection; from 0 USD; First 1M MAUs free (source, as of 5 November 2026) | ## Standards | Standard | Part of it | Status | What the page says | Source | | --- | --- | --- | --- | --- | | MCP | authorization server metadata | Supports | AuthKit serves /.well-known/oauth-authorization-server. | workos.com | | MCP | client ID metadata documents | Supports | CIMD can be enabled in the Dashboard; off by default. | workos.com | | MCP | dynamic client registration | Supports | DCR can be enabled for backwards compatibility. | workos.com | | MCP | resource parameter | Supports | MCP endpoint URLs are registered as Resource Indicators. | workos.com | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | workos.com | 86 of 100, grade A | 4 November 2026 | how it was taken | | Cloudflare agent-readiness scan | workos.com | 40 of 100, L1 Basic Web Presence; 6 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - WorkOS does not host the MCP server; the developer verifies AuthKit tokens in their own server. ## Related on this site Type - [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/) Standards - [MCP](https://agentmcpdirectory.com/standards/mcp/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/workos/index.md) ## Sources - [Secure auth for MCP servers - WorkOS](https://workos.com/mcp), read 5 November 2026 - [workos.com/docs/authkit/mcp](https://workos.com/docs/authkit/mcp), read 5 November 2026 - [workos.com/pricing](https://workos.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "xmcp: MCP vendor profile | Agent MCP Directory" description: "xmcp: SDK or framework. Products: xmcp. 6 dated facts, prices and two checks, each fact with its source, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/xmcp site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # xmcp: MCP vendor profile | Agent MCP Directory > xmcp: SDK or framework. Products: xmcp. 6 dated facts, prices and two checks, each fact with its source, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/xmcp Site: Agent MCP Directory Last reviewed: 2026-11-05 # xmcp: MCP vendor profile xmcp is a TypeScript framework from basement.studio that registers MCP tools, prompts and resources from project files and ships adapters for Next.js and Express plus auth and payment integrations, as documented by the vendor. xmcp supports HTTP and STDIO transports (xmcp.dev). ## At a glance | Listed as | xmcp (basement.studio) | | --- | --- | | Type | SDKs and frameworks | | Operator | basement.studio | | Home | xmcp.dev | | Price | open source | | Read | 5 November 2026 | ## What it does for this layer A new xmcp project starts with npx create-xmcp-app@latest ([xmcp.dev](https://xmcp.dev/)). xmcp serves a markdown version of docs pages when .md is appended or when Accept: text/markdown is sent, plus llms.txt and llms-full.txt ([xmcp.dev](https://xmcp.dev/)). The xmcp site says it is built by basement.studio and links github.com/basementstudio/xmcp and the xmcp npm package ([xmcp.dev](https://xmcp.dev/)). xmcp automatically registers tools, prompts and resources from project files ([xmcp.dev](https://xmcp.dev/)). xmcp ships authentication integrations, deployment adapters for existing Next.js and Express apps, and monetisation plugins ([xmcp.dev](https://xmcp.dev/)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | xmcp | Open-source TypeScript MCP framework. | open source; from 0 USD (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | xmcp.dev | 57 of 100, grade C | 16 September 2026 | how it was taken | | Cloudflare agent-readiness scan | xmcp.dev | 47 of 100, L4 Agent-Integrated; 7 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - xmcp is a framework, not a host; deployment goes through its adapters or the developer's platform. ## Related on this site Type - [SDKs and frameworks](https://agentmcpdirectory.com/vendors/by-type/sdk-or-framework/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/xmcp/index.md) ## Sources - [xmcp.dev/](https://xmcp.dev/), read 5 November 2026 Last reviewed 5 November 2026 --- --- title: "Zapier: MCP vendor profile | Agent MCP Directory" description: "Zapier: connector platform. Products: Zapier MCP. 5 dated facts, prices and two checks, each sourced, read 5 November 2026." canonical: https://agentmcpdirectory.com/vendors/zapier site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Vendors" --- # Zapier: MCP vendor profile | Agent MCP Directory > Zapier: connector platform. Products: Zapier MCP. 5 dated facts, prices and two checks, each sourced, read 5 November 2026. Source: https://agentmcpdirectory.com/vendors/zapier Site: Agent MCP Directory Last reviewed: 2026-11-05 # Zapier: MCP vendor profile Zapier MCP lets MCP clients run actions across Zapier's app catalogue, with each programmatic call drawn from the same monthly task allowance that powers Zap workflows, as documented by the vendor. Zapier's Free plan includes 100 tasks a month and basic access to its AI products, including MCP (zapier.com). ## At a glance | Listed as | Zapier (Zapier MCP) | | --- | --- | | Type | Connector platforms | | Home | zapier.com | | Price | tasks from the plan allowance | | Read | 5 November 2026 | ## What it does for this layer Zapier's plans are Free, Professional and Team, with Enterprise above them; Team adds 25 users, shared app connections and SAML SSO ([zapier.com](https://zapier.com/pricing)). Zapier lists audit logs on Team (6 months) and Enterprise (1 year) plans only ([zapier.com](https://zapier.com/pricing)). Zapier sells Agents and Chatbots as add-ons with their own billing units, outside the task allowance that MCP calls use ([zapier.com](https://zapier.com/pricing)). Zapier pricing says each programmatic call, for example through Zapier MCP, consumes tasks from the plan's monthly allowance, like each successful step in a Zap ([zapier.com](https://zapier.com/pricing)). ## Products and plans | Product | What it does | Price | | --- | --- | --- | | Zapier MCP | MCP server that exposes Zapier actions to MCP clients. | tasks from the plan allowance; from 0 USD; Free plan: 100 tasks a month (source, as of 5 November 2026) | ## Checks on its own domain | Check | Domain | Result | Scanned | Method | | --- | --- | --- | --- | --- | | Ora cached score | zapier.com | 84 of 100, grade B | 4 November 2026 | how it was taken | | Cloudflare agent-readiness scan | zapier.com | 73 of 100, L5 Agent-Native; 11 of 15 counted checks passed | 5 November 2026 | how it was taken | ## What it does not do - Zapier MCP calls are not free of charge beyond the plan's task allowance ([zapier.com](https://zapier.com/pricing)). ## Related on this site Hosts page - [Zapier MCP](https://agentmcpdirectory.com/hosts/zapier-mcp/) Type - [Connector platforms](https://agentmcpdirectory.com/vendors/by-type/connector-platform/) Section - [All vendors](https://agentmcpdirectory.com/vendors/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/vendors/zapier/index.md) ## Sources - [Zapier home](https://zapier.com/mcp), read 5 November 2026 - [zapier.com/pricing](https://zapier.com/pricing), read 5 November 2026 Last reviewed 5 November 2026 ---